ULYSSIS documentation ulyssis_docswiki https://docs.ulyssis.org/Overview MediaWiki 1.39.11 first-letter Media Special Talk User User talk ULYSSIS documentation ULYSSIS documentation talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk 8 2 2 2014-05-08T00:27:30Z Admin 1 Created page with "Overview" wikitext text/x-wiki Overview 0efc2e6be4c23b9a513d7ce0dcff8ed80e8912e7 0 3 3 2014-05-08T12:47:52Z Bert 8 Created page with "test" wikitext text/x-wiki test a94a8fe5ccb19ba61c4c0873d391e987982fbbd3 4 3 2014-05-10T01:16:30Z Bert 8 wikitext text/x-wiki test * aaa * bbb *ccc *ddd **eee *fff 413cc382bb7d2e5d1b2b1ffecefac1af856578c3 5 4 2014-05-10T01:17:26Z Bert 8 wikitext text/x-wiki test * aaa * bbb *ccc *ddd **eee *fff {| class="wikitable" ! Functie !! Persoon |- | Voorzitter || [[bert]] |- | Vicevoorzitter || [[Gebruiker:Johkke | johkke]] |- | Penningmeester || [[Gebruiker:robin5210 | robin5210]] |- | Secretaris || [[stephan]] |} 147d888b5a4a698efaec2770f6446fb7ed5f03d3 6 5 2014-05-10T01:18:12Z Bert 8 wikitext text/x-wiki test * aaa * bbb *ccc *ddd **eee *fff {| class="wikitable" ! Functie !! Persoon |- | Voorzitter || [[bert]] |- | Vicevoorzitter || [[Gebruiker:Johkke | johkke]] |- | Penningmeester || [[Gebruiker:robin5210 | robin5210]] |- | Secretaris || [[stephan]] |} {| class="wikitable" |- |* één * twee |} ca343e5e53af544393ba9dd6f892934aabd5b1ac 7 6 2014-05-10T01:18:35Z Bert 8 wikitext text/x-wiki test * aaa * bbb *ccc *ddd **eee *fff {| class="wikitable" ! Functie !! Persoon |- | Voorzitter || [[bert]] |- | Vicevoorzitter || [[Gebruiker:Johkke | johkke]] |- | Penningmeester || [[Gebruiker:robin5210 | robin5210]] |- | Secretaris || [[stephan]] |} {| class="wikitable" |- | ==titel== * één * twee |} c94527889525186dda8d34ad9221ab4f3a6dfd96 8 7 2014-05-10T01:25:03Z Bert 8 Replaced content with " ==test== *a *b" wikitext text/x-wiki ==test== *a *b ab8b6f864f8f56af881ab6031d17175423bd444d 9 8 2014-05-10T01:25:43Z Bert 8 wikitext text/x-wiki <code>==test== *a *b</code> 1d2afe0621c99e7b2cca8a683fc0a2466fc1b1ad 10 9 2014-05-10T01:25:55Z Bert 8 wikitext text/x-wiki ==test== *a *b 6709f48a6c3a70c037e9fac804ed7b6a8864c61c 11 10 2014-05-10T10:09:55Z Bert 8 wikitext text/x-wiki <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transfering your account]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] </div> <div style="clear:both;"></div> </div> a377680c7ab64f74a13e7615157f9029d9ee5c92 12 11 2014-05-10T10:10:39Z Bert 8 wikitext text/x-wiki <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transfering your account]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] </div> <div style="clear:both;"></div> 2c7a1e80ecd255b7842f99fedc1ec6d4fed1fe68 13 12 2014-05-10T10:10:59Z Bert 8 wikitext text/x-wiki <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transfering your account]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] </div> <div style="clear:both;"></div> </div> 131b7c779d463392d2fbeda86ac24785f7761fa7 14 13 2014-05-10T10:15:40Z Bert 8 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding-left:1.5em;"> = Welcome = Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support. </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transfering your account]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] </div> <div style="clear:both;"></div> </div> d70c1b969584ad2ed51931e56ac010c5d2de37f1 15 14 2014-05-10T10:15:50Z Bert 8 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding-left:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support. </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transfering your account]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] </div> <div style="clear:both;"></div> </div> db672bffee362fbd107e8d91cbee14af0204eb74 16 15 2014-05-10T10:16:06Z Bert 8 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support. </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transfering your account]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] </div> <div style="clear:both;"></div> </div> b83dd74551120f88e903e5b656a1ad1454c12d3a 17 16 2014-05-10T10:16:34Z Bert 8 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transfering your account]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] </div> <div style="clear:both;"></div> </div> 5a8e568c74c9689d246cc4c07043e1bff4ff57a8 18 17 2014-05-10T10:18:12Z Bert 8 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transfering your account]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Files == * [[Accessing your files]] * [[Transfering files over SFTP]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> d1e557a8ea3b45373b4604b2fcb914c573ce05f4 19 18 2014-05-10T10:18:36Z Bert 8 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transfering your account]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Files == * [[Accessing your files]] * [[Transfering files over SFTP]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> __NOTOC__ b13c0de500ed4662d3d431e5006cd2cfca4c6297 20 19 2014-05-10T10:28:47Z Bert 8 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transfering your account]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Files == * [[Accessing your files]] * [[Transfering files over SFTP]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transfering files over SFTP]] * [[Accessing shell servers over SSH] * [[ULYSSIS public IRC]] * [[Useful Linux Commands] </div> <div style="clear:both;"></div> </div> __NOTOC__ 077f1d976ec0a663dc6b2c36fed614e2dde99a73 21 20 2014-05-10T10:29:15Z Bert 8 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transfering your account]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Files == * [[Accessing your files]] * [[Transfering files over SFTP]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transfering files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 67f104e4510ab6fd0c856c615dd354160a88e840 22 21 2014-05-10T10:32:57Z Warreee 10 /* Files */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transfering your account]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Files == * [[Accessing your files]] * [[Transfering files over SFTP]] * [[Using SSHFS]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transfering files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 4b41b2547c5f09fbf10b66aa90894e4642363faf 40 22 2014-05-10T12:06:39Z Bert 8 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transfering your account]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Files == * [[Accessing your files]] * [[Transfering files over SFTP]] * [[Using SSHFS]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transfering files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion 101]] * [[Gitlab]] </div><div style="width:45%;float:left"> == Webserver == * [[Using your webspace]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Adding domain names (.be, .com, .org, ...)|Adding domain names]] </div> <div style="clear:both;"></div> </div> __NOTOC__ d5dd9429142954b3ba29f451b55d676f40031f01 41 40 2014-05-10T12:06:57Z Bert 8 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transfering your account]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Files == * [[Accessing your files]] * [[Transfering files over SFTP]] * [[Using SSHFS]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transfering files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion 101]] * [[Gitlab]] </div><div style="width:45%;float:left"> == Webserver == * [[Using your webspace]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 39ede5e59e9faf497cef177485aa2ca0a0027e6b 42 41 2014-05-10T12:07:51Z Bert 8 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transfering your account]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Files == * [[Accessing your files]] * [[Transfering files over SFTP]] * [[Using SSHFS]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transfering files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion 101]] * [[Gitlab]] </div><div style="width:45%;float:left"> == Webserver == * [[Using your webspace]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] </div> <div style="clear:both;"></div> </div> __NOTOC__ d003dd215e004d64083f03c7dd3a340121e355db 43 42 2014-05-10T12:10:06Z Bert 8 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transfering your account]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Files == * [[Accessing your files]] * [[Transfering files over SFTP]] * [[Using SSHFS]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transfering files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion 101]] * [[Gitlab]] </div><div style="width:45%;float:left"> == Webserver == * [[Using your webspace]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Keeping your website secure]] * [[Preventing spam on your website]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 7a37a565e10c1fb5485544b7825650958f164128 44 43 2014-05-10T15:41:22Z Bert 8 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transfering your account]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transfering files over SFTP]] * [[Using SSHFS]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Using your webspace]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transfering files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion 101]] * [[Gitlab]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Keeping your website secure]] * [[Preventing spam on your website]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 28ec20922e05d43cbbcd7bd99678632462aee8a7 45 44 2014-05-10T15:41:59Z Bert 8 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transfering your account]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transfering files over SFTP]] * [[Using SSHFS]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Using your webspace]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Keeping your website secure]] * [[Preventing spam on your website]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transfering files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion 101]] * [[Gitlab]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 9ab7317acad3bc3f58f663f5dd5fc4e20b613871 46 45 2014-05-10T15:42:39Z Bert 8 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transfering your account]] * [[Help, my account has been disabled]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transfering files over SFTP]] * [[Using SSHFS]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Using your webspace]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Keeping your website secure]] * [[Preventing spam on your website]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transfering files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion 101]] * [[Gitlab]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> __NOTOC__ d4e06b469ef734c8a14b1227c82cfe48b39b9b56 0 4 23 2014-05-10T10:58:42Z Warreee 10 Created page with "<p>Users can access the ULYSSIS servers through two machines: <code>ssh1.ulyssis.org</code> and <code>ssh2.ulyssis.org</code>. Both of them run Linux. You can run commands on ..." wikitext text/x-wiki <p>Users can access the ULYSSIS servers through two machines: <code>ssh1.ulyssis.org</code> and <code>ssh2.ulyssis.org</code>. Both of them run Linux. You can run commands on these servers or use them to access the files on your ULYSSIS account. The servers can only be accessed trough SSH, not through FTP or any other protocol.</p> <h2>Running commands</h2> To run a command on the shell servers, you will need to connect to them using a terminal. Our servers do not support a full graphical interface. <h3>Linux</h3> On Linux, you can just open a terminal and connect to the servers by using one of the following commands (with <code>username</code> your username): <p><code>ssh username@ssh1.ulyssis.org</code></p> <p><code>ssh username@ssh2.ulyssis.org</code></p> <p>Enter your password and you're connected. </p> <p>By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D.</p> <h3>Windows</h3> Windows doesn't support native terminals, so you will have to download a program first. A good option is [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty], which is completely free and doesn't require any installation. Just download it and run the .exe file. The parameters: <ul> <li>Host name: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Protocol: SSH</li> <li>Port: 22 (should be set automatically)</li> </ul> <p>You can save these options for later on.</p> <p>Next, you will be asked to give your password.</p> <p>Doing all this will open a terminal to the remote server which can be used the same way as a Linux terminal. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D.</p> <p>More information about Putty can be found at http://the.earth.li/~sgtatham/putty/0.60/htmldoc/. <h3> Mac </h3> On Mac, you can just open Terminal. This application can be found in the Utilities folder within your Application folder. If you don't find it there, you can use Spotlight to find it. You can now connect to the servers by using one of the following commands (with <code>username</code> your username): <p><code>ssh username@ssh1.ulyssis.org</code></p> <p><code>ssh username@ssh2.ulyssis.org</code></p> <p>Enter your password and you're connected. </p> <p>By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use ctrl+D.</p> <h3>Useful ideas</h3> Here are some useful ideas about what you could do with your shell server access: <ul> <li><a href="/docs/fetch-your-kuleuven-mail-in-gmail">Fetch your K.U.Leuven student mail in your Gmail account.</a></li> <li>Run an IRC client in a screen so you don't miss a thing.</li> </ul> <h3>Useful commands</h3> Some useful commands can be found <a href="http://ulyssis.be/docs/useful-linux-commands">here</a>. <h2>Accessing your files</h2> <p>Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for.</p> <p>On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc.</p> <h3>Graphical methods</h3> <h4> Linux </h4> Linux normally gives you the option to connect to a server graphically. On Ubuntu, in the "Places" menu, choose "Connect to server." using the following options: <ul> <li>Service type: SSH</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave this blank</li> <li>Folder: your home folder as described above (this is optional, this will save you clicking to your home folder)</li> </ul> This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. <h4> Windows </h4> Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. The parameters: <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> <h4> Mac </h4> Download the free and open source program [http://cyberduck.ch/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. <h3>Non-graphical methods</h3> <p>You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): </p> <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. 0a773bda81a602a0980112d46972768a4fa0fee2 24 23 2014-05-10T11:04:39Z Warreee 10 wikitext text/x-wiki <p>Users can access the ULYSSIS servers through two machines: <code>ssh1.ulyssis.org</code> and <code>ssh2.ulyssis.org</code>. Both of them run Linux. You can run commands on these servers or use them to access the files on your ULYSSIS account. The servers can only be accessed trough SSH, not through FTP or any other protocol.</p> <h2>Running commands</h2> To run a command on the shell servers, you will need to connect to them using a terminal. Our servers do not support a full graphical interface. <h3>Linux</h3> On Linux, you can just open a terminal and connect to the servers by using one of the following commands (with <code>username</code> your username): <p><code>ssh username@ssh1.ulyssis.org</code></p> <p><code>ssh username@ssh2.ulyssis.org</code></p> <p>Enter your password and you're connected. </p> <p>By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D.</p> <h3>Windows</h3> Windows doesn't support native terminals, so you will have to download a program first. A good option is [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty], which is completely free and doesn't require any installation. Just download it and run the .exe file. The parameters: <ul> <li>Host name: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Protocol: SSH</li> <li>Port: 22 (should be set automatically)</li> </ul> <p>You can save these options for later on.</p> <p>Next, you will be asked to give your password.</p> <p>Doing all this will open a terminal to the remote server which can be used the same way as a Linux terminal. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D.</p> <p>More information about Putty can be found at http://the.earth.li/~sgtatham/putty/0.60/htmldoc/. <h3> Mac </h3> On Mac, you can just open Terminal. This application can be found in the Utilities folder within your Application folder. If you don't find it there, you can use Spotlight to find it. You can now connect to the servers by using one of the following commands (with <code>username</code> your username): <p><code>ssh username@ssh1.ulyssis.org</code></p> <p><code>ssh username@ssh2.ulyssis.org</code></p> <p>Enter your password and you're connected. </p> <p>By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use ctrl+D.</p> <h3>Useful ideas</h3> Here are some useful ideas about what you could do with your shell server access: <ul> <li><a href="/docs/fetch-your-kuleuven-mail-in-gmail">Fetch your K.U.Leuven student mail in your Gmail account.</a></li> <li>Run an IRC client in a screen so you don't miss a thing.</li> </ul> <h3>Useful commands</h3> Some useful commands can be found <a href="http://ulyssis.be/docs/useful-linux-commands">here</a>. 4053775b6462640ea9d3293cca542e286b47bfda 27 24 2014-05-10T11:11:30Z Warreee 10 wikitext text/x-wiki <p>Users can access the ULYSSIS servers through two machines: <code>ssh1.ulyssis.org</code> and <code>ssh2.ulyssis.org</code>. Both of them run Linux. You can run commands on these servers or use them to access the files on your ULYSSIS account. The servers can only be accessed trough SSH, not through FTP or any other protocol.</p> <h2>Running commands</h2> To run a command on the shell servers, you will need to connect to them using a terminal. Our servers do not support a full graphical interface. <h3>Linux</h3> On Linux, you can just open a terminal and connect to the servers by using one of the following commands (with <code>username</code> your username): <p><code>ssh username@ssh1.ulyssis.org</code></p> <p><code>ssh username@ssh2.ulyssis.org</code></p> <p>Enter your password and you're connected. </p> <p>By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D.</p> <h3>Windows</h3> Windows doesn't support native terminals, so you will have to download a program first. A good option is [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty], which is completely free and doesn't require any installation. Just download it and run the .exe file. The parameters: <ul> <li>Host name: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Protocol: SSH</li> <li>Port: 22 (should be set automatically)</li> </ul> <p>You can save these options for later on.</p> <p>Next, you will be asked to give your password.</p> <p>Doing all this will open a terminal to the remote server which can be used the same way as a Linux terminal. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D.</p> <p>More information about Putty can be found at http://the.earth.li/~sgtatham/putty/0.60/htmldoc/. <h3> Mac </h3> On Mac, you can just open Terminal. This application can be found in the Utilities folder within your Application folder. If you don't find it there, you can use Spotlight to find it. You can now connect to the servers by using one of the following commands (with <code>username</code> your username): <p><code>ssh username@ssh1.ulyssis.org</code></p> <p><code>ssh username@ssh2.ulyssis.org</code></p> <p>Enter your password and you're connected. </p> <p>By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use ctrl+D.</p> <h3>Useful ideas</h3> Here are some useful ideas about what you could do with your shell server access: <ul> <li><a href="/docs/fetch-your-kuleuven-mail-in-gmail">Fetch your K.U.Leuven student mail in your Gmail account.</a></li> <li>Run an IRC client in a screen so you don't miss a thing.</li> </ul> <h3>Useful commands</h3> Some useful commands can be found [[Useful Linux Commands|here]]. 2a64f2a0ba1e3aa7fa4d1a5fa4a6278672f4fba5 28 27 2014-05-10T11:13:18Z Warreee 10 wikitext text/x-wiki Users can access the ULYSSIS servers through two machines: <code>ssh1.ulyssis.org</code> and <code>ssh2.ulyssis.org</code>. Both of them run Linux. You can run commands on these servers or use them to access the files on your ULYSSIS account. The servers can only be accessed trough SSH, not through FTP or any other protocol. =Running commands= To run a command on the shell servers, you will need to connect to them using a terminal. Our servers do not support a full graphical interface. ==Linux== On Linux, you can just open a terminal and connect to the servers by using one of the following commands (with <code>username</code> your username): <p><code>ssh username@ssh1.ulyssis.org</code></p> <p><code>ssh username@ssh2.ulyssis.org</code></p> <p>Enter your password and you're connected. </p> <p>By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D.</p> ==Windows== Windows doesn't support native terminals, so you will have to download a program first. A good option is [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty], which is completely free and doesn't require any installation. Just download it and run the .exe file. The parameters: <ul> <li>Host name: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Protocol: SSH</li> <li>Port: 22 (should be set automatically)</li> </ul> <p>You can save these options for later on.</p> <p>Next, you will be asked to give your password.</p> <p>Doing all this will open a terminal to the remote server which can be used the same way as a Linux terminal. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D.</p> <p>More information about Putty can be found at http://the.earth.li/~sgtatham/putty/0.60/htmldoc/. ==Mac== On Mac, you can just open Terminal. This application can be found in the Utilities folder within your Application folder. If you don't find it there, you can use Spotlight to find it. You can now connect to the servers by using one of the following commands (with <code>username</code> your username): <p><code>ssh username@ssh1.ulyssis.org</code></p> <p><code>ssh username@ssh2.ulyssis.org</code></p> <p>Enter your password and you're connected. </p> <p>By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use ctrl+D.</p> ===Useful ideas=== Here are some useful ideas about what you could do with your shell server access: <ul> <li><a href="/docs/fetch-your-kuleuven-mail-in-gmail">Fetch your K.U.Leuven student mail in your Gmail account.</a></li> <li>Run an IRC client in a screen so you don't miss a thing.</li> </ul> ===Useful commands=== Some useful commands can be found [[Useful Linux Commands|here]]. a52d425e8426f73423a960d17ec5868078155f5e 29 28 2014-05-10T11:13:40Z Warreee 10 /* Running commands */ wikitext text/x-wiki Users can access the ULYSSIS servers through two machines: <code>ssh1.ulyssis.org</code> and <code>ssh2.ulyssis.org</code>. Both of them run Linux. You can run commands on these servers or use them to access the files on your ULYSSIS account. The servers can only be accessed trough SSH, not through FTP or any other protocol. =Running commands= To run a command on the shell servers, you will need to connect to them using a terminal. Our servers do not support a full graphical interface. ==Linux== On Linux, you can just open a terminal and connect to the servers by using one of the following commands (with <code>username</code> your username): <p><code>ssh username@ssh1.ulyssis.org</code></p> <p><code>ssh username@ssh2.ulyssis.org</code></p> <p>Enter your password and you're connected. </p> <p>By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D.</p> ==Windows== Windows doesn't support native terminals, so you will have to download a program first. A good option is [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty], which is completely free and doesn't require any installation. Just download it and run the .exe file. The parameters: <ul> <li>Host name: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Protocol: SSH</li> <li>Port: 22 (should be set automatically)</li> </ul> <p>You can save these options for later on.</p> <p>Next, you will be asked to give your password.</p> <p>Doing all this will open a terminal to the remote server which can be used the same way as a Linux terminal. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D.</p> <p>More information about Putty can be found at http://the.earth.li/~sgtatham/putty/0.60/htmldoc/. ==Mac== On Mac, you can just open Terminal. This application can be found in the Utilities folder within your Application folder. If you don't find it there, you can use Spotlight to find it. You can now connect to the servers by using one of the following commands (with <code>username</code> your username): <p><code>ssh username@ssh1.ulyssis.org</code></p> <p><code>ssh username@ssh2.ulyssis.org</code></p> <p>Enter your password and you're connected. </p> <p>By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use ctrl+D.</p> =Useful ideas= Here are some useful ideas about what you could do with your shell server access: <ul> <li><a href="/docs/fetch-your-kuleuven-mail-in-gmail">Fetch your K.U.Leuven student mail in your Gmail account.</a></li> <li>Run an IRC client in a screen so you don't miss a thing.</li> </ul> =Useful commands= Some useful commands can be found [[Useful Linux Commands|here]]. b6c5b6e8dc3778d5123416fdf96804ef6e0a6296 30 29 2014-05-10T11:14:02Z Warreee 10 /* Useful ideas */ wikitext text/x-wiki Users can access the ULYSSIS servers through two machines: <code>ssh1.ulyssis.org</code> and <code>ssh2.ulyssis.org</code>. Both of them run Linux. You can run commands on these servers or use them to access the files on your ULYSSIS account. The servers can only be accessed trough SSH, not through FTP or any other protocol. =Running commands= To run a command on the shell servers, you will need to connect to them using a terminal. Our servers do not support a full graphical interface. ==Linux== On Linux, you can just open a terminal and connect to the servers by using one of the following commands (with <code>username</code> your username): <p><code>ssh username@ssh1.ulyssis.org</code></p> <p><code>ssh username@ssh2.ulyssis.org</code></p> <p>Enter your password and you're connected. </p> <p>By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D.</p> ==Windows== Windows doesn't support native terminals, so you will have to download a program first. A good option is [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty], which is completely free and doesn't require any installation. Just download it and run the .exe file. The parameters: <ul> <li>Host name: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Protocol: SSH</li> <li>Port: 22 (should be set automatically)</li> </ul> <p>You can save these options for later on.</p> <p>Next, you will be asked to give your password.</p> <p>Doing all this will open a terminal to the remote server which can be used the same way as a Linux terminal. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D.</p> <p>More information about Putty can be found at http://the.earth.li/~sgtatham/putty/0.60/htmldoc/. ==Mac== On Mac, you can just open Terminal. This application can be found in the Utilities folder within your Application folder. If you don't find it there, you can use Spotlight to find it. You can now connect to the servers by using one of the following commands (with <code>username</code> your username): <p><code>ssh username@ssh1.ulyssis.org</code></p> <p><code>ssh username@ssh2.ulyssis.org</code></p> <p>Enter your password and you're connected. </p> <p>By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use ctrl+D.</p> ==Useful ideas== Here are some useful ideas about what you could do with your shell server access: <ul> <li><a href="/docs/fetch-your-kuleuven-mail-in-gmail">Fetch your K.U.Leuven student mail in your Gmail account.</a></li> <li>Run an IRC client in a screen so you don't miss a thing.</li> </ul> =Useful commands= Some useful commands can be found [[Useful Linux Commands|here]]. ff06edc8b14be3b67043326142d60d1fd6be8c00 31 30 2014-05-10T11:14:08Z Warreee 10 /* Useful commands */ wikitext text/x-wiki Users can access the ULYSSIS servers through two machines: <code>ssh1.ulyssis.org</code> and <code>ssh2.ulyssis.org</code>. Both of them run Linux. You can run commands on these servers or use them to access the files on your ULYSSIS account. The servers can only be accessed trough SSH, not through FTP or any other protocol. =Running commands= To run a command on the shell servers, you will need to connect to them using a terminal. Our servers do not support a full graphical interface. ==Linux== On Linux, you can just open a terminal and connect to the servers by using one of the following commands (with <code>username</code> your username): <p><code>ssh username@ssh1.ulyssis.org</code></p> <p><code>ssh username@ssh2.ulyssis.org</code></p> <p>Enter your password and you're connected. </p> <p>By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D.</p> ==Windows== Windows doesn't support native terminals, so you will have to download a program first. A good option is [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty], which is completely free and doesn't require any installation. Just download it and run the .exe file. The parameters: <ul> <li>Host name: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Protocol: SSH</li> <li>Port: 22 (should be set automatically)</li> </ul> <p>You can save these options for later on.</p> <p>Next, you will be asked to give your password.</p> <p>Doing all this will open a terminal to the remote server which can be used the same way as a Linux terminal. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D.</p> <p>More information about Putty can be found at http://the.earth.li/~sgtatham/putty/0.60/htmldoc/. ==Mac== On Mac, you can just open Terminal. This application can be found in the Utilities folder within your Application folder. If you don't find it there, you can use Spotlight to find it. You can now connect to the servers by using one of the following commands (with <code>username</code> your username): <p><code>ssh username@ssh1.ulyssis.org</code></p> <p><code>ssh username@ssh2.ulyssis.org</code></p> <p>Enter your password and you're connected. </p> <p>By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use ctrl+D.</p> ==Useful ideas== Here are some useful ideas about what you could do with your shell server access: <ul> <li><a href="/docs/fetch-your-kuleuven-mail-in-gmail">Fetch your K.U.Leuven student mail in your Gmail account.</a></li> <li>Run an IRC client in a screen so you don't miss a thing.</li> </ul> ==Useful commands== Some useful commands can be found [[Useful Linux Commands|here]]. fbf86f42184744c7e8733b3be7ae59a2f848dade 32 31 2014-05-10T11:55:02Z Bert 8 wikitext text/x-wiki Users can access the ULYSSIS servers through two machines: <code>ssh1.ulyssis.org</code> and <code>ssh2.ulyssis.org</code>. Both of them run Linux. You can run commands on these servers or use them to access the files on your ULYSSIS account. The servers can only be accessed trough SSH, not through FTP or any other protocol. =Running commands= To run a command on the shell servers, you will need to connect to them using a terminal. Our servers do not support a full graphical interface. ==Linux== On Linux, you can just open a terminal and connect to the servers by using one of the following commands (with <code>username</code> your username): <code>ssh username@ssh1.ulyssis.org</code> <code>ssh username@ssh2.ulyssis.org</code> Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. ==Windows== Windows doesn't support native terminals, so you will have to download a program first. A good option is [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty], which is completely free and doesn't require any installation. Just download it and run the .exe file. The parameters: *Host name: ssh1.ulyssis.org or ssh2.ulyssis.org< *Protocol: SSH *Port: 22 (should be set automatically) You can save these options for later on. Next, you will be asked to give your password. Doing all this will open a terminal to the remote server which can be used the same way as a Linux terminal. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. More information about Putty can be found at http://the.earth.li/~sgtatham/putty/0.60/htmldoc/. ==Mac== On Mac, you can just open Terminal. This application can be found in the Utilities folder within your Application folder. If you don't find it there, you can use Spotlight to find it. You can now connect to the servers by using one of the following commands (with <code>username</code> your username): <p><code>ssh username@ssh1.ulyssis.org</code></p> <p><code>ssh username@ssh2.ulyssis.org</code></p> <p>Enter your password and you're connected. </p> <p>By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use ctrl+D.</p> ==Useful ideas== Here are some useful ideas about what you could do with your shell server access: <ul> <li><a href="/docs/fetch-your-kuleuven-mail-in-gmail">Fetch your K.U.Leuven student mail in your Gmail account.</a></li> <li>Run an IRC client in a screen so you don't miss a thing.</li> </ul> ==Useful commands== Some useful commands can be found [[Useful Linux Commands|here]]. ccbf82464969cabe40e6c72c3094d3332706fbd1 33 32 2014-05-10T11:55:15Z Bert 8 wikitext text/x-wiki Users can access the ULYSSIS servers through two machines: <code>ssh1.ulyssis.org</code> and <code>ssh2.ulyssis.org</code>. Both of them run Linux. You can run commands on these servers or use them to access the files on your ULYSSIS account. The servers can only be accessed trough SSH, not through FTP or any other protocol. =Running commands= To run a command on the shell servers, you will need to connect to them using a terminal. Our servers do not support a full graphical interface. ==Linux== On Linux, you can just open a terminal and connect to the servers by using one of the following commands (with <code>username</code> your username): <code>ssh username@ssh1.ulyssis.org</code> <code>ssh username@ssh2.ulyssis.org</code> Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. ==Windows== Windows doesn't support native terminals, so you will have to download a program first. A good option is [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty], which is completely free and doesn't require any installation. Just download it and run the .exe file. The parameters: *Host name: ssh1.ulyssis.org or ssh2.ulyssis.org< *Protocol: SSH *Port: 22 (should be set automatically) You can save these options for later on. Next, you will be asked to give your password. Doing all this will open a terminal to the remote server which can be used the same way as a Linux terminal. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. More information about Putty can be found at http://the.earth.li/~sgtatham/putty/0.60/htmldoc/. ==Mac== On Mac, you can just open Terminal. This application can be found in the Utilities folder within your Application folder. If you don't find it there, you can use Spotlight to find it. You can now connect to the servers by using one of the following commands (with <code>username</code> your username): <p><code>ssh username@ssh1.ulyssis.org</code></p> <p><code>ssh username@ssh2.ulyssis.org</code></p> <p>Enter your password and you're connected. </p> <p>By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use ctrl+D.</p> ==Useful ideas== Here are some useful ideas about what you could do with your shell server access: <ul> <li><a href="/docs/fetch-your-kuleuven-mail-in-gmail">Fetch your K.U.Leuven student mail in your Gmail account.</a></li> <li>Run an IRC client in a screen so you don't miss a thing.</li> </ul> ==Useful commands== Some useful commands can be found [[Useful Linux Commands|here]]. 583411414b3da13dc242d3c5e79b7e6135d845bb 34 33 2014-05-10T11:57:54Z Bert 8 wikitext text/x-wiki Users can access the ULYSSIS servers through two machines: <code>ssh1.ulyssis.org</code> and <code>ssh2.ulyssis.org</code>. Both of them run Linux. You can run commands on these servers or use them to access the files on your ULYSSIS account. The servers can only be accessed trough SSH, not through FTP or any other protocol. =Running commands= To run a command on the shell servers, you will need to connect to them using a terminal. Our servers do not support a full graphical interface. ==Linux== On Linux, you can just open a terminal and connect to the servers by using one of the following commands (with <code>username</code> your username): <code>ssh username@ssh1.ulyssis.org</code> <code>ssh username@ssh2.ulyssis.org</code> Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. ==Windows== Windows doesn't support native terminals, so you will have to download a program first. A good option is [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty], which is completely free and doesn't require any installation. Just download it and run the .exe file. The parameters: *Host name: ssh1.ulyssis.org or ssh2.ulyssis.org *Protocol: SSH *Port: 22 (should be set automatically) You can save these options for later on. Next, you will be asked to give your password. Doing all this will open a terminal to the remote server which can be used the same way as a Linux terminal. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. More information about Putty can be found at http://the.earth.li/~sgtatham/putty/0.60/htmldoc/. ==Mac== On Mac, you can just open Terminal. This application can be found in the Utilities folder within your Application folder. If you don't find it there, you can use Spotlight to find it. You can now connect to the servers by using one of the following commands (with <code>username</code> your username): <code>ssh username@ssh1.ulyssis.org</code> <code>ssh username@ssh2.ulyssis.org</code> Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use ctrl+D. ==Useful ideas== Here are some useful ideas about what you could do with your shell server access: *[[Accessing your files]] *[[Fetch your KU Leuven email into another email address]] *[[ULYSSIS public IRC]] ==Useful commands== Some useful commands can be found [[Useful Linux Commands|here]]. cc83d289b41d5c3b41ecfe893d86080dfc59bc88 35 34 2014-05-10T11:58:20Z Bert 8 wikitext text/x-wiki Users can access the ULYSSIS servers through two machines: <code>ssh1.ulyssis.org</code> and <code>ssh2.ulyssis.org</code>. Both of them run Linux. You can run commands on these servers or use them to access the files on your ULYSSIS account. The servers can only be accessed trough SSH, not through FTP or any other protocol. =Running commands= To run a command on the shell servers, you will need to connect to them using a terminal. Our servers do not support a full graphical interface. ==Linux== On Linux, you can just open a terminal and connect to the servers by using one of the following commands (with <code>username</code> your username): *<code>ssh username@ssh1.ulyssis.org</code> *<code>ssh username@ssh2.ulyssis.org</code> Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. ==Windows== Windows doesn't support native terminals, so you will have to download a program first. A good option is [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty], which is completely free and doesn't require any installation. Just download it and run the .exe file. The parameters: *Host name: ssh1.ulyssis.org or ssh2.ulyssis.org *Protocol: SSH *Port: 22 (should be set automatically) You can save these options for later on. Next, you will be asked to give your password. Doing all this will open a terminal to the remote server which can be used the same way as a Linux terminal. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. More information about Putty can be found at http://the.earth.li/~sgtatham/putty/0.60/htmldoc/. ==Mac== On Mac, you can just open Terminal. This application can be found in the Utilities folder within your Application folder. If you don't find it there, you can use Spotlight to find it. You can now connect to the servers by using one of the following commands (with <code>username</code> your username): <code>ssh username@ssh1.ulyssis.org</code> <code>ssh username@ssh2.ulyssis.org</code> Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use ctrl+D. ==Useful ideas== Here are some useful ideas about what you could do with your shell server access: *[[Accessing your files]] *[[Fetch your KU Leuven email into another email address]] *[[ULYSSIS public IRC]] ==Useful commands== Some useful commands can be found [[Useful Linux Commands|here]]. f765b05b5a462447e080dd2ea33f2c3e84144041 36 35 2014-05-10T11:58:50Z Bert 8 wikitext text/x-wiki Users can access the ULYSSIS servers through two machines: <code>ssh1.ulyssis.org</code> and <code>ssh2.ulyssis.org</code>. Both of them run Linux. You can run commands on these servers or use them to access the files on your ULYSSIS account. The servers can only be accessed trough SSH, not through FTP or any other protocol. =Running commands= To run a command on the shell servers, you will need to connect to them using a terminal. Our servers do not support a full graphical interface. ==Linux== On Linux, you can just open a terminal and connect to the servers by using one of the following commands (with <code>username</code> your username): <code>ssh username@ssh1.ulyssis.org</code> <code>ssh username@ssh2.ulyssis.org</code> Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. ==Windows== Windows doesn't support native terminals, so you will have to download a program first. A good option is [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty], which is completely free and doesn't require any installation. Just download it and run the .exe file. The parameters: *Host name: ssh1.ulyssis.org or ssh2.ulyssis.org *Protocol: SSH *Port: 22 (should be set automatically) You can save these options for later on. Next, you will be asked to give your password. Doing all this will open a terminal to the remote server which can be used the same way as a Linux terminal. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. More information about Putty can be found at http://the.earth.li/~sgtatham/putty/0.60/htmldoc/. ==Mac== On Mac, you can just open Terminal. This application can be found in the Utilities folder within your Application folder. If you don't find it there, you can use Spotlight to find it. You can now connect to the servers by using one of the following commands (with <code>username</code> your username): <code>ssh username@ssh1.ulyssis.org</code> <code>ssh username@ssh2.ulyssis.org</code> Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use ctrl+D. ==Useful ideas== Here are some useful ideas about what you could do with your shell server access: *[[Accessing your files]] *[[Fetch your KU Leuven email into another email address]] *[[ULYSSIS public IRC]] ==Useful commands== Some useful commands can be found [[Useful Linux Commands|here]]. de239562ca31c10987baa235a160ac4f292b0748 37 36 2014-05-10T12:00:00Z Bert 8 wikitext text/x-wiki Users can access the ULYSSIS servers through two machines: <code>ssh1.ulyssis.org</code> and <code>ssh2.ulyssis.org</code>. Both of them run Linux. You can run commands on these servers or use them to access the files on your ULYSSIS account. The servers can only be accessed trough SSH, not through FTP or any other protocol. =Running commands= To run a command on the shell servers, you will need to connect to them using a terminal. Our servers do not support a full graphical interface.Accessing your files ==Linux== On Linux, you can just open a terminal and connect to the servers by using one of the following commands (with <code>username</code> your username): <code>ssh username@ssh1.ulyssis.org</code><br /> <code>ssh username@ssh2.ulyssis.org</code> Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. ==Windows== Windows doesn't support native terminals, so you will have to download a program first. A good option is [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty], which is completely free and doesn't require any installation. Just download it and run the .exe file. The parameters: *Host name: ssh1.ulyssis.org or ssh2.ulyssis.org *Protocol: SSH *Port: 22 (should be set automatically) You can save these options for later on. Next, you will be asked to give your password. Doing all this will open a terminal to the remote server which can be used the same way as a Linux terminal. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. More information about Putty can be found at http://the.earth.li/~sgtatham/putty/0.60/htmldoc/. ==Mac== On Mac, you can just open Terminal. This application can be found in the Utilities folder within your Application folder. If you don't find it there, you can use Spotlight to find it. You can now connect to the servers by using one of the following commands (with <code>username</code> your username): <code>ssh username@ssh1.ulyssis.org</code> <code>ssh username@ssh2.ulyssis.org</code> Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use ctrl+D. ==Useful ideas== Here are some useful ideas about what you could do with your shell server access: *[[Accessing your files]] *[[Fetch your KU Leuven email into another email address]] *[[ULYSSIS public IRC]] ==Useful commands== Some useful commands can be found [[Useful Linux Commands|here]]. bd8b25e4f765b6ee77a6dacfa114448865b184eb 38 37 2014-05-10T12:00:15Z Bert 8 wikitext text/x-wiki Users can access the ULYSSIS servers through two machines: <code>ssh1.ulyssis.org</code> and <code>ssh2.ulyssis.org</code>. Both of them run Linux. You can run commands on these servers or use them to access the files on your ULYSSIS account. The servers can only be accessed trough SSH, not through FTP or any other protocol. =Running commands= To run a command on the shell servers, you will need to connect to them using a terminal. Our servers do not support a full graphical interface.Accessing your files ==Linux== On Linux, you can just open a terminal and connect to the servers by using one of the following commands (with <code>username</code> your username): <code>ssh username@ssh1.ulyssis.org</code><br /> <code>ssh username@ssh2.ulyssis.org</code> Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. ==Windows== Windows doesn't support native terminals, so you will have to download a program first. A good option is [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty], which is completely free and doesn't require any installation. Just download it and run the .exe file. The parameters: *Host name: ssh1.ulyssis.org or ssh2.ulyssis.org *Protocol: SSH *Port: 22 (should be set automatically) You can save these options for later on. Next, you will be asked to give your password. Doing all this will open a terminal to the remote server which can be used the same way as a Linux terminal. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. More information about Putty can be found at http://the.earth.li/~sgtatham/putty/0.60/htmldoc/. ==Mac== On Mac, you can just open Terminal. This application can be found in the Utilities folder within your Application folder. If you don't find it there, you can use Spotlight to find it. You can now connect to the servers by using one of the following commands (with <code>username</code> your username): <code>ssh username@ssh1.ulyssis.org</code><br /> <code>ssh username@ssh2.ulyssis.org</code> Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use ctrl+D. ==Useful ideas== Here are some useful ideas about what you could do with your shell server access: *[[Accessing your files]] *[[Fetch your KU Leuven email into another email address]] *[[ULYSSIS public IRC]] ==Useful commands== Some useful commands can be found [[Useful Linux Commands|here]]. 144528644249d687b0f3ec2600310d3e9d97191c 39 38 2014-05-10T12:00:33Z Bert 8 wikitext text/x-wiki Users can access the ULYSSIS servers through two machines: <code>ssh1.ulyssis.org</code> and <code>ssh2.ulyssis.org</code>. Both of them run Linux. You can run commands on these servers or use them to access the files on your ULYSSIS account. The servers can only be accessed trough SSH, not through FTP or any other protocol. =Running commands= To run a command on the shell servers, you will need to connect to them using a terminal. Our servers do not support a full graphical interface. ==Linux== On Linux, you can just open a terminal and connect to the servers by using one of the following commands (with <code>username</code> your username): <code>ssh username@ssh1.ulyssis.org</code><br /> <code>ssh username@ssh2.ulyssis.org</code> Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. ==Windows== Windows doesn't support native terminals, so you will have to download a program first. A good option is [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty], which is completely free and doesn't require any installation. Just download it and run the .exe file. The parameters: *Host name: ssh1.ulyssis.org or ssh2.ulyssis.org *Protocol: SSH *Port: 22 (should be set automatically) You can save these options for later on. Next, you will be asked to give your password. Doing all this will open a terminal to the remote server which can be used the same way as a Linux terminal. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. More information about Putty can be found at http://the.earth.li/~sgtatham/putty/0.60/htmldoc/. ==Mac== On Mac, you can just open Terminal. This application can be found in the Utilities folder within your Application folder. If you don't find it there, you can use Spotlight to find it. You can now connect to the servers by using one of the following commands (with <code>username</code> your username): <code>ssh username@ssh1.ulyssis.org</code><br /> <code>ssh username@ssh2.ulyssis.org</code> Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use ctrl+D. ==Useful ideas== Here are some useful ideas about what you could do with your shell server access: *[[Accessing your files]] *[[Fetch your KU Leuven email into another email address]] *[[ULYSSIS public IRC]] ==Useful commands== Some useful commands can be found [[Useful Linux Commands|here]]. bc544ee450277162a7f55f3502bd26e40605a211 0 5 25 2014-05-10T11:09:33Z Warreee 10 Created page with "=Accessing your files= Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The ..." wikitext text/x-wiki =Accessing your files= Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Linux== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in the "Places" menu, choose "Connect to server." using the following options: <ul> <li>Service type: SSH</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave this blank</li> <li>Folder: your home folder as described above (this is optional, this will save you clicking to your home folder)</li> </ul> This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. The parameters: <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> ===Mac=== Download the free and open source program [http://cyberduck.ch/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. c57ef768bb6c646d1832141c597d9af269853648 26 25 2014-05-10T11:09:52Z Warreee 10 /* =Linux */ wikitext text/x-wiki =Accessing your files= Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in the "Places" menu, choose "Connect to server." using the following options: <ul> <li>Service type: SSH</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave this blank</li> <li>Folder: your home folder as described above (this is optional, this will save you clicking to your home folder)</li> </ul> This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. The parameters: <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> ===Mac=== Download the free and open source program [http://cyberduck.ch/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. a03963a85c4dd3adf00698e3d246f2469334232e 0 6 47 2014-05-10T23:48:52Z Bert 8 Created page with "==Creating a MySQL user== To use MySQL on your ULYSSIS account you first need to create a MySQL user on [https://ucc.ulyssis.org|UCC]. In the MySQL section of the panel you wi..." wikitext text/x-wiki ==Creating a MySQL user== To use MySQL on your ULYSSIS account you first need to create a MySQL user on [https://ucc.ulyssis.org|UCC]. In the MySQL section of the panel you will be suggested to click a link to create a user. Then fill in a password for the database user. It is highly recommended that this password differs from the password you use for your account. Then you just click ''Create user'' and you are ready to go. ==Creating a MySQL database== ==Using MySQL for your website or application== ==Managing MySQL with PHPMyAdmin== ==Accessing MySQL from outside of our network== 1ccf04dc068495c1f12b5ff7c0ec1efb84e39fc5 48 47 2014-05-11T00:09:12Z Bert 8 wikitext text/x-wiki ==Creating a MySQL user== To use MySQL on your ULYSSIS account you first need to create a MySQL user on [https://ucc.ulyssis.org|UCC]. In the MySQL section of the panel you will be suggested to click a link to create a user. Then fill in a password for the database user. It is highly recommended that this password differs from the password you use for your account. Then you just click ''Create user'' and you are ready to go. ==Creating a MySQL database== After creating a MySQL user, you can simple press ''Add database'' in [https://ucc.ulyssis.org|UCC] and enter the name for your new database. It will automatically be prefixed by your username. ==Using MySQL for your website or application== Host: mysql.ulyssis.org Username: your account's username Password: the password you chose when you made the MySQL user Database: the database name you chose, prefixed by your username For example, if my username is foobar, I made a database called website and I were to create a PHP application I would use something like this: $db = new mysqli('mysql.ulyssis.org', 'foobar', 'correct horse battery staple', 'foobar_website'); $db = new PDO('mysql:host=mysql.ulyssis.org;dbname=foobar_website', 'foobar', 'correct horse battery staple'); ==Managing MySQL with PHPMyAdmin== ==Accessing MySQL from outside of our network== b74c717086c3c01cbcc695d37f31a92092f24d93 49 48 2014-05-11T00:09:48Z Bert 8 wikitext text/x-wiki ==Creating a MySQL user== To use MySQL on your ULYSSIS account you first need to create a MySQL user on [https://ucc.ulyssis.org|UCC]. In the MySQL section of the panel you will be suggested to click a link to create a user. Then fill in a password for the database user. It is highly recommended that this password differs from the password you use for your account. Then you just click ''Create user'' and you are ready to go. ==Creating a MySQL database== After creating a MySQL user, you can simple press ''Add database'' in [https://ucc.ulyssis.org|UCC] and enter the name for your new database. It will automatically be prefixed by your username. ==Using MySQL for your website or application== Host: mysql.ulyssis.org Username: your account's username Password: the password you chose when you made the MySQL user Database: the database name you chose, prefixed by your username For example, if my username is foobar, I made a database called website and I were to create a PHP application I would use something like this: $db = new mysqli('mysql.ulyssis.org', 'foobar', 'correct horse battery staple', 'foobar_website'); or $db = new PDO('mysql:host=mysql.ulyssis.org;dbname=foobar_website', 'foobar', 'correct horse battery staple'); ==Managing MySQL with PHPMyAdmin== ==Accessing MySQL from outside of our network== 24c8521a4c510b47cdb906d76ee87f8d440f039b 50 49 2014-05-11T00:12:08Z Bert 8 wikitext text/x-wiki ==Creating a MySQL user== To use MySQL on your ULYSSIS account you first need to create a MySQL user on [https://ucc.ulyssis.org|UCC]. In the MySQL section of the panel you will be suggested to click a link to create a user. Then fill in a password for the database user. It is highly recommended that this password differs from the password you use for your account. Then you just click ''Create user'' and you are ready to go. ==Creating a MySQL database== After creating a MySQL user, you can simple press ''Add database'' in [https://ucc.ulyssis.org|UCC] and enter the name for your new database. It will automatically be prefixed by your username. ==Using MySQL for your website or application== Host: mysql.ulyssis.org Username: your account's username Password: the password you chose when you made the MySQL user Database: the database name you chose, prefixed by your username For example, if my username is foobar, I made a database called website and I were to create a PHP website I would use something like: $db = new mysqli('mysql.ulyssis.org', 'foobar', 'correct horse battery staple', 'foobar_website'); or $db = new PDO('mysql:host=mysql.ulyssis.org;dbname=foobar_website', 'foobar', 'correct horse battery staple'); ==Managing MySQL with PHPMyAdmin== ==Accessing MySQL from outside of our network== 85e64fc25cc9ea6c6b6686e05865a43805a8f7db 51 50 2014-05-11T00:15:48Z Bert 8 wikitext text/x-wiki ==Creating a MySQL user== To use MySQL on your ULYSSIS account you first need to create a MySQL user on [https://ucc.ulyssis.org|UCC]. In the MySQL section of the panel you will be suggested to click a link to create a user. Then fill in a password for the database user. It is highly recommended that this password differs from the password you use for your account. Then you just click ''Create user'' and you are ready to go. ==Creating a MySQL database== After creating a MySQL user, you can simple press ''Add database'' in [https://ucc.ulyssis.org|UCC] and enter the name for your new database. It will automatically be prefixed by your username. ==Using MySQL for your website or application== Host: mysql.ulyssis.org Username: your account's username Password: the password you chose when you made the MySQL user Database: the database name you chose, prefixed by your username For example, if my username is foobar, I made a database called website and I were to create a PHP website I would use something like: $db = new mysqli('mysql.ulyssis.org', 'foobar', 'correct horse battery staple', 'foobar_website'); or $db = new PDO('mysql:host=mysql.ulyssis.org;dbname=foobar_website', 'foobar', 'correct horse battery staple');or ==Managing MySQL with PHPMyAdmin== Using your username and password you can easily manage your MySQL databases, tables and records on [https://phpmyadmin.ulyssis.org] ==Accessing MySQL from outside of our network== To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH-tunnel. In many mysql management tools this is already supported. On Linux, Mac OSX and other Unix-like Operating Systems it is also easily possible to use the following command to create a tunnel to a local port (in this case 3300) ssh -f username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N ee96974627fbc35bdf7f3812dfae6c9304085335 0 6 52 51 2014-05-11T00:16:02Z Bert 8 wikitext text/x-wiki ==Creating a MySQL user== To use MySQL on your ULYSSIS account you first need to create a MySQL user on [https://ucc.ulyssis.org|UCC]. In the MySQL section of the panel you will be suggested to click a link to create a user. Then fill in a password for the database user. It is highly recommended that this password differs from the password you use for your account. Then you just click ''Create user'' and you are ready to go. ==Creating a MySQL database== After creating a MySQL user, you can simple press ''Add database'' in [https://ucc.ulyssis.org|UCC] and enter the name for your new database. It will automatically be prefixed by your username. ==Using MySQL for your website or application== Host: mysql.ulyssis.org Username: your account's username Password: the password you chose when you made the MySQL user Database: the database name you chose, prefixed by your username For example, if my username is foobar, I made a database called website and I were to create a PHP website I would use something like: $db = new mysqli('mysql.ulyssis.org', 'foobar', 'correct horse battery staple', 'foobar_website'); or $db = new PDO('mysql:host=mysql.ulyssis.org;dbname=foobar_website', 'foobar', 'correct horse battery staple'); ==Managing MySQL with PHPMyAdmin== Using your username and password you can easily manage your MySQL databases, tables and records on [https://phpmyadmin.ulyssis.org] ==Accessing MySQL from outside of our network== To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH-tunnel. In many mysql management tools this is already supported. On Linux, Mac OSX and other Unix-like Operating Systems it is also easily possible to use the following command to create a tunnel to a local port (in this case 3300) ssh -f username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N a60945ebecd47e09f1fdf1d260905b6104dbb85f 53 52 2014-05-11T00:17:03Z Bert 8 wikitext text/x-wiki ==Creating a MySQL user== To use MySQL on your ULYSSIS account you first need to create a MySQL user on [https://ucc.ulyssis.org|UCC]. In the MySQL section of the panel you will be suggested to click a link to create a user. Then fill in a password for the database user. It is highly recommended that this password differs from the password you use for your account. Then you just click ''Create user'' and you are ready to go. ==Creating a MySQL database== After creating a MySQL user, you can simple press ''Add database'' in [https://ucc.ulyssis.org|UCC] and enter the name for your new database. It will automatically be prefixed by your username. ==Using MySQL for your website or application== Host: mysql.ulyssis.org Username: your account's username Password: the password you chose when you made the MySQL user Database: the database name you chose, prefixed by your username For example, if my username is foobar, I made a database called website and I were to create a PHP website I would use something like: $db = new mysqli('mysql.ulyssis.org', 'foobar', 'correct horse battery staple', 'foobar_website'); or $db = new PDO('mysql:host=mysql.ulyssis.org;dbname=foobar_website', 'foobar', 'correct horse battery staple'); ==Managing MySQL with PHPMyAdmin== Using your username and password you can easily manage your MySQL databases, tables and records on https://phpmyadmin.ulyssis.org ==Accessing MySQL from outside of our network== To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH-tunnel. In many mysql management tools this is already supported. On Linux, Mac OSX and other Unix-like Operating Systems it is also easily possible to use the following command to create a tunnel to a local port (in this case 3300) ssh -f username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N d4e62c3e8bab1413774ce037aff5031cc4595119 54 53 2014-05-11T00:17:18Z Bert 8 wikitext text/x-wiki ==Creating a MySQL user== To use MySQL on your ULYSSIS account you first need to create a MySQL user on [https://ucc.ulyssis.org UCC]. In the MySQL section of the panel you will be suggested to click a link to create a user. Then fill in a password for the database user. It is highly recommended that this password differs from the password you use for your account. Then you just click ''Create user'' and you are ready to go. ==Creating a MySQL database== After creating a MySQL user, you can simple press ''Add database'' in [https://ucc.ulyssis.org UCC] and enter the name for your new database. It will automatically be prefixed by your username. ==Using MySQL for your website or application== Host: mysql.ulyssis.org Username: your account's username Password: the password you chose when you made the MySQL user Database: the database name you chose, prefixed by your username For example, if my username is foobar, I made a database called website and I were to create a PHP website I would use something like: $db = new mysqli('mysql.ulyssis.org', 'foobar', 'correct horse battery staple', 'foobar_website'); or $db = new PDO('mysql:host=mysql.ulyssis.org;dbname=foobar_website', 'foobar', 'correct horse battery staple'); ==Managing MySQL with PHPMyAdmin== Using your username and password you can easily manage your MySQL databases, tables and records on https://phpmyadmin.ulyssis.org ==Accessing MySQL from outside of our network== To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH-tunnel. In many mysql management tools this is already supported. On Linux, Mac OSX and other Unix-like Operating Systems it is also easily possible to use the following command to create a tunnel to a local port (in this case 3300) ssh -f username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N 49ce5e3c62f694030ad75a9dd7f6092becb13f3c 68 54 2014-05-11T09:43:22Z Bert 8 wikitext text/x-wiki ==Creating a MySQL user== To use MySQL on your ULYSSIS account you first need to create a MySQL user on [https://ucc.ulyssis.org UCC]. In the MySQL section of the panel you will be suggested to click a link to create a user. Then fill in a password for the database user. It is highly recommended that this password differs from the password you use for your account. Then you just click ''Create user'' and you are ready to go. ==Creating a MySQL database== After creating a MySQL user, you can simple press ''Add database'' in [https://ucc.ulyssis.org UCC] and enter the name for your new database. It will automatically be prefixed by your username. ==Using MySQL for your website or application== Host: mysql.ulyssis.org Username: your account's username Password: the password you chose when you made the MySQL user Database: the database name you chose, prefixed by your username For example, if my username is foobar, I made a database called website and I were to create a PHP website I would use something like: <syntaxhighlight lang="php">$db = new mysqli('mysql.ulyssis.org', 'foobar', 'correct horse battery staple', 'foobar_website');</syntaxhighlight> or $db = new PDO('mysql:host=mysql.ulyssis.org;dbname=foobar_website', 'foobar', 'correct horse battery staple'); ==Managing MySQL with PHPMyAdmin== Using your username and password you can easily manage your MySQL databases, tables and records on https://phpmyadmin.ulyssis.org ==Accessing MySQL from outside of our network== To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH-tunnel. In many mysql management tools this is already supported. On Linux, Mac OSX and other Unix-like Operating Systems it is also easily possible to use the following command to create a tunnel to a local port (in this case 3300) ssh -f username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N fcac9c8ef9734c0639ea2cc9096be54cd283ec6f 69 68 2014-05-11T09:43:54Z Bert 8 wikitext text/x-wiki ==Creating a MySQL user== To use MySQL on your ULYSSIS account you first need to create a MySQL user on [https://ucc.ulyssis.org UCC]. In the MySQL section of the panel you will be suggested to click a link to create a user. Then fill in a password for the database user. It is highly recommended that this password differs from the password you use for your account. Then you just click ''Create user'' and you are ready to go. ==Creating a MySQL database== After creating a MySQL user, you can simple press ''Add database'' in [https://ucc.ulyssis.org UCC] and enter the name for your new database. It will automatically be prefixed by your username. ==Using MySQL for your website or application== Host: mysql.ulyssis.org Username: your account's username Password: the password you chose when you made the MySQL user Database: the database name you chose, prefixed by your username For example, if my username is foobar, I made a database called website and I were to create a PHP website I would use something like: <syntaxhighlight lang="php"> $db = new mysqli('mysql.ulyssis.org', 'foobar', 'correct horse battery staple', 'foobar_website');</syntaxhighlight> or $db = new PDO('mysql:host=mysql.ulyssis.org;dbname=foobar_website', 'foobar', 'correct horse battery staple'); ==Managing MySQL with PHPMyAdmin== Using your username and password you can easily manage your MySQL databases, tables and records on https://phpmyadmin.ulyssis.org ==Accessing MySQL from outside of our network== To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH-tunnel. In many mysql management tools this is already supported. On Linux, Mac OSX and other Unix-like Operating Systems it is also easily possible to use the following command to create a tunnel to a local port (in this case 3300) ssh -f username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N 6a44eb0710e78d7077bfb19c840a93cc8eb127d5 70 69 2014-05-11T09:44:04Z Bert 8 wikitext text/x-wiki ==Creating a MySQL user== To use MySQL on your ULYSSIS account you first need to create a MySQL user on [https://ucc.ulyssis.org UCC]. In the MySQL section of the panel you will be suggested to click a link to create a user. Then fill in a password for the database user. It is highly recommended that this password differs from the password you use for your account. Then you just click ''Create user'' and you are ready to go. ==Creating a MySQL database== After creating a MySQL user, you can simple press ''Add database'' in [https://ucc.ulyssis.org UCC] and enter the name for your new database. It will automatically be prefixed by your username. ==Using MySQL for your website or application== Host: mysql.ulyssis.org Username: your account's username Password: the password you chose when you made the MySQL user Database: the database name you chose, prefixed by your username For example, if my username is foobar, I made a database called website and I were to create a PHP website I would use something like: <syntaxhighlight lang="php"> $db = new mysqli('mysql.ulyssis.org', 'foobar', 'correct horse battery staple', 'foobar_website');</syntaxhighlight> or $db = new PDO('mysql:host=mysql.ulyssis.org;dbname=foobar_website', 'foobar', 'correct horse battery staple'); ==Managing MySQL with PHPMyAdmin== Using your username and password you can easily manage your MySQL databases, tables and records on https://phpmyadmin.ulyssis.org ==Accessing MySQL from outside of our network== To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH-tunnel. In many mysql management tools this is already supported. On Linux, Mac OSX and other Unix-like Operating Systems it is also easily possible to use the following command to create a tunnel to a local port (in this case 3300) ssh -f username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N afbed46812207fe1f08aa7d4aa2990665e11fb85 71 70 2014-05-11T09:44:27Z Bert 8 wikitext text/x-wiki ==Creating a MySQL user== To use MySQL on your ULYSSIS account you first need to create a MySQL user on [https://ucc.ulyssis.org UCC]. In the MySQL section of the panel you will be suggested to click a link to create a user. Then fill in a password for the database user. It is highly recommended that this password differs from the password you use for your account. Then you just click ''Create user'' and you are ready to go. ==Creating a MySQL database== After creating a MySQL user, you can simple press ''Add database'' in [https://ucc.ulyssis.org UCC] and enter the name for your new database. It will automatically be prefixed by your username. ==Using MySQL for your website or application== Host: mysql.ulyssis.org Username: your account's username Password: the password you chose when you made the MySQL user Database: the database name you chose, prefixed by your username For example, if my username is foobar, I made a database called website and I were to create a PHP website I would use something like: <syntaxhighlight lang="php">$db = new mysqli('mysql.ulyssis.org', 'foobar', 'correct horse battery staple', 'foobar_website');</syntaxhighlight> or <syntaxhighlight lang="php">$db = new PDO('mysql:host=mysql.ulyssis.org;dbname=foobar_website', 'foobar', 'correct horse battery staple');</syntaxhighlight> ==Managing MySQL with PHPMyAdmin== Using your username and password you can easily manage your MySQL databases, tables and records on https://phpmyadmin.ulyssis.org ==Accessing MySQL from outside of our network== To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH-tunnel. In many mysql management tools this is already supported. On Linux, Mac OSX and other Unix-like Operating Systems it is also easily possible to use the following command to create a tunnel to a local port (in this case 3300) ssh -f username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N 7af260d881713d451c19d4cf90e28276e415d401 0 7 55 2014-05-11T00:37:23Z Bert 8 Created page with "ULYSSIS hosts its own IRC server. (IRC stands for Internet Relay Chat, [http://en.wikipedia.org/wiki/Internet_Relay_Chat IRC on wikipedia]) ==Contact us on IRC== The public ..." wikitext text/x-wiki ULYSSIS hosts its own IRC server. (IRC stands for Internet Relay Chat, [http://en.wikipedia.org/wiki/Internet_Relay_Chat IRC on wikipedia]) ==Contact us on IRC== The public channel is simply called ulyssis, if you have a question, you can use IRC as a fast way to contact us. Details: Server: irc.ulyssis.org Channel: #ulyssis To use IRC you'll need an IRC client, we advise the terminal based [http://irssi.org/ irssi] for Linux (just use sudo apt-get install) and [http://www.mirc.com/ mIRC] for Windows, but there are a lot of other free options. ==Using irssi in a Screen== Our IRC server isn't very crowded and as you only see messages when you're connected, we advise you to run irssi in a screen. Members can run a screen on our shellservers, as they keep running 24/7 you can use them to keep track of your conversations. ===Connect to the shellserver=== Use the ssh command in the linux or mac terminal or PuTTY to connect on windows. Extensive information on how to do so can be found on [[Accessing shell servers over SSH]]. ===Start irssi in a screen=== *When on the shellserver, enter <code>screen</code> to start a screen. *Enter <code>irssi</code> to start irssi in that screen. *Connect to the IRC server: <code>/server irc.ulyssis.org</code> *Connect to the public channel: <code>/join #ulyssis</code> ===Screen usage=== *To exit the screen: press Ctrl-A and press D ('detach') to return to the shellserver. *To reconnect: enter <code>screen -r</code> or <code>screen -DR</code> (the latter will create a new screen if it wasn't already made). *Help I can't connect to my screen! **Check if you are on the right shellserver and didn't make a typing error. **If everything is correct, your screen may have been stopped by a crash of our shellserver. You can check the <a href="http://www.ulyssis.org/status">status</a> section of our website for more information about possible downtimes. 1334a9fe602267a3b7c993edb64658de4811584f 56 55 2014-05-11T00:38:49Z Bert 8 wikitext text/x-wiki ULYSSIS hosts its own IRC server. (IRC stands for Internet Relay Chat, [http://en.wikipedia.org/wiki/Internet_Relay_Chat IRC on wikipedia]) ==Contact us on IRC== The public channel is simply called ulyssis, if you have a question, you can use IRC as a fast way to contact us. Details: Server: irc.ulyssis.org Channel: #ulyssis To use IRC you'll need an IRC client, we advise the terminal based [http://irssi.org/ irssi] for Linux (just use sudo apt-get install) and [http://www.mirc.com/ mIRC] for Windows, but there are a lot of other free options. ==Using irssi in a Screen== Our IRC server isn't very crowded and as you only see messages when you're connected, we advise you to run irssi in a screen. Members can run a screen on our shellservers, as they keep running 24/7 you can use them to keep track of your conversations. ===Connect to the shellserver=== Use the ssh command in the linux or mac terminal or PuTTY to connect on windows. Extensive information on how to do so can be found on [[Accessing shell servers over SSH]]. ===Start irssi in a screen=== *When on the shellserver, enter <code>screen</code> to start a screen. *Enter <code>irssi</code> to start irssi in that screen. *Connect to the IRC server: <code>/server irc.ulyssis.org</code> *Connect to the public channel: <code>/join #ulyssis</code> ===Screen usage=== *To exit the screen: press Ctrl-A and press D ('detach') to return to the shellserver. *To reconnect: enter <code>screen -r</code> or <code>screen -DR</code> (the latter will create a new screen if it wasn't already made). *Help I can't connect to my screen! **Check if you are on the right shellserver and didn't make a typing error. **If everything is correct, your screen may have been stopped by a crash of our shellserver. You can check the [http://www.ulyssis.org/status status] section of our website for more information about possible downtimes. 1e9d4e61da1bbbd3dd59d88b8f3bf92a932a571d 0 8 57 2014-05-11T01:16:04Z Bert 8 Created page with "PHP errors are not displayed by default. If you want to show PHP errors you can add these line to a .htaccess file in the documentroot of your website. For example create a f..." wikitext text/x-wiki PHP errors are not displayed by default. If you want to show PHP errors you can add these line to a .htaccess file in the documentroot of your website. For example create a file ~/www/.htaccess with this content: php_value display_errors on 5f96b4a0971bdfd1f47a74fb5698dc1984844af5 66 57 2014-05-11T06:59:22Z Rockinroel 9 wikitext text/x-wiki PHP errors are not displayed by default. If an error occurs, you will simply get a blank page. This is for security reasons: this way, an attacker doesn't know about possible vulnerabilities of your website. If you want to see PHP errors, you can log them to a file, or enable the display of errors. = Logging errors to a file = If your username is ''foobar'', create a <code>.htaccess</code> file (for example: <code>~/wwww/.htaccess</code>) with this content, if you are a regular user: php_flag log_errors on php_value error_log /home/user/foobar/php_error.log Or if you are an organization: php_flag log_errors on php_value error_log /home/org/foobar/php_error.log = Displaying errors = Create a <code>.htaccess</code> file (for example: <code>~/www/.htaccess</code>) with this content: php_flag display_errors on 6ae00076567bd1a3425353205054adfd8ab9f7fd 0 9 58 2014-05-11T01:20:38Z Bert 8 Created page with "You can find all your apache logs (like the access.log and error.log) on all of our servers in the directory: /var/log/apache_user/''username'' So if your username is ''fooba..." wikitext text/x-wiki You can find all your apache logs (like the access.log and error.log) on all of our servers in the directory: /var/log/apache_user/''username'' So if your username is ''foobar'' then you can easily access your logs this way: foobar@zap:~$ cd /var/log/apache_user/foobar foobar@zap:/var/log/apache_user/foobar$ ls foobar.ulyssis.be foobar@zap:/var/log/apache_user/foobar$ cd foobar.ulyssis.be foobar@zap:/var/log/apache_user/foobar/foobar.ulyssis.be$ ls access-2014-05-07.log error-2014-05-07.log foobar@zap:/var/log/apache_user/foobar/foobar.ulyssis.be$ tail error-2014-05-07.log [Wed May 07 01:27:14 2014] [error] [client 10.0.0.1] File does not exist: /home/user/foobar/www/favicon.ico 0c20741b7cb7a532c04b5a06fce3174c3e2969c5 59 58 2014-05-11T01:20:51Z Bert 8 wikitext text/x-wiki You can find all your apache logs (like the access.log and error.log) on all of our servers in the directory: /var/log/apache_user/''username'' So if your username is ''foobar'' then you can easily access your logs this way: foobar@zap:~$ cd /var/log/apache_user/foobar <br> foobar@zap:/var/log/apache_user/foobar$ ls foobar.ulyssis.be foobar@zap:/var/log/apache_user/foobar$ cd foobar.ulyssis.be foobar@zap:/var/log/apache_user/foobar/foobar.ulyssis.be$ ls access-2014-05-07.log error-2014-05-07.log foobar@zap:/var/log/apache_user/foobar/foobar.ulyssis.be$ tail error-2014-05-07.log [Wed May 07 01:27:14 2014] [error] [client 10.0.0.1] File does not exist: /home/user/foobar/www/favicon.ico 89e218d82349b3ccab94e4e05aec41ff6100b4fa 60 59 2014-05-11T01:21:01Z Bert 8 wikitext text/x-wiki You can find all your apache logs (like the access.log and error.log) on all of our servers in the directory: /var/log/apache_user/''username'' So if your username is ''foobar'' then you can easily access your logs this way: foobar@zap:~$ cd /var/log/apache_user/foobar<br> foobar@zap:/var/log/apache_user/foobar$ ls foobar.ulyssis.be foobar@zap:/var/log/apache_user/foobar$ cd foobar.ulyssis.be foobar@zap:/var/log/apache_user/foobar/foobar.ulyssis.be$ ls access-2014-05-07.log error-2014-05-07.log foobar@zap:/var/log/apache_user/foobar/foobar.ulyssis.be$ tail error-2014-05-07.log [Wed May 07 01:27:14 2014] [error] [client 10.0.0.1] File does not exist: /home/user/foobar/www/favicon.ico e2f5c90cec60856df5cef343eda6daa26fec29ac 61 60 2014-05-11T01:21:19Z Bert 8 wikitext text/x-wiki You can find all your apache logs (like the access.log and error.log) on all of our servers in the directory: /var/log/apache_user/''username'' So if your username is ''foobar'' then you can easily access your logs this way: foobar@zap:~$ cd /var/log/apache_user/foobar<br> foobar@zap:/var/log/apache_user/foobar$ ls foobar.ulyssis.be foobar@zap:/var/log/apache_user/foobar$ cd foobar.ulyssis.be foobar@zap:/var/log/apache_user/foobar/foobar.ulyssis.be$ ls access-2014-05-07.log error-2014-05-07.log foobar@zap:/var/log/apache_user/foobar/foobar.ulyssis.be$ tail error-2014-05-07.log [Wed May 07 01:27:14 2014] [error] [client 10.0.0.1] File does not exist: /home/user/foobar/www/favicon.ico 8ba60684e64e267f3820737d6cbd9ad438cabd59 62 61 2014-05-11T01:21:26Z Bert 8 wikitext text/x-wiki You can find all your apache logs (like the access.log and error.log) on all of our servers in the directory: /var/log/apache_user/''username'' So if your username is ''foobar'' then you can easily access your logs this way: foobar@zap:~$ cd /var/log/apache_user/foobar foobar@zap:/var/log/apache_user/foobar$ ls foobar.ulyssis.be foobar@zap:/var/log/apache_user/foobar$ cd foobar.ulyssis.be foobar@zap:/var/log/apache_user/foobar/foobar.ulyssis.be$ ls access-2014-05-07.log error-2014-05-07.log foobar@zap:/var/log/apache_user/foobar/foobar.ulyssis.be$ tail error-2014-05-07.log [Wed May 07 01:27:14 2014] [error] [client 10.0.0.1] File does not exist: /home/user/foobar/www/favicon.ico 4ec1adcd6829c1374470354889628dfb62a74d5a 64 62 2014-05-11T06:45:10Z Rockinroel 9 wikitext text/x-wiki You can find all your apache logs (like the access.log and error.log) on all of our servers in the directory: /var/log/apache_user/''username'' So if your username is ''foobar'' then you can easily access your logs this way: foobar@zap:~$ cd /var/log/apache_user/foobar foobar@zap:/var/log/apache_user/foobar$ ls foobar.ulyssis.be foobar@zap:/var/log/apache_user/foobar$ cd foobar.ulyssis.be foobar@zap:/var/log/apache_user/foobar/foobar.ulyssis.be$ ls access-2014-05-07.log error-2014-05-07.log foobar@zap:/var/log/apache_user/foobar/foobar.ulyssis.be$ tail error-2014-05-07.log [Wed May 07 01:27:14 2014] [error] [client 10.0.0.1] File does not exist: /home/user/foobar/www/favicon.ico If you can't find your username inside of ''/var/log/apache_user'', don't worry. If you enter it with ''cd foobar'' it will automatically appear. 42ef155b1c0fcca4b91ce4bddb17b943debbfea1 65 64 2014-05-11T06:46:24Z Rockinroel 9 wikitext text/x-wiki You can find all your apache logs (like the access.log and error.log) on all of our servers in the directory: /var/log/apache_user/''username'' So if your username is ''foobar'' then you can easily access your logs this way: foobar@zap:~$ cd /var/log/apache_user/foobar foobar@zap:/var/log/apache_user/foobar$ ls foobar.ulyssis.be foobar@zap:/var/log/apache_user/foobar$ cd foobar.ulyssis.be foobar@zap:/var/log/apache_user/foobar/foobar.ulyssis.be$ ls access-2014-05-07.log error-2014-05-07.log foobar@zap:/var/log/apache_user/foobar/foobar.ulyssis.be$ tail error-2014-05-07.log [Wed May 07 01:27:14 2014] [error] [client 10.0.0.1] File does not exist: /home/user/foobar/www/favicon.ico If you can't find your username inside of <code>/var/log/apache_user</code>, don't worry. If you enter it with <code>cd foobar</code>, it will automatically appear. b123793157c5afc4fead6b2db817dcecf2689a0e 0 10 63 2014-05-11T01:36:01Z Bert 8 Created page with "ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide request and install a certificate from the KU Leuven is you a..." wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide request and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''Katholieke Universiteit Leuven'' or ''KU Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org 2deaccc48c79c79fc840f334bc8220afd79869d1 0 11 67 2014-05-11T09:03:51Z Rockinroel 9 Created page with "By default, your website is accessible at the following URLs: * http://''username''.ulyssis.be * http://''username''.studentenweb.org Where ''username'' is your ULYSSIS user..." wikitext text/x-wiki By default, your website is accessible at the following URLs: * http://''username''.ulyssis.be * http://''username''.studentenweb.org Where ''username'' is your ULYSSIS user name. If you wish, you can also register another domain name. ULYSSIS isn't a domain name registrar, so you'll have to use an external registrar. For example, you can find a list of all registrars for .be at [http://dns.be dns.be]. If you have registered your own domain and you want to use it with your ULYSSIS account, you need to: # Point your domain name to the following ULYSSIS nameservers: ## ns.ulyssis.student.kuleuven.be ## ns3.ulyssis.student.kuleuven.be ## Optionally: ns2.ulyssis.student.kuleuven.be # Mail us at ulyssis@ulyssis.org, with the following details: ## Your ULYSSIS username ## The domain name you registered ## The directory that you want the domain to point at. This could be your <code>www</code> folder, but any other folder within your home directory is possible. ## Whether you want to receive e-mail at that domain name via ULYSSIS. Note that we need to request this with ICTS, so this will take a while. You can find more information about DNS at http://en.wikipedia.org/wiki/Domain_Name_System. daf9c90ad8b45d1632e76b28227b18afbb13e477 0 12 72 2014-05-11T09:44:54Z Rockinroel 9 Created page with "= Creating a database = You can create one or more PostgreSQL databases in [https://ucc.ulyssis.org UCC]. The first database you create will have the same name as your usern..." wikitext text/x-wiki = Creating a database = You can create one or more PostgreSQL databases in [https://ucc.ulyssis.org UCC]. The first database you create will have the same name as your username. Subsequent databases will be prefixed with "''username''_". = Managing your database = * The easiest way to manage your database is using [https://phppgadmin.ulyssis.org phpPgAdmin]. * You can also access it via the [[Accessing shell servers over SSH|command line]] with: psql -h pgsql.ulyssis.org = Connecting to the database = You can connect to the database with the following details: * Host: <code>pgsql.ulyssis.org</code> * Login: your ULYSSIS username * Password: the PostgreSQL password you chose in UCC * Database: the database you created in UCC Note that some CMSs will assume that you use "localhost" as the host, and will hide the host option under advanced settings in the installation process. If you can't find anywhere to enter the hostname, look under advanced settings. == Connection string == If you are programming your application yourself, PostgreSQL often uses the following connection format: host=$host user=$username password=$password db=$dbname Where you replace the parts starting with <code>$</code> with the above connection details. == pg_connect == If you are using PHP's [http://www.php.net/manual/en/function.pg-connect.php pg_connect] to connect to the database, and your username is "foo", your password is "password" and your database name is "foo": <syntaxhighlight lang="php"> $connection = pg_connect("host=pgsql.ulyssi.org user=foo password=password db=foo"); </syntaxhighlight> == PDO == If you want to connect using [http://be2.php.net/manual/en/intro.pdo.php PDO], your username is "foo", your password is "password" and your database is "foo": <syntaxhighlight lang="php"> $pdo = new PDO('pgsql:host=pgsql.ulyssis.org;dbname=foo', 'foo', 'password'); </syntaxhighlight> 781ad8eaeefb882fdec539e1d2ad45ff8086e39e 73 72 2014-05-11T09:45:18Z Rockinroel 9 wikitext text/x-wiki = Creating a database = You can create one or more PostgreSQL databases in [https://ucc.ulyssis.org UCC]. The first database you create will have the same name as your username. Subsequent databases will be prefixed with "''username''_". = Managing your database = * The easiest way to manage your database is using [https://phppgadmin.ulyssis.org phpPgAdmin]. * You can also access it via the [[Accessing shell servers over SSH|command line]] with: psql -h pgsql.ulyssis.org = Connecting to the database = You can connect to the database with the following details: * Host: <code>pgsql.ulyssis.org</code> * Login: your ULYSSIS username * Password: the PostgreSQL password you chose in UCC * Database: the database you created in UCC Note that some CMSs will assume that you use "localhost" as the host, and will hide the host option under advanced settings in the installation process. If you can't find anywhere to enter the hostname, look under advanced settings. == Connection string == If you are programming your application yourself, PostgreSQL often uses the following connection format: host=$host user=$username password=$password db=$dbname Where you replace the parts starting with <code>$</code> with the above connection details. == pg_connect == If you are using PHP's [http://www.php.net/manual/en/function.pg-connect.php pg_connect] to connect to the database, and your username is "foo", your password is "password" and your database name is "foo": <syntaxhighlight lang="php"> $connection = pg_connect("host=pgsql.ulyssis.org user=foo password=password db=foo"); </syntaxhighlight> == PDO == If you want to connect using [http://be2.php.net/manual/en/intro.pdo.php PDO], your username is "foo", your password is "password" and your database is "foo": <syntaxhighlight lang="php"> $pdo = new PDO('pgsql:host=pgsql.ulyssis.org;dbname=foo', 'foo', 'password'); </syntaxhighlight> a97b1eaa444e5b76ff3f07c37ec61d1d3bd15559 79 73 2014-05-11T10:16:30Z Rockinroel 9 wikitext text/x-wiki = Creating a database = You can create one or more PostgreSQL databases in [https://ucc.ulyssis.org UCC]. The first database you create will have the same name as your username. Subsequent databases will be prefixed with "''username''_". = Managing your database = * The easiest way to manage your database is using [https://phppgadmin.ulyssis.org phpPgAdmin]. * You can also access it via the [[Accessing shell servers over SSH|command line]] with: psql -h pgsql.ulyssis.org = Connecting to the database = You can connect to the database with the following details: * Host: <code>pgsql.ulyssis.org</code> * Login: your ULYSSIS username * Password: the PostgreSQL password you chose in UCC * Database: the database you created in UCC Note that some CMSs will assume that you use "localhost" as the host, and will hide the host option under advanced settings in the installation process. If you can't find anywhere to enter the hostname, look under advanced settings. == Connection string == If you are programming your application yourself, PostgreSQL often uses the following connection format: host=$host user=$username password=$password db=$dbname Where you replace the parts starting with <code>$</code> with the above connection details. == pg_connect == If you are using PHP's [http://www.php.net/manual/en/function.pg-connect.php pg_connect] to connect to the database, and your username is "foo", your password is "password" and your database name is "foo": <syntaxhighlight lang="php"> $connection = pg_connect("host=pgsql.ulyssis.org user=foo password=password db=foo"); </syntaxhighlight> == PDO == If you want to connect using [http://be2.php.net/manual/en/intro.pdo.php PDO], your username is "foo", your password is "password" and your database is "foo": <syntaxhighlight lang="php"> $pdo = new PDO('pgsql:host=pgsql.ulyssis.org;dbname=foo', 'foo', 'password'); </syntaxhighlight> =Accessing PostgreSQL from outside of our network= To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH-tunnel. On Linux, Mac OSX and other Unix-like Operating Systems it is easily possible to use the following command to create a tunnel to a local port (in this case 5400) ssh -f username@ssh2.ulyssis.org -L 5400:pgsql.ulyssis.org:5432 -N bce8de7c1ab004017157e0d8fd73e014531216cc 80 79 2014-05-11T10:16:45Z Rockinroel 9 /* Accessing PostgreSQL from outside of our network */ wikitext text/x-wiki = Creating a database = You can create one or more PostgreSQL databases in [https://ucc.ulyssis.org UCC]. The first database you create will have the same name as your username. Subsequent databases will be prefixed with "''username''_". = Managing your database = * The easiest way to manage your database is using [https://phppgadmin.ulyssis.org phpPgAdmin]. * You can also access it via the [[Accessing shell servers over SSH|command line]] with: psql -h pgsql.ulyssis.org = Connecting to the database = You can connect to the database with the following details: * Host: <code>pgsql.ulyssis.org</code> * Login: your ULYSSIS username * Password: the PostgreSQL password you chose in UCC * Database: the database you created in UCC Note that some CMSs will assume that you use "localhost" as the host, and will hide the host option under advanced settings in the installation process. If you can't find anywhere to enter the hostname, look under advanced settings. == Connection string == If you are programming your application yourself, PostgreSQL often uses the following connection format: host=$host user=$username password=$password db=$dbname Where you replace the parts starting with <code>$</code> with the above connection details. == pg_connect == If you are using PHP's [http://www.php.net/manual/en/function.pg-connect.php pg_connect] to connect to the database, and your username is "foo", your password is "password" and your database name is "foo": <syntaxhighlight lang="php"> $connection = pg_connect("host=pgsql.ulyssis.org user=foo password=password db=foo"); </syntaxhighlight> == PDO == If you want to connect using [http://be2.php.net/manual/en/intro.pdo.php PDO], your username is "foo", your password is "password" and your database is "foo": <syntaxhighlight lang="php"> $pdo = new PDO('pgsql:host=pgsql.ulyssis.org;dbname=foo', 'foo', 'password'); </syntaxhighlight> =Accessing PostgreSQL from outside of our network= To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH-tunnel. On Linux, Mac OSX and other Unix-like Operating Systems it is easily possible to use the following command to create a tunnel to a local port (in this case 5400): ssh -f username@ssh2.ulyssis.org -L 5400:pgsql.ulyssis.org:5432 -N 6018f6c3bd6f7e6842fda714098ceaaa541a07f3 0 3 74 46 2014-05-11T09:48:28Z Rockinroel 9 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Help, my account has been disabled]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Using your webspace]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Keeping your website secure]] * [[Preventing spam on your website]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion 101]] * [[Gitlab]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> __NOTOC__ f40888ae7189f064028066fa84e18110b809e052 76 74 2014-05-11T10:10:52Z Rockinroel 9 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Help, my account has been disabled]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Using your webspace]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Keeping your website secure]] * [[Preventing spam on your website]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion 101]] * [[GitLab]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> __NOTOC__ b4187bdb6172a22737eec9cbf529935bbf37d031 84 76 2014-05-12T13:50:37Z Bert 8 /* Webserver */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Help, my account has been disabled]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Using your webspace]] * [[Using CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Keeping your website secure]] * [[Preventing spam on your website]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion 101]] * [[GitLab]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 07601ed00cd36b0c1e68a206a1947a157d58ac41 98 84 2014-06-01T09:22:30Z Rockinroel 9 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Help, my account has been disabled]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2014]] * [[Using your webspace]] * [[Using CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Keeping your website secure]] * [[Preventing spam on your website]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion 101]] * [[GitLab]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 1b6f70a227d0e01baf6265f23cccc52cd59300c5 99 98 2014-06-15T20:40:34Z Rockinroel 9 /* Webserver */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Help, my account has been disabled]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Using your webspace]] * [[Using CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Keeping your website secure]] * [[Preventing spam on your website]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion 101]] * [[GitLab]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 07601ed00cd36b0c1e68a206a1947a157d58ac41 116 99 2014-06-18T19:40:24Z Rockinroel 9 /* Webserver */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Help, my account has been disabled]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2014]] * [[Using your webspace]] * [[Using CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Keeping your website secure]] * [[Preventing spam on your website]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion 101]] * [[GitLab]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 1b6f70a227d0e01baf6265f23cccc52cd59300c5 0 13 75 2014-05-11T10:09:33Z Rockinroel 9 Created page with "If you want to use [http://git-scm.com/ git] for version control to work privately on personal projects, or collaborate with others on projects, you can use GitLab for central..." wikitext text/x-wiki If you want to use [http://git-scm.com/ git] for version control to work privately on personal projects, or collaborate with others on projects, you can use GitLab for central repositories, and for tracking bugs. = Accessing GitLab = You can access our GitLab server at https://gitlab.ulyssis.org. You can log in with your standard ULYSSIS username and password. Leave the tab at "LDAP". = Getting started with Git = If you want to get acquainted with git, these are good free resources: * [https://try.github.io Try Git]: an interactive introduction to git * [http://git-scm.com/book Pro Git]: a book that you can read for free online * [http://git-scm.com/docs The official Git reference documentation] = Guest users = Sadly, we do not provide guest user support for GitLab yet, as we do for Subversion. Everyone who works on your project will have to have their own ULYSSIS account. We plan to provide this feature some day, but not in the near future. bd42091a5688801547b81a8abec1eac6f57c4337 77 75 2014-05-11T10:11:24Z Rockinroel 9 Rockinroel moved page [[Gitlab]] to [[GitLab]] wikitext text/x-wiki If you want to use [http://git-scm.com/ git] for version control to work privately on personal projects, or collaborate with others on projects, you can use GitLab for central repositories, and for tracking bugs. = Accessing GitLab = You can access our GitLab server at https://gitlab.ulyssis.org. You can log in with your standard ULYSSIS username and password. Leave the tab at "LDAP". = Getting started with Git = If you want to get acquainted with git, these are good free resources: * [https://try.github.io Try Git]: an interactive introduction to git * [http://git-scm.com/book Pro Git]: a book that you can read for free online * [http://git-scm.com/docs The official Git reference documentation] = Guest users = Sadly, we do not provide guest user support for GitLab yet, as we do for Subversion. Everyone who works on your project will have to have their own ULYSSIS account. We plan to provide this feature some day, but not in the near future. bd42091a5688801547b81a8abec1eac6f57c4337 0 14 78 2014-05-11T10:11:24Z Rockinroel 9 Rockinroel moved page [[Gitlab]] to [[GitLab]] wikitext text/x-wiki #REDIRECT [[GitLab]] 54e078e6e6356fdf327606460501f938c4e2613d 0 15 81 2014-05-11T12:56:11Z Robin5210 12 Created page with "=Transferring your account= You can transfer the account of your (faculty) organization to a new webmaster. The new webmaster must have a valid Centrale KULeuven Login. Other..." wikitext text/x-wiki =Transferring your account= You can transfer the account of your (faculty) organization to a new webmaster. The new webmaster must have a valid Centrale KULeuven Login. Otherwise the new webmaster can not accept the account transfer. The instructions below must be executed by the current account owner. * Login into [https://ucc.ulyssis.org/ UCC]. * Choose 'Transfer account' in the menu on the right. * Enter the details of the new account owner. (Make sure you type the KULeuven email address correct!) The new owner will get an email to confirm the transfer. adbd42c0c358d922a6664ca9712268b34001da07 82 81 2014-05-11T12:57:00Z Robin5210 12 wikitext text/x-wiki You can transfer the account of your (faculty) organization to a new webmaster. The new webmaster must have a valid Centrale KULeuven Login. Otherwise the new webmaster can not accept the account transfer. The instructions below must be executed by the current account owner. * Login into [https://ucc.ulyssis.org/ UCC]. * Choose 'Transfer account' in the menu on the right. * Enter the details of the new account owner. (Make sure you type the KULeuven email address correct!) The new owner will get an email to confirm the transfer. f174717b6e6e76d9d7ffb963e861413898370724 83 82 2014-05-11T12:57:26Z Robin5210 12 wikitext text/x-wiki You can transfer the account of your (faculty) organization to a new webmaster. The new webmaster must have a valid Centrale KU Leuven Login. Otherwise the new webmaster can not accept the account transfer. The instructions below must be executed by the current account owner. * Login into [https://ucc.ulyssis.org/ UCC]. * Choose 'Transfer account' in the menu on the right. * Enter the details of the new account owner. (Make sure you type the KULeuven email address correct!) The new owner will get an email to confirm the transfer. 744a73e54d8eb54d8c18bf5f0859e1b80232154e 0 16 85 2014-05-12T17:26:00Z Robin5210 12 Created page with "Once you've connected, you can use these commands to use the ULYSSIS shell. First of all, whenever you need to type a longer command or filename, try the TAB key as it will t..." wikitext text/x-wiki Once you've connected, you can use these commands to use the ULYSSIS shell. First of all, whenever you need to type a longer command or filename, try the TAB key as it will try to complete the name of the command or file you are typing. Pressing TAB twice will show a list of possible completions. A more extensive document on this can be found at http://info.ee.surrey.ac.uk/Teaching/Unix/. ==Basic file managment== <code>cd directoryname</code> Change directory. Works the same as under MS-DOS. cd without argument changes to your home directory (like My Documents in windows). Go to the parent directory with <code>cd ..</code> <code>ls</code> List the contents of the current directory. Many different formats are available, a common one is <code>ls -al</code>. To accomodate MS-DOS/Windows users, <code>dir</code> is an alias (synonym) for <code>ls -alF</code>, which gives output similar to the <code>dir</code> command in MS-DOS/Windows. <code>cp inputfile targetfile</code> Copy inputfile to targetfile. Additional arguments (e.g. -r or -v are explained in the man-page.) <code>mv inputfile targetfile</code> Move inputfile to targetfile. Additional arguments (e.g. -i or -v are explained in the man-page.) This is the way to rename a file. Note that you cannot use a construction like mv *.htm *.html to add an ``l'' to a bunch of files. A small shell script can provide a way to do this: <code>for i in *.htm; do mv i; done</code> <code>rm filename</code> Remove filename. Additional arguments (e.g. -r or -v are explained in the man-page.) Note: there is no undelete-alike function in most unices. <code>mkdir dirname</code> Creates a directory called dirname. <code>rmdir dirname</code> Removes an empty directory. Use rm -r to delete a directory and recursively everything in it. Add -f to disable any prompts (dangerous!). ==Getting help== <code>man command-name</code> Displays manual pages, if available. E.g. man ls. Use 'q' to exit. Relatives: apropos, help. <code>apropos word</code> Searches through headers of all man pages. <code>help command-name</code> Displays help about command-name. Only for internal bash-functions. <code>bash</code> The Bourne Again SHell. Widely used successor of sh, the Bourne shell. This is the program you're working under after you open a ssh-session (you don't have to start it to use it). Bash interprets your commands, and executes them. Tab-completion, * and ? expansions, etc are all bash functions. man bash will give you tons of info about it. Alternatives : tcsh, zsh, rc ==Text editors== It's easier to use a text editor on a server, than editing your file locally and uploading that file. <code>pico</code> or <code>nano</code> Probably the easiest text editor. Should be self-explanatory. <code>joe</code> Another easy text editor. Press Ctrl+C to quit. <code>vim</code> Probably the best text editor. Start editing by pressing <code>i</code>. Stop editing by pressing the <code>escape</code> key. Save and quit with <code>:wq</code>. Quit without saving with <code>:q!</code>. ==Utilities== <code>df</code> Displays info about the free diskspace on the system. df . will give info about the filesystem where the current directory resides. The output becomes a bit more readable with the -h switch. <code>du</code> Displays info about the diskusage in the current directory (and its subdirectories. A common parameter is -s , equivalent to -summarize , to summarize the disk-usage (without the per-subdir totals). <code>quota</code> Displays info about your diskusage, and your disk quota. Quota are limits on diskusage, imposed by the system administrator. The system will warn you if you exceed these limits. <code>ps</code> Displays info about processes. Various options possible, for example ps auxf gives info on all processes, including process owner, memory usage, and parent-child indication. <code>htop</code> Displays top CPU processes. Use it to see what gets most cpu power at the moment. Don't leave top open for a long time, since it eats cpu time itself. (quit with 'q'). 12f93b5290b1fa38d5a6bfd5854c8e4232d03cc7 86 85 2014-05-12T17:27:17Z Robin5210 12 wikitext text/x-wiki Once you've connected, you can use these commands to use the ULYSSIS shell. First of all, whenever you need to type a longer command or filename, try the <code>TAB</code> key as it will try to complete the name of the command or file you are typing. Pressing <code>TAB</code> twice will show a list of possible completions. A more extensive document on this can be found at http://info.ee.surrey.ac.uk/Teaching/Unix/. ==Basic file managment== <code>cd directoryname</code> Change directory. Works the same as under MS-DOS. cd without argument changes to your home directory (like My Documents in windows). Go to the parent directory with <code>cd ..</code> <code>ls</code> List the contents of the current directory. Many different formats are available, a common one is <code>ls -al</code>. To accomodate MS-DOS/Windows users, <code>dir</code> is an alias (synonym) for <code>ls -alF</code>, which gives output similar to the <code>dir</code> command in MS-DOS/Windows. <code>cp inputfile targetfile</code> Copy inputfile to targetfile. Additional arguments (e.g. -r or -v are explained in the man-page.) <code>mv inputfile targetfile</code> Move inputfile to targetfile. Additional arguments (e.g. -i or -v are explained in the man-page.) This is the way to rename a file. Note that you cannot use a construction like mv *.htm *.html to add an ``l'' to a bunch of files. A small shell script can provide a way to do this: <code>for i in *.htm; do mv i; done</code> <code>rm filename</code> Remove filename. Additional arguments (e.g. -r or -v are explained in the man-page.) Note: there is no undelete-alike function in most unices. <code>mkdir dirname</code> Creates a directory called dirname. <code>rmdir dirname</code> Removes an empty directory. Use rm -r to delete a directory and recursively everything in it. Add -f to disable any prompts (dangerous!). ==Getting help== <code>man command-name</code> Displays manual pages, if available. E.g. man ls. Use 'q' to exit. Relatives: apropos, help. <code>apropos word</code> Searches through headers of all man pages. <code>help command-name</code> Displays help about command-name. Only for internal bash-functions. <code>bash</code> The Bourne Again SHell. Widely used successor of sh, the Bourne shell. This is the program you're working under after you open a ssh-session (you don't have to start it to use it). Bash interprets your commands, and executes them. Tab-completion, * and ? expansions, etc are all bash functions. man bash will give you tons of info about it. Alternatives : tcsh, zsh, rc ==Text editors== It's easier to use a text editor on a server, than editing your file locally and uploading that file. <code>pico</code> or <code>nano</code> Probably the easiest text editor. Should be self-explanatory. <code>joe</code> Another easy text editor. Press Ctrl+C to quit. <code>vim</code> Probably the best text editor. Start editing by pressing <code>i</code>. Stop editing by pressing the <code>escape</code> key. Save and quit with <code>:wq</code>. Quit without saving with <code>:q!</code>. ==Utilities== <code>df</code> Displays info about the free diskspace on the system. df . will give info about the filesystem where the current directory resides. The output becomes a bit more readable with the -h switch. <code>du</code> Displays info about the diskusage in the current directory (and its subdirectories. A common parameter is -s , equivalent to -summarize , to summarize the disk-usage (without the per-subdir totals). <code>quota</code> Displays info about your diskusage, and your disk quota. Quota are limits on diskusage, imposed by the system administrator. The system will warn you if you exceed these limits. <code>ps</code> Displays info about processes. Various options possible, for example ps auxf gives info on all processes, including process owner, memory usage, and parent-child indication. <code>htop</code> Displays top CPU processes. Use it to see what gets most cpu power at the moment. Don't leave top open for a long time, since it eats cpu time itself. (quit with 'q'). 20f5c31c4af3cc3a23b268e9a27ff7f00d13e41f 0 17 87 2014-05-13T15:52:05Z W29 13 Created page with "<p>You can use our shell-servers to forward mails from your KULeuven mailbox to an email provider of your choice (e.g. GMail).</p> <p>DOING THIS IS ENTIRELY ON YOUR OWN RISK. ..." wikitext text/x-wiki <p>You can use our shell-servers to forward mails from your KULeuven mailbox to an email provider of your choice (e.g. GMail).</p> <p>DOING THIS IS ENTIRELY ON YOUR OWN RISK. ULYSSIS CANNOT BE HELD RESPONSIBLE FOR LOST/DELAY MAILS. BY HAVING OUR SERVERS FORWARD YOUR KULEUVEN MAIL, YOU TAKE FULL RESPONSIBILITY.</p> <p>This tutorial is based on http://ronin.ulyssis.be/files/kulmail_gmail2.txt</p> <p>We wrote a script that configures everything automatically. To use it, log in on one of our shell servers and execute the following commands:</p> <ul> <li>wget ftp://ftp.ulyssis.org/kulforward/kulforwardsetup.sh</li> <li>chmod u+x kulforwardsetup.sh</li> <li>./kulforwardsetup.sh</li> <li>Follow the instructions on the screen.</li> </ul> <p>Alternatively, you can configure everything yourself. Below we briefly explain how to do this.</p> <ul> <li>Create a directory to save the SSL certificates:<br />mkdir .certs</li> <li>Put the necessary certificates in the .certs directory:<br />cd .certs<br />wget ftp://ftp.ulyssis.org/kulforward/imapkul.pem<br />wget ftp://ftp.ulyssis.org/kulforward/usertrust.pem<br />cp /etc/ssl/certs/AddTrust_External_Root.pem .<br />cd </li> <li>Rehash them:<br />c_rehash ~/.certs/</li> <li>Create the fetchmail configuration file with your favourite text editor and enter the confiration details:<br /> $login = your KULeuven login (e.g. s0123456)<br /> $pass = your KULeuven password<br /> $mail = the email address to forward your KULeuven mail to (TRIPLECHECK IT!!)<br /> keep = "" (delete forwarded mails from your KULeuven mailbox) or "keep" (keep forwarded emails)<br /> set daemon 600 # Check every 10 minutes<br /> poll imaps.student.kuleuven.be port 993 protocol imap username "$login" password "$pass" smtpname "$mail" ssl sslcertck $keep sslcertpath .certs/</li> <li>Add it to your crontab<br /> crontab -e<br /> @reboot fetchmail </li> <li>Because of our setup fetchmail cannot be started automatically when the shell server is restarted. But you if you add it to your crontab, you'll get email that it failed. You can then manually login on our shell servers to start fetchmail again.</li> <li>Start fetchmail:<br /> fetchmail</li> </ul> bbe4be7a99abfd3ceed2dc9718e82166cf1cf2ff 0 19 96 2014-05-23T14:21:30Z Robin5210 12 Created page with "Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mail regularly, because all important information..." wikitext text/x-wiki Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mail regularly, because all important information will be sent to this address. You can check your e-mail using the webmail or an email client of your own. ==Webmail== You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to enter the website. ==POP and IMAP access== You can access your ulyssis mail by POP or IMAP protocol. The configuration parameters are: * '''server''': mail.ulyssis.org * '''username''': ''your username'' * '''security''': SSL 03f86609567c7ef4ead3ce7e5dd018738c45419d 0 20 97 2014-05-23T16:49:59Z Robin5210 12 Created page with "==Wordpress installeren gaat zeker gemakkelijk op onze servers== Je downloadt het installatiebestand van de [http://http://wordpress.org wordpress-site]. Hierbij krijg je ee..." wikitext text/x-wiki ==Wordpress installeren gaat zeker gemakkelijk op onze servers== Je downloadt het installatiebestand van de [http://http://wordpress.org wordpress-site]. Hierbij krijg je een gecomprimeerd bestand (.tar.gz of .zip) dit pak je uit. Je krijgt dan een map met bestanden, deze bestanden (en dus niet de map) kopieer je via filezilla of een ander ftp programma naar je www-map op je shellaccount. Hierna surf je naar je account, dus naar username.ulyssis.be, je krijgt hier een melding dat je je wp-config.php nog moet aanmaken, het gemakkelijkste is gewoon de wizard blijven volgen, klik dus op: ''Create a Configuration File''. Daarna op ''Let's go!'' waarna je gegevens van je database gaat moeten invullen: * '''Database Name: '''als je nog geen mysql database of user hebt aangemaakt op UCC dan moet je dat daar doen. De standaard database is dan: username_username. * '''User Name: '''dit is de naam die je hebt opgegven tijdens het maken van je mysql account, vaak is deze hetzelfde als je gebruikersnaam bij ULYSSIS. * '''Password: '''het wachtwoord dat je hebt opgegven bij de aanmaak van je mysql account * '''Database Host: '''dit is <code>mysql.ulyssis.org</code> * Het laatste veld verander je niet. Vervolgens krijg je de volgende error: ''Sorry, but I can’t write the <code>wp-config.php</code> file.'' Maar geen paniek, de tekst die WordPress gemaakt heeft is hetgene wat we nodig hebben. Kopieer deze tekst, sla dit op in een bestand <code>wp-config.php</code>. Dit bestand zet je dan weer via Filezilla over naar je www-directory. Klik hierna op ''Run The install.'' Hier kan je dan de laatste gegevens invullen. Daarna zal de installatie zichzelf uitvoeren en voilà, je hebt wordpress geïnstalleerd. a950a4666cbdde58e43f1fab1e3521c2b31b823f 114 97 2014-06-18T11:13:16Z Warreee 10 wikitext text/x-wiki ==Wordpress installeren gaat zeker gemakkelijk op onze servers== Je downloadt het installatiebestand van de [http://wordpress.org wordpress-site]. Hierbij krijg je een gecomprimeerd bestand (.tar.gz of .zip) dit pak je uit. Je krijgt dan een map met bestanden, deze bestanden (en dus niet de map) kopieer je via filezilla of een ander ftp programma naar je www-map op je shellaccount. Hierna surf je naar je account, dus naar username.ulyssis.be, je krijgt hier een melding dat je je wp-config.php nog moet aanmaken, het gemakkelijkste is gewoon de wizard blijven volgen, klik dus op: ''Create a Configuration File''. Daarna op ''Let's go!'' waarna je gegevens van je database gaat moeten invullen: * '''Database Name: '''als je nog geen mysql database of user hebt aangemaakt op UCC dan moet je dat daar doen. De standaard database is dan: username_username. * '''User Name: '''dit is de naam die je hebt opgegven tijdens het maken van je mysql account, vaak is deze hetzelfde als je gebruikersnaam bij ULYSSIS. * '''Password: '''het wachtwoord dat je hebt opgegven bij de aanmaak van je mysql account * '''Database Host: '''dit is <code>mysql.ulyssis.org</code> * Het laatste veld verander je niet. Vervolgens krijg je de volgende error: ''Sorry, but I can’t write the <code>wp-config.php</code> file.'' Maar geen paniek, de tekst die WordPress gemaakt heeft is hetgene wat we nodig hebben. Kopieer deze tekst, sla dit op in een bestand <code>wp-config.php</code>. Dit bestand zet je dan weer via Filezilla over naar je www-directory. Klik hierna op ''Run The install.'' Hier kan je dan de laatste gegevens invullen. Daarna zal de installatie zichzelf uitvoeren en voilà, je hebt wordpress geïnstalleerd. ==Setting up multiple instance of Wordpress== If you want to have multiple instances of a Wordpress site then you the create a new folder in your homedir from you shell account. Then you make a new virtual host for this directory in UCC. Name: alias.username.ulyssis.be Document root: /home/user/username/new_folder From now on you do al the same steps as for a regular wordpress installation. 1c3b618806eca597e8dc6cd14c248bbd8259a706 6 24 105 2014-06-16T17:54:38Z Rockinroel 9 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 25 106 2014-06-16T17:54:56Z Rockinroel 9 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 26 107 2014-06-16T17:55:12Z Rockinroel 9 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 27 108 2014-06-16T17:55:26Z Rockinroel 9 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 29 121 2014-06-22T00:02:33Z Bert 8 Created page with "To register an account you can follow these easy steps: * Go to https://ucc.ulyssis.org/accounts and login using your Central KU Leuven Account * Select the kind of account y..." wikitext text/x-wiki To register an account you can follow these easy steps: * Go to https://ucc.ulyssis.org/accounts and login using your Central KU Leuven Account * Select the kind of account you wish to register ** Most people will want to register a regular account for personal use ** If you are a recognised faculty union, assembly or representational organisation you are entitled to this free account. We verify this using the list of recognised "kringen" of LOKO. Recognised organisations are not entitled to a free account. ** If you are a Recognised organisation by LOKO, Studentenraad KU Leuven or the KU Leuven itself you are entitled to an organisation account, this account has a reduced price. * After picking your account type you have to chose what options you want, and choose a username and language. * Next you need to accept the ULYSSIS terms of use and confirm your order. * An email will be sent to your KU Leuven emailaddress to confirm your order and with a request for payment. * As soon as we have received and processed your payment your account will be activated and you will receive instructions to set a password. 90bc342d21600a5f46d4d7f62711578070f8b3fe 123 121 2014-06-22T10:46:00Z Bert 8 wikitext text/x-wiki To register an account you can follow these easy steps: * Go to https://ucc.ulyssis.org/accounts and login using your Central KU Leuven Account * Select the kind of account you wish to register ** Most people will want to register a *regular account* for *personal use* ** If you are a recognised faculty union, assembly or representational organisation you are entitled to this free account. We verify this using the list of recognised "kringen" of LOKO. Recognised organisations are not entitled to a free account. ** If you are a Recognised organisation by LOKO, Studentenraad KU Leuven or the KU Leuven itself you are entitled to an organisation account, this account has a reduced price. * After picking your account type you have to chose what options you want, and choose a username and language. * Next you need to accept the ULYSSIS terms of use and confirm your order. * An email will be sent to your KU Leuven emailaddress to confirm your order and with a request for payment. * As soon as we have received and processed your payment your account will be activated and you will receive instructions to set a password. 9e189f67c79215b36e266ada2097841f095d0049 124 123 2014-06-22T10:47:30Z Bert 8 wikitext text/x-wiki To register an account you can follow these easy steps: * Go to https://ucc.ulyssis.org/accounts and login using your Central KU Leuven Account * Select the kind of account you wish to register ** Most people will want to register a '''regular account''' for '''personal use''' ** If you are a recognised '''faculty''' union, assembly or representational organisation you are entitled to this free account. We verify this using the list of '''recognised "kringen"''' of LOKO, http://loko.be/verenigingen/ . Recognised organisations are not entitled to a free account. ** If you are a '''Recognised organisation''' by LOKO, Studentenraad KU Leuven or the KU Leuven itself you are entitled to an organisation account, this account has a reduced price. * After picking your account type you have to chose what options you want, and choose a username and language. * Next you need to accept the ULYSSIS terms of use and confirm your order. * An email will be sent to your KU Leuven emailaddress to confirm your order and with a request for payment. * As soon as we have received and processed your payment your account will be activated and you will receive instructions to set a password. af2c56076bfc50e877ee08607f5beb29a7df96ea 0 30 122 2014-06-22T00:25:17Z Bert 8 Created page with "3 weeks before your account expires you will start receiving emails reminding you to renew your account. These will continue until your account expires. To renew your account..." wikitext text/x-wiki 3 weeks before your account expires you will start receiving emails reminding you to renew your account. These will continue until your account expires. To renew your account you visit https://ucc.ulyssis.org/accounts and, while making sure you are not logged into a ULYSSIS Account, login using the Central KU Leuven Login and select your account (the renewal option will only be available if the account is in the renewal period of 3 weeks or has expired already). * Select your account option, you are free to upgrade your personal account to a higher tier now * Verify your personal information (in case of errors please contact ULYSSIS) * Accept the terms of use * Confirm your order * An email will be sent to your KU Leuven emailaddress to confirm your order and with a request for payment. * As soon as we have received and processed your payment your account will get renewed, you will receive a notification. * If you are running late with your payment and you wish to prevent your account from getting expired you can contact ULYSSIS with a screenshot or scan that confirms the payment, we will then temporarily renew your account and verify that the money arrives within the near future. 470a8935cc143ffffc280e25d705a7a771e99701 0 20 129 114 2014-06-22T14:20:07Z Rockinroel 9 /* Setting up multiple instance of Wordpress */ wikitext text/x-wiki ==Wordpress installeren gaat zeker gemakkelijk op onze servers== Je downloadt het installatiebestand van de [http://wordpress.org wordpress-site]. Hierbij krijg je een gecomprimeerd bestand (.tar.gz of .zip) dit pak je uit. Je krijgt dan een map met bestanden, deze bestanden (en dus niet de map) kopieer je via filezilla of een ander ftp programma naar je www-map op je shellaccount. Hierna surf je naar je account, dus naar username.ulyssis.be, je krijgt hier een melding dat je je wp-config.php nog moet aanmaken, het gemakkelijkste is gewoon de wizard blijven volgen, klik dus op: ''Create a Configuration File''. Daarna op ''Let's go!'' waarna je gegevens van je database gaat moeten invullen: * '''Database Name: '''als je nog geen mysql database of user hebt aangemaakt op UCC dan moet je dat daar doen. De standaard database is dan: username_username. * '''User Name: '''dit is de naam die je hebt opgegven tijdens het maken van je mysql account, vaak is deze hetzelfde als je gebruikersnaam bij ULYSSIS. * '''Password: '''het wachtwoord dat je hebt opgegven bij de aanmaak van je mysql account * '''Database Host: '''dit is <code>mysql.ulyssis.org</code> * Het laatste veld verander je niet. Vervolgens krijg je de volgende error: ''Sorry, but I can’t write the <code>wp-config.php</code> file.'' Maar geen paniek, de tekst die WordPress gemaakt heeft is hetgene wat we nodig hebben. Kopieer deze tekst, sla dit op in een bestand <code>wp-config.php</code>. Dit bestand zet je dan weer via Filezilla over naar je www-directory. Klik hierna op ''Run The install.'' Hier kan je dan de laatste gegevens invullen. Daarna zal de installatie zichzelf uitvoeren en voilà, je hebt wordpress geïnstalleerd. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site then you the create a new folder in your homedir from you shell account. Then you make a new virtual host for this directory in UCC. Name: alias.username.ulyssis.be Document root: /home/user/username/new_folder From now on you do al the same steps as for a regular wordpress installation. 78b537e38ee5d8c00f0ea2a7be68398f163a0847 130 129 2014-06-22T14:20:33Z Rockinroel 9 /* Setting up multiple instances of Wordpress */ wikitext text/x-wiki ==Wordpress installeren gaat zeker gemakkelijk op onze servers== Je downloadt het installatiebestand van de [http://wordpress.org wordpress-site]. Hierbij krijg je een gecomprimeerd bestand (.tar.gz of .zip) dit pak je uit. Je krijgt dan een map met bestanden, deze bestanden (en dus niet de map) kopieer je via filezilla of een ander ftp programma naar je www-map op je shellaccount. Hierna surf je naar je account, dus naar username.ulyssis.be, je krijgt hier een melding dat je je wp-config.php nog moet aanmaken, het gemakkelijkste is gewoon de wizard blijven volgen, klik dus op: ''Create a Configuration File''. Daarna op ''Let's go!'' waarna je gegevens van je database gaat moeten invullen: * '''Database Name: '''als je nog geen mysql database of user hebt aangemaakt op UCC dan moet je dat daar doen. De standaard database is dan: username_username. * '''User Name: '''dit is de naam die je hebt opgegven tijdens het maken van je mysql account, vaak is deze hetzelfde als je gebruikersnaam bij ULYSSIS. * '''Password: '''het wachtwoord dat je hebt opgegven bij de aanmaak van je mysql account * '''Database Host: '''dit is <code>mysql.ulyssis.org</code> * Het laatste veld verander je niet. Vervolgens krijg je de volgende error: ''Sorry, but I can’t write the <code>wp-config.php</code> file.'' Maar geen paniek, de tekst die WordPress gemaakt heeft is hetgene wat we nodig hebben. Kopieer deze tekst, sla dit op in een bestand <code>wp-config.php</code>. Dit bestand zet je dan weer via Filezilla over naar je www-directory. Klik hierna op ''Run The install.'' Hier kan je dan de laatste gegevens invullen. Daarna zal de installatie zichzelf uitvoeren en voilà, je hebt wordpress geïnstalleerd. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site then you the create a new folder in your homedir from your shell account. Then you make a new virtual host for this directory in UCC. Name: alias.username.ulyssis.be Document root: /home/user/username/new_folder From now on you do al the same steps as for a regular wordpress installation. fa3378d8a2fae2b0bebe63f6e4223fce5eb2c611 0 13 131 77 2014-06-23T19:14:03Z Rockinroel 9 wikitext text/x-wiki If you want to use [http://git-scm.com/ git] for version control to work privately on personal projects, or collaborate with others on projects, you can use GitLab for central repositories, and for tracking bugs. = Accessing GitLab = You can access our GitLab server at https://gitlab.ulyssis.org. You can log in with your standard ULYSSIS username and password. = Getting started with Git = If you want to get acquainted with git, these are good free resources: * [https://try.github.io Try Git]: an interactive introduction to git * [http://git-scm.com/book Pro Git]: a book that you can read for free online * [http://git-scm.com/docs The official Git reference documentation] = Guest users = Sadly, we do not provide guest user support for GitLab yet, as we do for Subversion. Everyone who works on your project will have to have their own ULYSSIS account. We plan to provide this feature some day, but not in the near future. f4d9aea687a7acb54d3a37a0c2ef59d53ea380f1 0 3 132 116 2014-07-08T16:55:30Z Bert 8 /* Webserver */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Help, my account has been disabled]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2014]] * [[Using your webspace]] * [[Using CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Keeping your website secure]] * [[Preventing spam on your website]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion 101]] * [[GitLab]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 715887dc2e30568947598c5b18e6dc3b6a215cf0 139 132 2014-08-08T12:28:20Z Drickx 16 /* Mail */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Help, my account has been disabled]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2014]] * [[Using your webspace]] * [[Using CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Keeping your website secure]] * [[Preventing spam on your website]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Alias toevoegen in Gmail]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion 101]] * [[GitLab]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 9e97af0de74aa2dcb6ff2cebec446ac4378a595e 149 139 2014-08-08T20:55:43Z Rockinroel 9 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Help, my account has been disabled]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2014]] * [[Using your webspace]] * [[Using CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Keeping your website secure]] * [[Preventing spam on your website]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Add an alias in Gmail]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion 101]] * [[GitLab]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 54c061bf04a28335d4cd6a2dc531e75010b3407b 0 32 133 2014-07-09T01:40:27Z Bert 8 Created page with "Just like PHP errors, you can set PHP options you would normally set in php.ini using .htaccess. You just add the option preceded by php_flag and follow by the value: php_va..." wikitext text/x-wiki Just like PHP errors, you can set PHP options you would normally set in php.ini using .htaccess. You just add the option preceded by php_flag and follow by the value: php_value upload_max_filesize 20M php_value post_max_size 25M php_value memory_limit 32M You can of course also use the [[http://be2.php.net/manual/en/function.ini-set.php|ini_set]] function. 2ec473ec079fe24ec9f3152e05a6843855114eff 134 133 2014-07-09T01:40:40Z Bert 8 wikitext text/x-wiki Just like PHP errors, you can set PHP options you would normally set in php.ini using .htaccess. You just add the option preceded by php_flag and follow by the value: php_value upload_max_filesize 20M php_value post_max_size 25M php_value memory_limit 32M You can of course also use the [[http://be2.php.net/manual/en/function.ini-set.php | ini_set]] function. 8aaf1fd7aa2c7fa08f78b8860c2f36bd042eeae7 135 134 2014-07-09T01:40:53Z Bert 8 wikitext text/x-wiki Just like PHP errors, you can set PHP options you would normally set in php.ini using .htaccess. You just add the option preceded by php_flag and follow by the value: php_value upload_max_filesize 20M php_value post_max_size 25M php_value memory_limit 32M You can of course also use the [http://be2.php.net/manual/en/function.ini-set.php | ini_set] function. e12b287f7978aae2f534b21e3e31cbd3480bfea8 136 135 2014-07-09T01:41:00Z Bert 8 wikitext text/x-wiki Just like PHP errors, you can set PHP options you would normally set in php.ini using .htaccess. You just add the option preceded by php_flag and follow by the value: php_value upload_max_filesize 20M php_value post_max_size 25M php_value memory_limit 32M You can of course also use the [http://be2.php.net/manual/en/function.ini-set.php ini_set] function. 4ed1c79813b5ccab5d5ced326a59862da2b91f86 0 33 137 2014-07-09T02:01:19Z Bert 8 Created page with "Shibboleth is the software powering the Central KU Leuven Login. It's a piece of software used by many universities to supply identification and access management. ULYSSIS w..." wikitext text/x-wiki Shibboleth is the software powering the Central KU Leuven Login. It's a piece of software used by many universities to supply identification and access management. ULYSSIS works together with ICTS to supply limited access to Shibboleth. We are however only able to supply Shibboleth to those approved by ICTS. In practice all faculty unions will be granted access if they can prove they have the technical ability to use Shibboleth in a safe and privacy friendly way. For other organisations it can be more difficult to get access, therefore it is best to write an extensive explenation of what you plan to do with Shibboleth, why your organisation requires it, what your organisation does, and other relevant information. We will then contact ICTS with your request. == Deploying Shibboleth == After you have been granted access you can soon start using Shibboleth. The first step is to add the following lines to your .htaccess ShibDisable Off AuthType Shibboleth require shibboleth ShibRequireSession off We disable certain features of Shibboleth here because it will otherwise interfere with any other HTTP-auth options you might be using. Now that you have added this information to .htaccess you are able to serve requests to Shibboleth.sso, if your request is well-formed the sso will handle communication with the IdP (identity provider) of the KU Leuven. A login link follows the following syntax: https://[YOUR_HOSTNAME]/Shibboleth.sso/WAYF/kuleuven?target=[URLENCODED_RETURN_URL] And logout links: https://[YOUR_HOSTNAME]/Shibboleth.sso/Logout?return=[URLENCODED_DISPLAY_URL] It is important to note that on logout the user will stay on the KU Leuven's IdP-page and your link will only be displayed. The user will NOT be redirected (even though this is the normale behaviour according to the Shibboleth documentation). As soon as a user is logged in, his or hers attributes will be available to your application. Attributes are certain properties that an account may have and that supply further information about them. Some examples are: first name, last name, mail, student id. All of these will be available as HTTP headers. But keep in mind that apache might prefix those with REDIRECT_ multiple times (for example when mod_rewrite is used). For an overview of all attributes you can check out http://shib.kuleuven.be/secure/allAttributes More general information on the KU Leuvens implementation can be found on http://shib.kuleuven.be/ . But be aware of the fact that some of the documentation is very outdated (some of it is about shib 1.3, while we now use shib 2.x) dedcf64f890ce5132ef450366c75162a426e09f2 138 137 2014-07-09T02:02:06Z Bert 8 wikitext text/x-wiki Shibboleth is the software powering the Central KU Leuven Login. It's a piece of software used by many universities to supply identification and access management. ULYSSIS works together with ICTS to supply limited access to Shibboleth. We are however only able to supply Shibboleth to those approved by ICTS. In practice all faculty unions will be granted access if they can prove they have the technical ability to use Shibboleth in a safe and privacy friendly way. For other organisations it can be more difficult to get access, therefore it is best to write an extensive explenation of what you plan to do with Shibboleth, why your organisation requires it, what your organisation does, and other relevant information. We will then contact ICTS with your request. == Deploying Shibboleth == After you have been granted access you can soon start using Shibboleth. The first step is to add the following lines to your .htaccess ShibDisable Off AuthType Shibboleth require shibboleth ShibRequireSession off We disable certain features of Shibboleth here because it will otherwise interfere with any other HTTP-auth options you might be using. Now that you have added this information to .htaccess you are able to serve requests to Shibboleth.sso, if your request is well-formed the sso will handle communication with the IdP (identity provider) of the KU Leuven. A login link follows the following syntax: https://[YOUR_HOSTNAME]/Shibboleth.sso/WAYF/kuleuven?target=[URLENCODED_RETURN_URL] And logout links: https://[YOUR_HOSTNAME]/Shibboleth.sso/Logout?return=[URLENCODED_DISPLAY_URL] It is important to note that on logout the user will stay on the KU Leuven's IdP-page and your link will only be displayed. The user will NOT be redirected (even though this is the normale behaviour according to the Shibboleth documentation). As soon as a user is logged in, his or hers attributes will be available to your application. Attributes are certain properties that an account may have and that supply further information about them. Some examples are: first name, last name, mail, student id. All of these will be available as HTTP headers. But keep in mind that apache might prefix those with REDIRECT_ multiple times (for example when mod_rewrite is used). For an overview of all attributes you can check out http://shib.kuleuven.be/secure/allAttributes More general information on the KU Leuvens implementation can be found on http://shib.kuleuven.be/ . But be aware of the fact that some of the documentation is very outdated (Most notably information about shib 1.3) 0a12cbd52376e8d67f3fb4545b2d8cd848e985a3 0 34 140 2014-08-08T12:36:55Z Drickx 16 Created page with "1) druk in Gmal op het tandwiel rechtsboven om naar de instellingen te gaan. 2) ga vervolgens naar het tabblad "Accounts en import" 3) druk hier bij "E-mailberichten sturen va..." wikitext text/x-wiki 1) druk in Gmal op het tandwiel rechtsboven om naar de instellingen te gaan. 2) ga vervolgens naar het tabblad "Accounts en import" 3) druk hier bij "E-mailberichten sturen vanaf" op "Nog een e-mailadres toevoegen waarvan je eigenaar bent" 4) voeg hier de naam van het emailaccount en het emailadres in, en vink het vinkje "Beschouwen als alias." af (meer informatie hierover: http://support.google.com/mail/bin/answer.py?ctx=gmail&answer=1710338&hl=nl&authuser=0) Druk vervolgens op "Volgende stap". 5) SMTP informatie: - SMTP server: smtp.kuleuven.be - port: 587 - username: studentennummer - paswoord: wachtwoord_studentennummer Druk op "Account toevoegen". 2fce23fe454cc881273dd2e64a182d61f8470f60 141 140 2014-08-08T12:40:36Z Drickx 16 wikitext text/x-wiki * druk in Gmal op het tandwiel rechtsboven om naar '''Instellingen''' te gaan. * ga vervolgens naar het tabblad '''Accounts en import''' * druk hier bij '''E-mailberichten sturen vanaf''' op '''Nog een e-mailadres toevoegen waarvan je eigenaar bent''' * voeg hier de naam van het emailaccount en het emailadres in, en vink het vinkje '''Beschouwen als alias.''' af (meer informatie hierover: http://support.google.com/mail/bin/answer.py?ctx=gmail&answer=1710338&hl=nl&authuser=0) Druk vervolgens op '''Volgende stap'''. * SMTP informatie: ** '''SMTP server''': smtp.kuleuven.be ** '''port''': 587 ** '''username''': studentennummer ** '''paswoord''': wachtwoord_studentennummer Druk op '''Account toevoegen'''. edf46a73671b3be1fe17be2aba50a8713f9ea96d 142 141 2014-08-08T12:55:39Z Drickx 16 wikitext text/x-wiki * in Gmail, go to '''Instellingen'''. * go to the tab '''Accounts en import''' * press here underneath '''E-mailberichten sturen vanaf''' on '''Nog een e-mailadres toevoegen waarvan je eigenaar bent''' * fill in your name and mail address and check off '''Beschouwen als alias.''' (more information: http://support.google.com/mail/bin/answer.py?ctx=gmail&answer=1710338&hl=nl&authuser=0) Press than on '''Volgende stap'''. * SMTP information: ** '''SMTP server''': smtps.kuleuven.be ** '''port''': 443 ** '''username''': studentennummer ** '''paswoord''': wachtwoord_studentennummer ** SSL Press on '''Account toevoegen'''. 09c75a83a2de9633344f5187e7946187c652a771 143 142 2014-08-08T12:56:49Z Drickx 16 wikitext text/x-wiki * in Gmail, go to '''Instellingen'''. * go to the tab '''Accounts en import''' * press here underneath '''E-mailberichten sturen vanaf''' on '''Nog een e-mailadres toevoegen waarvan je eigenaar bent''' * fill in your name and mail address and check off '''Beschouwen als alias.''' (more information: http://support.google.com/mail/bin/answer.py?ctx=gmail&answer=1710338&hl=nl&authuser=0) Press than on '''Volgende stap'''. * SMTP information (https://admin.kuleuven.be/icts/services/email/begrippen): ** '''SMTP server''': smtps.kuleuven.be ** '''port''': 443 or 465 ** '''username''': studentennummer ** '''paswoord''': wachtwoord_studentennummer ** SSL Press on '''Account toevoegen'''. 2db16ece546b9469d474c5cd9536f87cbf4ffa98 144 143 2014-08-08T13:05:02Z Drickx 16 wikitext text/x-wiki * in Gmail, go to '''Instellingen'''. * go to the tab '''Accounts en import''' * press here underneath '''E-mailberichten sturen vanaf''' on '''Nog een e-mailadres toevoegen waarvan je eigenaar bent''' * fill in your name and mail address and check off '''Beschouwen als alias.''' (more information: http://support.google.com/mail/bin/answer.py?ctx=gmail&answer=1710338&hl=nl&authuser=0) Press then on '''Volgende stap'''. * SMTP information (https://admin.kuleuven.be/icts/services/email/begrippen): ** '''SMTP server''': smtps.kuleuven.be ** '''port''': 443 or 465 ** '''username''': studentennummer ** '''paswoord''': wachtwoord_studentennummer ** SSL Press on '''Account toevoegen'''. 3af10049760c387cdc6b4e4a0a6ef3c1fb558308 145 144 2014-08-08T13:08:00Z Drickx 16 wikitext text/x-wiki * in Gmail, go to '''Instellingen'''. * go to the tab '''Accounts en import''' * press here underneath '''E-mailberichten sturen vanaf''' on '''Nog een e-mailadres toevoegen waarvan je eigenaar bent''' * fill in your name and mail address and check off '''Beschouwen als alias.''' (more information: http://support.google.com/mail/bin/answer.py?ctx=gmail&answer=1710338&hl=nl&authuser=0) Press then on '''Volgende stap'''. * SMTP information (https://admin.kuleuven.be/icts/services/email/begrippen): ** '''SMTP server''': smtp.kuleuven.be ** '''port''': 465 ** '''username''': studentennummer ** '''paswoord''': '''paswoord''' ** SSL Press on '''Account toevoegen'''. 6e96d68a3bdff76cba9e6a67129d1d173c7b19c4 146 145 2014-08-08T13:09:51Z Drickx 16 wikitext text/x-wiki * in Gmail, go to '''Instellingen'''. * go to the tab '''Accounts en import''' * press here underneath '''E-mailberichten sturen vanaf''' on '''Nog een e-mailadres toevoegen waarvan je eigenaar bent''' * fill in your name and mail address and check off '''Beschouwen als alias.''' (more information: http://support.google.com/mail/bin/answer.py?ctx=gmail&answer=1710338&hl=nl&authuser=0) Press then on '''Volgende stap'''. * SMTP information (https://admin.kuleuven.be/icts/services/email/begrippen): ** '''SMTP server''': '''smtp.kuleuven.be''' or '''smtps.kuleuven.be''' ** '''port''': 443 or 465 ** '''username''': studentennumber ** '''paswoord''': password_of_studentnumber or simply '''paswoord''' ** SSL Press on '''Account toevoegen'''. bbb7b4107961778b173325148e1d69e6bec53395 147 146 2014-08-08T20:55:18Z Rockinroel 9 Rockinroel moved page [[Alias toevoegen in Gmail]] to [[Add an alias in Gmail]] wikitext text/x-wiki * in Gmail, go to '''Instellingen'''. * go to the tab '''Accounts en import''' * press here underneath '''E-mailberichten sturen vanaf''' on '''Nog een e-mailadres toevoegen waarvan je eigenaar bent''' * fill in your name and mail address and check off '''Beschouwen als alias.''' (more information: http://support.google.com/mail/bin/answer.py?ctx=gmail&answer=1710338&hl=nl&authuser=0) Press then on '''Volgende stap'''. * SMTP information (https://admin.kuleuven.be/icts/services/email/begrippen): ** '''SMTP server''': '''smtp.kuleuven.be''' or '''smtps.kuleuven.be''' ** '''port''': 443 or 465 ** '''username''': studentennumber ** '''paswoord''': password_of_studentnumber or simply '''paswoord''' ** SSL Press on '''Account toevoegen'''. bbb7b4107961778b173325148e1d69e6bec53395 150 147 2014-08-08T21:03:44Z Rockinroel 9 wikitext text/x-wiki * In Gmail, go to '''Settings''' (in Dutch: '''Instellingen'''). * Go to the tab '''Accounts and Import''' (in Dutch: '''Accounts en import''') * Under '''Send mail as:''' ('''E-mailberichten sturen vanaf'''), click on: '''Add another email address you own''' ('''Nog een e-mailadres toevoegen waarvan je eigenaar bent'''). * Fill in your name and the e-mail address, and check '''Treat as an alias.''' ('''Beschouwen als alias.''') More info: https://support.google.com/a/answer/1710338 * Click on '''Next step''' ('''Volgende stap'''). * Fill in the following information SMTP information (https://admin.kuleuven.be/icts/services/email/begrippen): ** '''SMTP server''': '''smtp.kuleuven.be''' or '''smtps.kuleuven.be''' ** '''port''': 443 or 465 ** '''Username''': your student id ** '''Password''': password_of_studentnumber or simply '''paswoord''' ** SSL Press on '''Add Account''' ('''Account toevoegen'''). 7398b9cad1f89598687cd2e04f0d77d5f697fd32 151 150 2014-08-09T10:13:28Z Rockinroel 9 wikitext text/x-wiki * In Gmail, go to '''Settings''' (in Dutch: '''Instellingen'''). * Go to the tab '''Accounts and Import''' (in Dutch: '''Accounts en import''') * Under '''Send mail as:''' ('''E-mailberichten sturen vanaf'''), click on: '''Add another email address you own''' ('''Nog een e-mailadres toevoegen waarvan je eigenaar bent'''). * Fill in your name and the e-mail address, and check '''Treat as an alias.''' ('''Beschouwen als alias.''') More info: https://support.google.com/a/answer/1710338 * Click on '''Next step''' ('''Volgende stap'''). * Fill in the following information SMTP information (https://admin.kuleuven.be/icts/services/email/begrippen): ** '''SMTP server''': '''smtp.kuleuven.be''' or '''smtps.kuleuven.be''' ** '''port''': 443 or 465 ** '''Username''': your student id ** '''Password''': your KU Leuven password ** SSL Press on '''Add Account''' ('''Account toevoegen'''). a7a504fad28f459e194b7b30cff65eb1406a4ec7 152 151 2014-08-09T10:14:17Z Rockinroel 9 wikitext text/x-wiki * In Gmail, go to '''Settings''' (in Dutch: '''Instellingen'''). * Go to the tab '''Accounts and Import''' (in Dutch: '''Accounts en import''') * Under '''Send mail as:''' ('''E-mailberichten sturen vanaf'''), click on: '''Add another email address you own''' ('''Nog een e-mailadres toevoegen waarvan je eigenaar bent'''). * Fill in your name and the e-mail address, and check '''Treat as an alias.''' ('''Beschouwen als alias.''') More info: https://support.google.com/a/answer/1710338 * Click on '''Next step''' ('''Volgende stap'''). * Fill in the following information SMTP information (https://admin.kuleuven.be/icts/services/email/begrippen): ** '''SMTP server''': '''smtps.kuleuven.be''' ** '''port''': 465 ** '''Username''': your student id ** '''Password''': your KU Leuven password ** SSL Press on '''Add Account''' ('''Account toevoegen'''). 9fb4ffcf28f7129777fb5c8bc8f7b6fda6f85f9e 153 152 2014-08-09T10:15:36Z Rockinroel 9 wikitext text/x-wiki # In Gmail, go to '''Settings''' (in Dutch: '''Instellingen'''). # Go to the tab '''Accounts and Import''' (in Dutch: '''Accounts en import''') # Under '''Send mail as:''' ('''E-mailberichten sturen vanaf'''), click on: '''Add another email address you own''' ('''Nog een e-mailadres toevoegen waarvan je eigenaar bent'''). # Fill in your name and the e-mail address, and check '''Treat as an alias.''' ('''Beschouwen als alias.''') More info: https://support.google.com/a/answer/1710338 # Click on '''Next step''' ('''Volgende stap'''). # Fill in the following information SMTP information (https://admin.kuleuven.be/icts/services/email/begrippen): #* '''SMTP server''': '''smtps.kuleuven.be''' #* '''port''': 465 #* '''Username''': your student id #* '''Password''': your KU Leuven password #* SSL # Press on '''Add Account''' ('''Account toevoegen'''). de4f580fc56b6a7635409a4f4e3ed1fe798fb0f4 154 153 2014-08-09T10:17:48Z Rockinroel 9 wikitext text/x-wiki You may want to send e-mail from Gmail using your @ulyssis.org-address, or another domain name that you use for your account. Gmail allows you to do this, but asks for SMTP info. We don't provide SMTP on our own mail server, but you can use the SMTP servers of the KU Leuven. # In Gmail, go to '''Settings''' (in Dutch: '''Instellingen'''). # Go to the tab '''Accounts and Import''' (in Dutch: '''Accounts en import''') # Under '''Send mail as:''' ('''E-mailberichten sturen vanaf'''), click on: '''Add another email address you own''' ('''Nog een e-mailadres toevoegen waarvan je eigenaar bent'''). # Fill in your name and the e-mail address, and check '''Treat as an alias.''' ('''Beschouwen als alias.''') More info: https://support.google.com/a/answer/1710338 # Click on '''Next step''' ('''Volgende stap'''). # Fill in the following information SMTP information (https://admin.kuleuven.be/icts/services/email/begrippen): #* '''SMTP server''': '''smtps.kuleuven.be''' #* '''port''': 465 #* '''Username''': your student id #* '''Password''': your KU Leuven password #* SSL # Press on '''Add Account''' ('''Account toevoegen'''). cc83f8e6081513e0dae3f3e8f9105c04f9e7b9d2 155 154 2014-08-10T12:17:14Z Drickx 16 wikitext text/x-wiki You may want to send e-mail from Gmail using your @ulyssis.org-address, or another domain name that you use for your account. Gmail allows you to do this, but asks for SMTP info. We don't provide SMTP on our own mail server, but you can use the SMTP servers of the KU Leuven. # In Gmail, go to '''Settings''' (in Dutch: '''Instellingen'''). # Go to the tab '''Accounts and Import''' (in Dutch: '''Accounts en import''') # Under '''Send mail as:''' ('''E-mailberichten sturen vanaf'''), click on: '''Add another email address you own''' ('''Nog een e-mailadres toevoegen waarvan je eigenaar bent'''). # Fill in your name and the e-mail address, and check '''Treat as an alias.''' ('''Beschouwen als alias.''') More info: https://support.google.com/a/answer/1710338 # Click on '''Next step''' ('''Volgende stap'''). # Fill in the following information SMTP information (https://admin.kuleuven.be/icts/services/email/begrippen): #* '''SMTP server''': '''smtp.kuleuven.be''' #* '''port''': 465 #* '''Username''': your student id #* '''Password''': your KU Leuven password #* SSL # Press on '''Add Account''' ('''Account toevoegen'''). 2fb15de76047edd2844e147494dd5c1b3f285637 0 35 148 2014-08-08T20:55:18Z Rockinroel 9 Rockinroel moved page [[Alias toevoegen in Gmail]] to [[Add an alias in Gmail]] wikitext text/x-wiki #REDIRECT [[Add an alias in Gmail]] 22a7205e6a851979ef444677d2211fee17d080d8 0 10 156 63 2014-08-14T12:48:46Z Bert 8 wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''Katholieke Universiteit Leuven'' or ''KU Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org c480db87e2a56a071c64bc0fc18df4608a0ef1d5 157 156 2014-08-14T12:49:26Z Bert 8 wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''Katholieke Universiteit Leuven'' or ''KU Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org c165bb1710c023b903148eff0f6d07eb9f5f5339 0 36 158 2014-08-26T13:09:36Z W29 13 Created page with "=Transferring your files over SFTP= ULYSSIS doesn't support ftp, because it is insecure. However, we support sftp (ftp over ssh). This works similar as ssh. On the server, y..." wikitext text/x-wiki =Transferring your files over SFTP= ULYSSIS doesn't support ftp, because it is insecure. However, we support sftp (ftp over ssh). This works similar as ssh. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Non-graphical methods== The most common way to transfer files is with a terminal by using the <code>scp</code> command.<br/> Copying file to host:<br> <code>scp SourceFile user@host:directory/TargetFile</code><br> Copying file from host:<br> <code>scp user@host:directory/SourceFile TargetFile scp -r user@host:directory/SourceFolder TargetFolder</code> You don't need to use the full path to your file. You may you the relative path, starting from your home directory. For example:<br> <code>scp index.html user@ssh1.ulyssis.org:www/index.html</code> ==Graphical methods== The graphical methods are explained in [[Accessing your files]]. 36493f6d8410f76b60b972cb0a64d3dbcebae1b3 160 158 2014-08-26T13:11:16Z W29 13 /* Transferring your files over SFTP */ wikitext text/x-wiki ULYSSIS doesn't support ftp, because it is insecure. However, we support sftp (ftp over ssh). This works similar as ssh. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Non-graphical methods== The most common way to transfer files is with a terminal by using the <code>scp</code> command.<br/> Copying file to host:<br> <code>scp SourceFile user@host:directory/TargetFile</code><br> Copying file from host:<br> <code>scp user@host:directory/SourceFile TargetFile scp -r user@host:directory/SourceFolder TargetFolder</code> You don't need to use the full path to your file. You may you the relative path, starting from your home directory. For example:<br> <code>scp index.html user@ssh1.ulyssis.org:www/index.html</code> ==Graphical methods== The graphical methods are explained in [[Accessing your files]]. 38c7070090551e3eac3e50f775282d47fb4c2c6b 0 5 159 26 2014-08-26T13:11:00Z W29 13 /* Accessing your files */ wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in the "Places" menu, choose "Connect to server." using the following options: <ul> <li>Service type: SSH</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave this blank</li> <li>Folder: your home folder as described above (this is optional, this will save you clicking to your home folder)</li> </ul> This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. The parameters: <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> ===Mac=== Download the free and open source program [http://cyberduck.ch/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. aa1d06f58708775290d48cfc0179171fde9fab22 0 19 161 96 2014-08-30T14:48:30Z Rockinroel 9 wikitext text/x-wiki Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mail regularly, because all important information will be sent to this address. You can check your e-mail using the webmail or an email client of your own. ==Webmail== You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to enter the website. ==POP and IMAP access== You can access your ulyssis mail by POP or IMAP protocol. The configuration parameters are: * '''server''': <tt>mail.ulyssis.org</tt> * '''username''': ''your username'' * '''security''': SSL ==SMTP== ULYSSIS doesn't offer SMTP. Instead, you can use the KULeuven's SMTP server: * '''server''': <tt>smtp.ulyssis.be</tt> * '''port''': 465 * '''username''': your student id * '''password''': your KULeuven password * '''security''': SSL cf9fa25925e197937dc2a6cae9bd26656441e9fc 162 161 2014-08-30T14:49:09Z Rockinroel 9 wikitext text/x-wiki Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mail regularly, because all important information will be sent to this address. You can check your e-mail using the webmail or an email client of your own. ==Webmail== You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to enter the website. ==POP and IMAP access== You can access your ulyssis mail by POP or IMAP protocol. The configuration parameters are: * '''server''': <tt>mail.ulyssis.org</tt> * '''username''': ''your username'' * '''security''': SSL ==SMTP== ULYSSIS doesn't offer SMTP. Instead, you can use KULeuven's SMTP server: * '''server''': <tt>smtp.ulyssis.be</tt> * '''port''': 465 * '''username''': your student id * '''password''': your KULeuven password * '''security''': SSL b2feeaa599e7d48c892b4b595b7efbf8377c9b4b 163 162 2014-08-30T14:50:53Z Rockinroel 9 /* POP and IMAP access */ wikitext text/x-wiki Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mail regularly, because all important information will be sent to this address. You can check your e-mail using the webmail or an email client of your own. ==Webmail== You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to enter the website. ==POP and IMAP access== You can access your ulyssis mail by POP or IMAP protocol. The configuration parameters are: * '''server''': <tt>mail.ulyssis.org</tt> * '''username''': ''your ULYSSIS username'' * '''password''': ''your ULYSSIS password'' * '''security''': SSL ==SMTP== ULYSSIS doesn't offer SMTP. Instead, you can use KULeuven's SMTP server: * '''server''': <tt>smtp.ulyssis.be</tt> * '''port''': 465 * '''username''': your student id * '''password''': your KULeuven password * '''security''': SSL 8d78c441bd18d86be72c00fdcd2e85d7da0bb8ba 164 163 2014-08-30T14:51:09Z Rockinroel 9 /* SMTP */ wikitext text/x-wiki Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mail regularly, because all important information will be sent to this address. You can check your e-mail using the webmail or an email client of your own. ==Webmail== You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to enter the website. ==POP and IMAP access== You can access your ulyssis mail by POP or IMAP protocol. The configuration parameters are: * '''server''': <tt>mail.ulyssis.org</tt> * '''username''': ''your ULYSSIS username'' * '''password''': ''your ULYSSIS password'' * '''security''': SSL ==SMTP== ULYSSIS doesn't offer SMTP. Instead, you can use KULeuven's SMTP server: * '''server''': <tt>smtp.ulyssis.be</tt> * '''port''': 465 * '''username''': ''your student id'' * '''password''': ''your KULeuven password'' * '''security''': SSL 54786f148dfd4353f7136ffd94cbcfb874b3e7ac 0 37 165 2014-08-30T15:22:15Z Rockinroel 9 Created page with "You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI s..." wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. ==CGI== CGI is a very easy and simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. d74d673a528fb72880636c28b399a36be88494d1 166 165 2014-08-30T16:48:02Z Rockinroel 9 /* FastCGI */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. ==CGI== CGI is a very easy and simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> </li> <li> Install flup for FastCGI: <pre>pip install flup</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre> Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os sys.path.insert(0, '/home/user/username/mysite') os.chdir('/home/user/username/mysite') os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' from django.core.servers.fastcgi import runfastcgi runfastcgi(method="threaded", daemonize="false") </pre> </li> </ol> 9fb833b7a9d2df35c01bed2e93f6b986af1f45be 167 166 2014-08-30T16:50:02Z Rockinroel 9 wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. ==CGI== CGI is a very easy and simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre> Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os sys.path.insert(0, '/home/user/username/mysite') os.chdir('/home/user/username/mysite') os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' from django.core.servers.fastcgi import runfastcgi runfastcgi(method="threaded", daemonize="false")</pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> </ol> d427d260cd18bef0db6868299f962ec6165d02c5 168 167 2014-08-30T16:51:56Z Rockinroel 9 /* Example: Django */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. ==CGI== CGI is a very easy and simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre> Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os sys.path.insert(0, '/home/user/username/mysite') os.chdir('/home/user/username/mysite') os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' from django.core.servers.fastcgi import runfastcgi runfastcgi(method="threaded", daemonize="false")</pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> d1a2e5579d2fb8e1f44506dbc244c43f0d8bdfa1 169 168 2014-08-30T16:55:02Z Rockinroel 9 /* Example: Django */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. ==CGI== CGI is a very easy and simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre> Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os sys.path.insert(0, '/home/user/username/mysite') os.chdir('/home/user/username/mysite') os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' from django.core.servers.fastcgi import runfastcgi runfastcgi(method="threaded", daemonize="false")</pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/1.6/intro/tutorial01/ The Django tutorial] * [https://docs.djangoproject.com/en/1.6/howto/deployment/fastcgi/#apache-shared-hosting Running Django on a shared-hosting provider with Apache] 0bb5a9533381c657442be003c6731cf0fb3acc28 170 169 2014-08-30T16:55:20Z Rockinroel 9 wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. ==CGI== CGI is a very easy and simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre> Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os sys.path.insert(0, '/home/user/username/mysite') os.chdir('/home/user/username/mysite') os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' from django.core.servers.fastcgi import runfastcgi runfastcgi(method="threaded", daemonize="false")</pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/1.6/intro/tutorial01/ The Django tutorial] * [https://docs.djangoproject.com/en/1.6/howto/deployment/fastcgi/#apache-shared-hosting Running Django on a shared-hosting provider with Apache] df5cb01aee3706c25e9973dc84b42a2cb2d3ce82 171 170 2014-08-30T16:59:07Z Rockinroel 9 /* FastCGI */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. ==CGI== CGI is a very easy and simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. In order to do that, you have to set the modification date of the starter script to a more recent date: <pre>touch starter.fcgi</pre> ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre> Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os sys.path.insert(0, '/home/user/username/mysite') os.chdir('/home/user/username/mysite') os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' from django.core.servers.fastcgi import runfastcgi runfastcgi(method="threaded", daemonize="false")</pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/1.6/intro/tutorial01/ The Django tutorial] * [https://docs.djangoproject.com/en/1.6/howto/deployment/fastcgi/#apache-shared-hosting Running Django on a shared-hosting provider with Apache] 3ffe0983d00092bb267a1245fe19da5890596364 172 171 2014-08-30T17:00:43Z Rockinroel 9 /* FastCGI */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. ==CGI== CGI is a very easy and simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. In order to do that, you have to set the modification date of the starter script to a more recent date: <pre>touch starter.fcgi</pre> ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre> Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os sys.path.insert(0, '/home/user/username/mysite') os.chdir('/home/user/username/mysite') os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' from django.core.servers.fastcgi import runfastcgi runfastcgi(method="threaded", daemonize="false")</pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/1.6/intro/tutorial01/ The Django tutorial] * [https://docs.djangoproject.com/en/1.6/howto/deployment/fastcgi/#apache-shared-hosting Running Django on a shared-hosting provider with Apache] 63f9682457db5ef48721c65d958346ae477f1f09 173 172 2014-08-30T17:04:38Z Rockinroel 9 /* FastCGI */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. ==CGI== CGI is a very easy and simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. In order to do that, you have to set the modification date of the starter script to a more recent date: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os sys.path.insert(0, '/home/user/username/mysite') os.chdir('/home/user/username/mysite') os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' from django.core.servers.fastcgi import runfastcgi runfastcgi(method="threaded", daemonize="false")</pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/1.6/intro/tutorial01/ The Django tutorial] * [https://docs.djangoproject.com/en/1.6/howto/deployment/fastcgi/#apache-shared-hosting Running Django on a shared-hosting provider with Apache] 6e28cb82ef3525d204d2b35220a22236d7996710 174 173 2014-08-30T17:05:41Z Rockinroel 9 /* FastCGI */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. ==CGI== CGI is a very easy and simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</pre> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. In order to do that, you have to set the modification date of the starter script to a more recent date: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os sys.path.insert(0, '/home/user/username/mysite') os.chdir('/home/user/username/mysite') os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' from django.core.servers.fastcgi import runfastcgi runfastcgi(method="threaded", daemonize="false")</pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/1.6/intro/tutorial01/ The Django tutorial] * [https://docs.djangoproject.com/en/1.6/howto/deployment/fastcgi/#apache-shared-hosting Running Django on a shared-hosting provider with Apache] 592b16992a2aed2ecf955a8a63a4e88cf68d50af 175 174 2014-08-30T17:10:08Z Rockinroel 9 /* CGI */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework with FastCGI. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</pre> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. In order to do that, you have to set the modification date of the starter script to a more recent date: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os sys.path.insert(0, '/home/user/username/mysite') os.chdir('/home/user/username/mysite') os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' from django.core.servers.fastcgi import runfastcgi runfastcgi(method="threaded", daemonize="false")</pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/1.6/intro/tutorial01/ The Django tutorial] * [https://docs.djangoproject.com/en/1.6/howto/deployment/fastcgi/#apache-shared-hosting Running Django on a shared-hosting provider with Apache] 71d07f0d3509b39e8ca6210115bcafbf1dc3f861 176 175 2014-08-30T17:10:41Z Rockinroel 9 /* CGI */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</pre> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. In order to do that, you have to set the modification date of the starter script to a more recent date: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os sys.path.insert(0, '/home/user/username/mysite') os.chdir('/home/user/username/mysite') os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' from django.core.servers.fastcgi import runfastcgi runfastcgi(method="threaded", daemonize="false")</pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/1.6/intro/tutorial01/ The Django tutorial] * [https://docs.djangoproject.com/en/1.6/howto/deployment/fastcgi/#apache-shared-hosting Running Django on a shared-hosting provider with Apache] 5fb4207fb24b814782ba7806ce9f409ebfc7880c 177 176 2014-08-30T17:11:08Z Rockinroel 9 /* CGI */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</pre> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. In order to do that, you have to set the modification date of the starter script to a more recent date: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os sys.path.insert(0, '/home/user/username/mysite') os.chdir('/home/user/username/mysite') os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' from django.core.servers.fastcgi import runfastcgi runfastcgi(method="threaded", daemonize="false")</pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/1.6/intro/tutorial01/ The Django tutorial] * [https://docs.djangoproject.com/en/1.6/howto/deployment/fastcgi/#apache-shared-hosting Running Django on a shared-hosting provider with Apache] 2d324725737189624e621b1b6f52c8b04cc9493c 178 177 2014-08-30T17:11:47Z Rockinroel 9 /* CGI */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</pre> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. In order to do that, you have to set the modification date of the starter script to a more recent date: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os sys.path.insert(0, '/home/user/username/mysite') os.chdir('/home/user/username/mysite') os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' from django.core.servers.fastcgi import runfastcgi runfastcgi(method="threaded", daemonize="false")</pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/1.6/intro/tutorial01/ The Django tutorial] * [https://docs.djangoproject.com/en/1.6/howto/deployment/fastcgi/#apache-shared-hosting Running Django on a shared-hosting provider with Apache] d4586dc72e55514acf48f1d7f7acad1b3f4c890e 0 37 179 178 2014-08-30T17:12:26Z Rockinroel 9 Rockinroel moved page [[Using CGI for non-PHP websites]] to [[Using (Fast)CGI for non-PHP websites]] wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</pre> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. In order to do that, you have to set the modification date of the starter script to a more recent date: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os sys.path.insert(0, '/home/user/username/mysite') os.chdir('/home/user/username/mysite') os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' from django.core.servers.fastcgi import runfastcgi runfastcgi(method="threaded", daemonize="false")</pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/1.6/intro/tutorial01/ The Django tutorial] * [https://docs.djangoproject.com/en/1.6/howto/deployment/fastcgi/#apache-shared-hosting Running Django on a shared-hosting provider with Apache] d4586dc72e55514acf48f1d7f7acad1b3f4c890e 0 38 180 2014-08-30T17:12:26Z Rockinroel 9 Rockinroel moved page [[Using CGI for non-PHP websites]] to [[Using (Fast)CGI for non-PHP websites]] wikitext text/x-wiki #REDIRECT [[Using (Fast)CGI for non-PHP websites]] 6b469f399b4690fd0e1a64ee6c2cb8b17edc56ac 0 3 181 149 2014-08-30T17:12:50Z Rockinroel 9 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Help, my account has been disabled]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2014]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Keeping your website secure]] * [[Preventing spam on your website]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Add an alias in Gmail]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion 101]] * [[GitLab]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> __NOTOC__ e2296ee3f66fb548dec5a7e7583fea2af1952d15 187 181 2014-09-14T19:00:51Z Bert 8 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Help, my account has been disabled]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2014]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Keeping your website secure]] * [[Preventing spam on your website]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Add an alias in Gmail]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion 101]] * [[GitLab]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 5843ba5a659576ce06f9d090f2d370d23a2d44cb 188 187 2014-09-14T19:01:17Z Bert 8 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Help, my account has been disabled]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Taking Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2014]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Keeping your website secure]] * [[Preventing spam on your website]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Add an alias in Gmail]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion 101]] * [[GitLab]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 033d2d3b9da888f866a663be6fbc6330682f5cf6 192 188 2014-09-14T19:09:05Z Bert 8 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Help, my account has been disabled]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2014]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Keeping your website secure]] * [[Preventing spam on your website]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Add an alias in Gmail]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion 101]] * [[GitLab]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 10b1b4655526bb665a107fe1dd79af29a535f69b 196 192 2014-10-16T18:22:16Z Bert 8 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2014]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Keeping your website secure]] * [[Preventing spam on your website]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Add an alias in Gmail]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion 101]] * [[GitLab]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> __NOTOC__ bbe13ef25d927841862aa1d909f378f324041b9b 199 196 2014-11-07T04:35:23Z Bert 8 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2014]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Keeping your website secure]] * [[Preventing spam on your website]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Add an alias in Gmail]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion 101]] * [[GitLab]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 6dba010bf6113b75abd135f7037e0f09eaa9e98f 200 199 2014-11-07T04:35:59Z Bert 8 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2014]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Keeping your website secure]] * [[Preventing spam on your website]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Add an alias in Gmail]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion 101]] * [[GitLab]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 55b177d83ff44c669ce95dea9cd5d8ef0e1ee520 201 200 2014-11-07T04:37:11Z Bert 8 /* CMSs */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2014]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] ** [[Preventing spam on Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] ** [[Preventing spam on MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Keeping your website secure]] * [[Preventing spam on your website]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Add an alias in Gmail]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion 101]] * [[GitLab]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 80b04d864e8e129e0c08c4dc7a79bff125021bbf 202 201 2014-11-07T04:37:29Z Bert 8 /* CMSs */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2014]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] * [[Preventing spam on Wordpress]] * [[Preventing spam on MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Keeping your website secure]] * [[Preventing spam on your website]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Add an alias in Gmail]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion 101]] * [[GitLab]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> __NOTOC__ a049dd82062bcf5a5806708ca4c9cb872d5a95ea 203 202 2014-11-07T04:37:40Z Bert 8 /* CMSs */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2014]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Keeping your website secure]] * [[Preventing spam on your website]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Add an alias in Gmail]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion 101]] * [[GitLab]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 0cc26f4d8d81fbcbcdb887c06d2efb71bf1eb7b6 204 203 2014-11-07T04:37:59Z Bert 8 /* Security & anti-spam */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2014]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Keeping your website secure]] * [[Preventing spam on your website]] * [[Preventing spam on Wordpress]] * [[Preventing spam on MediaWiki]] * [[Preventing spam on forums]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Add an alias in Gmail]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion 101]] * [[GitLab]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 4e795935f90e8a2892115cb61240f8f8aac2bf56 229 204 2015-05-11T20:19:44Z Bert 8 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2014]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Keeping your website secure]] * [[Preventing spam on your website]] * [[Preventing spam on Wordpress]] * [[Preventing spam on MediaWiki]] * [[Preventing spam on forums]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Add an alias in Gmail]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == IRC == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 6b4d858afa360bba7224769399bfbdcc73289f36 234 229 2015-08-11T15:54:50Z Bert 8 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2014]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Keeping your website secure]] * [[Preventing spam on your website]] * [[Preventing spam on Wordpress]] * [[Preventing spam on MediaWiki]] * [[Preventing spam on forums]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Add an alias in Gmail]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> </div> __NOTOC__ cb9e0951afb95793029c45ea597584705aa0f615 6 39 182 2014-08-30T17:34:19Z Rockinroel 9 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 9 183 65 2014-08-30T17:38:11Z Rockinroel 9 wikitext text/x-wiki You can find all your apache logs (like the access.log and error.log) on all of our servers in the directory: /var/log/apache_user/''username'' So if your username is ''foobar'' then you can easily access your logs this way: foobar@zap:~$ cd /var/log/apache_user/foobar foobar@zap:/var/log/apache_user/foobar$ ls foobar.ulyssis.be foobar@zap:/var/log/apache_user/foobar$ cd foobar.ulyssis.be foobar@zap:/var/log/apache_user/foobar/foobar.ulyssis.be$ ls access-2014-05-07.log error-2014-05-07.log foobar@zap:/var/log/apache_user/foobar/foobar.ulyssis.be$ tail error-2014-05-07.log [Wed May 07 01:27:14 2014] [error] [client 10.0.0.1] File does not exist: /home/user/foobar/www/favicon.ico If you can't find your username inside of <code>/var/log/apache_user</code>, don't worry. If you enter it with <code>cd foobar</code>, it will automatically appear. ==With FileZilla== You can also access the log files with an SFTP client, like FileZilla. Just enter <tt>/var/log/apache_user/''username''</tt> on the right hand side, where it says "Remote site", and press <tt>Enter</tt>: [[File:Logs.png]] 1660fefb56e19558a12deeebd49255c6783b0873 184 183 2014-08-30T17:38:38Z Rockinroel 9 /* With FileZilla */ wikitext text/x-wiki You can find all your apache logs (like the access.log and error.log) on all of our servers in the directory: /var/log/apache_user/''username'' So if your username is ''foobar'' then you can easily access your logs this way: foobar@zap:~$ cd /var/log/apache_user/foobar foobar@zap:/var/log/apache_user/foobar$ ls foobar.ulyssis.be foobar@zap:/var/log/apache_user/foobar$ cd foobar.ulyssis.be foobar@zap:/var/log/apache_user/foobar/foobar.ulyssis.be$ ls access-2014-05-07.log error-2014-05-07.log foobar@zap:/var/log/apache_user/foobar/foobar.ulyssis.be$ tail error-2014-05-07.log [Wed May 07 01:27:14 2014] [error] [client 10.0.0.1] File does not exist: /home/user/foobar/www/favicon.ico If you can't find your username inside of <code>/var/log/apache_user</code>, don't worry. If you enter it with <code>cd foobar</code>, it will automatically appear. ==With FileZilla== You can also access the log files with an SFTP client, like FileZilla. Just enter <tt>/var/log/apache_user/''username''</tt> (replace ''username'' with your username) on the right hand side, where it says "Remote site", and press <tt>Enter</tt>: [[File:Logs.png]] 699ddb0a60de029380d3fd343af37317afbe35cc 0 40 185 2014-09-14T18:08:10Z Bert 8 Created page with "You can access your MySQL databases using PHPMyAdmin. This application can be found on https://phpmyadmin.ulyssis.org." wikitext text/x-wiki You can access your MySQL databases using PHPMyAdmin. This application can be found on https://phpmyadmin.ulyssis.org. 01afbb2a0a67471bdcbb5dd398888c7249f52733 186 185 2014-09-14T19:00:24Z Bert 8 wikitext text/x-wiki You can access your MySQL databases using PHPMyAdmin. This application can be found on https://phpmyadmin.ulyssis.org. To login you need to use your MySQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your MySQL password you can get it from your websites configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. == Basic Usage == On the left you will see your username, you can click the plus sign to reveal all your databases. You can then view databases and tables. For each table you can view the records, view and change the structure, add records, take backups, etc. == Taking Backups == To take a backup of all your databases you simple select "Export" on the main menu and press start. You can later restore backups by uploading the file to the "Import" page. 7bb1f6ac51757933c0175d69c6b0247ba3ee2a26 0 41 189 2014-09-14T19:08:31Z Bert 8 Created page with "ULYSSIS takes backups of all files, databases, settings and repositories 1-4 times a week. These backups can be restored in case of severe server failure or in case of an emer..." wikitext text/x-wiki ULYSSIS takes backups of all files, databases, settings and repositories 1-4 times a week. These backups can be restored in case of severe server failure or in case of an emergency (if for example a user by mistake deletes all of their site). It is, however, more convenient that users take their own backups when they do experimental things on their account. == A backup of your files == You can use the graphical methods described in [[Accessing your files]] to download a copy of all of your files. This copy, or certain files, can then easily be uploaded again using the same method to restore backups == A backup of your databases == To take a backup of your database you simple use the export function of PHPMyAdmin as described on [[Using PHPMyAdmin]]. bffc748824e001001d30340d77a82e68714b6520 190 189 2014-09-14T19:08:55Z Bert 8 Bert moved page [[Taking Backups]] to [[Making Backups]] wikitext text/x-wiki ULYSSIS takes backups of all files, databases, settings and repositories 1-4 times a week. These backups can be restored in case of severe server failure or in case of an emergency (if for example a user by mistake deletes all of their site). It is, however, more convenient that users take their own backups when they do experimental things on their account. == A backup of your files == You can use the graphical methods described in [[Accessing your files]] to download a copy of all of your files. This copy, or certain files, can then easily be uploaded again using the same method to restore backups == A backup of your databases == To take a backup of your database you simple use the export function of PHPMyAdmin as described on [[Using PHPMyAdmin]]. bffc748824e001001d30340d77a82e68714b6520 0 42 191 2014-09-14T19:08:55Z Bert 8 Bert moved page [[Taking Backups]] to [[Making Backups]] wikitext text/x-wiki #REDIRECT [[Making Backups]] bd0a85b2960e645274e21af6dad135f5da70e3fb 0 43 193 2014-09-23T10:33:32Z W29 13 Created page with "You may want to receive e-mail from ulyssis on another email provider. It is very easy to set this up. # Go to ucc.ulyssis.org and log in with your username and password. # O..." wikitext text/x-wiki You may want to receive e-mail from ulyssis on another email provider. It is very easy to set this up. # Go to ucc.ulyssis.org and log in with your username and password. # On the right side, click on '''Mail'''. # Under '''Address forward''' you can change the forward address of your ULYSSIS mail by clicking on '''edit'''. # Choose '''forward''' and enter the email address you want to forward your ULYSSIS mail to and save the changes. # If you forward it to your Gmail account, it is recommended to [[Add an alias in Gmail]] so you can send mails from your ULYSSIS accout using Gmail. b5ca856b6ac2adc2f3541686ee1ace89de89b7d7 0 44 194 2014-09-23T10:49:28Z W29 13 Created page with "= Location of your files = All the files you want to provide via the web browser must reside in a directory named "www" in your homefolder. Within that folder you can organis..." wikitext text/x-wiki = Location of your files = All the files you want to provide via the web browser must reside in a directory named "www" in your homefolder. Within that folder you can organise your data in sub directories. For more information about accessing your files is available [https://docs.ulyssis.org/Accessing_your_files here]. = Accessing your website = Your webspace is accessible on following url's (with username your username): * http://username.ulyssis.be * http://username.studentenweb.org If you have a domainname like yourname.be, you can link it with our webserver. For more information on this subject, see the [https://docs.ulyssis.org/Adding_domain_names domainnames documentation]. = Troubleshooting = I keep getting an "HTTP Error 403: permission denied" when accessing my website. Try changing the permissions of your www-directory. Log in to a ULYSSIS shell machine and type: <code>chmod o+x ~ chmod o+rx ~/www</code> 742f6e4e07673a1e7edb29970133dc72d462cc4e 0 19 195 164 2014-09-28T15:50:15Z Jorisvh 15 /* SMTP */ ulyssis.be -> kuleuven.be wikitext text/x-wiki Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mail regularly, because all important information will be sent to this address. You can check your e-mail using the webmail or an email client of your own. ==Webmail== You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to enter the website. ==POP and IMAP access== You can access your ulyssis mail by POP or IMAP protocol. The configuration parameters are: * '''server''': <tt>mail.ulyssis.org</tt> * '''username''': ''your ULYSSIS username'' * '''password''': ''your ULYSSIS password'' * '''security''': SSL ==SMTP== ULYSSIS doesn't offer SMTP. Instead, you can use KULeuven's SMTP server: * '''server''': <tt>smtp.kuleuven.be</tt> * '''port''': 465 * '''username''': ''your student id'' * '''password''': ''your KULeuven password'' * '''security''': SSL fac418ab218baced5b45c6efe8bb25899a6b54fe 0 45 197 2014-11-05T10:53:43Z W29 13 Created page with "If you have lost your password, you can always reset it. To reset your password you visit [https://ucc.ulyssis.org/ucc/passwd/reset UCC]. * Fill in your username and click on..." wikitext text/x-wiki If you have lost your password, you can always reset it. To reset your password you visit [https://ucc.ulyssis.org/ucc/passwd/reset UCC]. * Fill in your username and click on 'reset password' * Then you will have to sign in using your kuleuven credentials to make sure it is really you * Choose another password * Click on reset password * Try to log in at UCC with your new password Be wise and pick a [https://xkcd.com/936/ strong and easy to remember password]. 43fb5bb5cb9b4967b7080cbef632df63a4e3e15b 198 197 2014-11-05T10:54:54Z W29 13 wikitext text/x-wiki You can always reset your password. In order to reset your password, visit [https://ucc.ulyssis.org/ucc/passwd/reset UCC]. * Fill in your username and click on 'reset password' * Then you will have to sign in using your KULeuven credentials to make sure it is really you * Choose another password * Click on reset password * Try to log in at UCC with your new password Be wise and pick a [https://xkcd.com/936/ strong and easy to remember password]. d107e7bf80802733782b1510dae3d6bf25b18fe4 0 46 205 2014-11-08T16:03:45Z Koen 17 Created page with "If you stumble upon this question, don't worry; you already payed us." wikitext text/x-wiki If you stumble upon this question, don't worry; you already payed us. 939f401b47d998604ad2857f96a6269b32e2f773 206 205 2014-11-08T16:04:28Z Koen 17 wikitext text/x-wiki If you stumbled upon this question, don't worry; you already payed us. bacb5a2473b7a76b9b96ee624157a6adb3566d34 207 206 2014-11-08T16:08:13Z Koen 17 wikitext text/x-wiki If you stumbled upon this question, don't worry; you don't have to (and coudn't) make an empty transfer. 2996fcac3faa0f5a36acd1abafa5e00feb1f733d 208 207 2014-11-11T19:46:23Z Rockinroel 9 wikitext text/x-wiki If you stumbled upon this question, don't worry; you don't have to (and can't) make an empty transfer. f96e6fe1afc0e6110097be1002d6be84bfe981f3 0 47 209 2014-11-19T14:30:36Z Koen 17 Created page with "This page will go through a basic setup of MediaWiki. It is based on [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wikipage], ..." wikitext text/x-wiki This page will go through a basic setup of MediaWiki. It is based on [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wikipage], and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. =Putting setup-files in place= First we'll have to download the setup file which you can find over at [http://www.mediawiki.org/wiki/Download the official MediaWiki website]. It's an archived file, so you need to extract it first and put the files in a subdirectory of your "document root". The default is just a www directory in your home folder. You can also see it by looking at your [https://ucc.ulyssis.org/vhosts vhost configuration]. If you put your files in www/wiki/ your wiki will be located at usersname.ulyssis.be/wiki/. If you prefer, you can do this all graphically; [https://docs.ulyssis.org/Accessing_your_files]. If you prefer the command line; <pre> homeuser@home:~$ ssh me@ssh1.ulyssis.org enter super secret password: me@zap:~$ wget http://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.6.tar.gz me@zap:~$ tar xvxf mediawiki-1.23.6.tar.gz me@zap:~$ mv mediawiki-1.23.6 www/wiki me@zap:~$ rm -r mediawiki-1.23.6.tar.gz </pre> =Setting up database= Like the [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wiki] tells us, we have three different options to choose from; PostgreSQL, MySQL and SQLite. It's easy to set a PostgreSQL or MySQL database; just go to the UCC. For this tutorial we will continue with a MySQL database (PostgreSQL installation steps are quite similar). Let us visit https://ucc.ulyssis.org/mysql; if this is your first time using MySQL you'll need to create a new account by putting in a super secret password. The wizard will create your MySQL account with the same name as your user-account. We'll also create a new database with an appropriate name by clicking on 'Add database'. In this tutorial we will choose; "wiki", notice that it will be prepended with our username, so we'll end up with a new database named "me_wiki". =Setup your wiki= If all went well, you can access your website at http://username.ulyssis.be/the_folder_you_used and start the setup wizard. In our example, will surf to http://me.ulyssis.be/wiki. The wizard will guide you through some configuration options. Most of them our pretty straight-forward. When in doubt, you can always click the question mark wich will show you some sensible and recommended default... We'll just discuss the page were the wizard asks you for the database. In our example; <pre> Database host: mysql.ulyssis.org Database name: me_wiki // The name of our database; i.e. the name we chose, prepended by our username. Database table prefix: // We can leave this blank. Database user: me // This is the name of our MySQL-user, which was named after our ULLYSIS-username. Database password: supersecretpassword // Please note that this is not your ULLYSIS-password, but the password you used in UCC when creating the MySQL user! </pre> =Creating the wiki= After the setup wizard is complete, you can begin the installation procedure. If all went well, you'll be greeted by a page which congratulates you with your new installation. =Finalizing steps= The setup will offer you a configuration file (containing some settings you specified) that you need to download to your server (more specifically in directory where your MediaWiki-files reside in). You again can do this graphically, or if you prefer a terminal; <pre> homeuser@home:~$ scp path_to_file/LocalSettings.php me@ssh1.ulyssis.org:~/www/wiki enter super secret password: </pre> After this is done, you can finally start using your wiki. !!! Note that this is only a very basic case of a wiki install. Please refer to [http://www.mediawiki.org/wiki/MediaWiki the original MediaWiki wiki] for a more in depth source. !!! !!! Please know that managing a wiki comes with great responsibility, keep your wiki up to date and follow healthy and recommended security practices. !!! 643dbfd2f7f0c463b543e10947b02ec848db4fed 210 209 2014-11-19T14:32:27Z Koen 17 wikitext text/x-wiki This page will go through a basic setup of MediaWiki. It is based on [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wikipage], and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. =Putting setup-files in place= First we'll have to download the setup file which you can find over at [http://www.mediawiki.org/wiki/Download the official MediaWiki website]. It's an archived file, so you need to extract it first and put the files in a subdirectory of your "document root". The default is just a www directory in your home folder. You can also see it by looking at your [https://ucc.ulyssis.org/vhosts vhost configuration]. Putting your files in document_root/wiki/ will make your wiki be located at usersname.ulyssis.be/wiki/. If you prefer, you can do this all graphically; [https://docs.ulyssis.org/Accessing_your_files]. If you prefer the command line; <pre> homeuser@home:~$ ssh me@ssh1.ulyssis.org enter super secret password: me@zap:~$ wget http://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.6.tar.gz me@zap:~$ tar xvxf mediawiki-1.23.6.tar.gz me@zap:~$ mv mediawiki-1.23.6 www/wiki me@zap:~$ rm -r mediawiki-1.23.6.tar.gz </pre> =Setting up database= Like the [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wiki] tells us, we have three different options to choose from; PostgreSQL, MySQL and SQLite. It's easy to set a PostgreSQL or MySQL database; just go to the UCC. For this tutorial we will continue with a MySQL database (PostgreSQL installation steps are quite similar). Let us visit https://ucc.ulyssis.org/mysql; if this is your first time using MySQL you'll need to create a new account by putting in a super secret password. The wizard will create your MySQL account with the same name as your user-account. We'll also create a new database with an appropriate name by clicking on 'Add database'. In this tutorial we will choose; "wiki", notice that it will be prepended with our username, so we'll end up with a new database named "me_wiki". =Setup your wiki= If all went well, you can access your website at http://username.ulyssis.be/the_folder_you_used and start the setup wizard. In our example, will surf to http://me.ulyssis.be/wiki. The wizard will guide you through some configuration options. Most of them our pretty straight-forward. When in doubt, you can always click the question mark wich will show you some sensible and recommended default... We'll just discuss the page were the wizard asks you for the database. In our example; <pre> Database host: mysql.ulyssis.org Database name: me_wiki // The name of our database; i.e. the name we chose, prepended by our username. Database table prefix: // We can leave this blank. Database user: me // This is the name of our MySQL-user, which was named after our ULLYSIS-username. Database password: supersecretpassword // Please note that this is not your ULLYSIS-password, but the password you used in UCC when creating the MySQL user! </pre> =Creating the wiki= After the setup wizard is complete, you can begin the installation procedure. If all went well, you'll be greeted by a page which congratulates you with your new installation. =Finalizing steps= The setup will offer you a configuration file (containing some settings you specified) that you need to download to your server (more specifically in directory where your MediaWiki-files reside in). You again can do this graphically, or if you prefer a terminal; <pre> homeuser@home:~$ scp path_to_file/LocalSettings.php me@ssh1.ulyssis.org:~/www/wiki enter super secret password: </pre> After this is done, you can finally start using your wiki. !!! Note that this is only a very basic case of a wiki install. Please refer to [http://www.mediawiki.org/wiki/MediaWiki the original MediaWiki wiki] for a more in depth source. !!! !!! Please know that managing a wiki comes with great responsibility, keep your wiki up to date and follow healthy and recommended security practices. !!! 1ade087eff9006ad17f090fd8b0b2e6ac38b3c10 211 210 2014-11-19T14:36:30Z Koen 17 wikitext text/x-wiki This page will go through a basic setup of MediaWiki. It is based on [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wikipage], and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. This tutorial we'll use a ULYSSIS-account with username "me". =Putting setup-files in place= First we'll have to download the setup file which you can find over at [http://www.mediawiki.org/wiki/Download the official MediaWiki website]. It's an archived file, so you need to extract it first and put the files in a subdirectory of your "document root". The default is just a www directory in your home folder. You can also see it by looking at your [https://ucc.ulyssis.org/vhosts vhost configuration]. Putting your files in document_root/wiki/ will make your wiki be located at usersname.ulyssis.be/wiki/. If you prefer, you can do this all graphically; [https://docs.ulyssis.org/Accessing_your_files]. If you prefer the command line; <pre> homeuser@home:~$ ssh me@ssh1.ulyssis.org enter super secret password: me@zap:~$ wget http://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.6.tar.gz me@zap:~$ tar xvxf mediawiki-1.23.6.tar.gz me@zap:~$ mv mediawiki-1.23.6 www/wiki me@zap:~$ rm -r mediawiki-1.23.6.tar.gz </pre> =Setting up database= Like the [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wiki] tells us, we have three different options to choose from; PostgreSQL, MySQL and SQLite. It's easy to set a PostgreSQL or MySQL database; just go to the UCC. For this tutorial we will continue with a MySQL database (PostgreSQL installation steps are quite similar). Let us visit https://ucc.ulyssis.org/mysql; if this is your first time using MySQL you'll need to create a new account by putting in a super secret password. The wizard will create your MySQL account with the same name as your user-account. We'll also create a new database with an appropriate name by clicking on 'Add database'. In this tutorial we will choose; "wiki", notice that it will be prepended with our username, so we'll end up with a new database named "me_wiki". =Setup your wiki= If all went well, you can access your website at http://username.ulyssis.be/the_folder_you_used and start the setup wizard. In our example, will surf to http://me.ulyssis.be/wiki. The wizard will guide you through some configuration options. Most of them our pretty straight-forward. When in doubt, you can always click the question mark wich will show you some sensible and recommended default... We'll just discuss the page were the wizard asks you for the database. In our example; <pre> Database host: mysql.ulyssis.org Database name: me_wiki // The name of our database; i.e. the name we chose, prepended by our username. Database table prefix: // We can leave this blank. Database user: me // This is the name of our MySQL-user, which was named after our ULLYSIS-username. Database password: supersecretpassword // Please note that this is not your ULLYSIS-password, but the password you used in UCC when creating the MySQL user! </pre> =Creating the wiki= After the setup wizard is complete, you can begin the installation procedure. If all went well, you'll be greeted by a page which congratulates you with your new installation. =Finalizing steps= The setup will offer you a configuration file (containing some settings you specified) that you need to download to your server (more specifically in directory where your MediaWiki-files reside in). You again can do this graphically, or if you prefer a terminal; <pre> homeuser@home:~$ scp path_to_file/LocalSettings.php me@ssh1.ulyssis.org:~/www/wiki enter super secret password: </pre> After this is done, you can finally start using your wiki. !!! Note that this is only a very basic case of a wiki install. Please refer to [http://www.mediawiki.org/wiki/MediaWiki the original MediaWiki wiki] for a more in depth source. !!! !!! Please know that managing a wiki comes with great responsibility, keep your wiki up to date and follow healthy and recommended security practices. !!! 09b32476b0d4d722b86161100b0061bb945edd7f 212 211 2014-11-22T05:12:53Z Bert 8 wikitext text/x-wiki This page will go through a basic setup of MediaWiki. It is based on [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wikipage], and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. This tutorial we'll use a ULYSSIS-account with username "me". =Putting setup-files in place= First we'll have to download the setup file which you can find over at [http://www.mediawiki.org/wiki/Download the official MediaWiki website]. It's an archived file, so you need to extract it first and put the files in a subdirectory of your "document root". The default is just a www directory in your home folder. You can also see it by looking at your [https://ucc.ulyssis.org/vhosts vhost configuration]. Putting your files in document_root/wiki/ will make your wiki be located at usersname.ulyssis.be/wiki/. If you prefer, you can do this all graphically; [[https://docs.ulyssis.org/Accessing_your_files]]. If you prefer the command line; <pre> homeuser@home:~$ ssh me@ssh1.ulyssis.org enter super secret password: me@zap:~$ wget http://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.6.tar.gz me@zap:~$ tar xvxf mediawiki-1.23.6.tar.gz me@zap:~$ mv mediawiki-1.23.6 www/wiki me@zap:~$ rm -r mediawiki-1.23.6.tar.gz </pre> =Setting up database= Like the [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wiki] tells us, we have three different options to choose from; PostgreSQL, MySQL and SQLite. It's easy to set a PostgreSQL or MySQL database; just go to the UCC. For this tutorial we will continue with a MySQL database (PostgreSQL installation steps are quite similar). Let us visit https://ucc.ulyssis.org/mysql; if this is your first time using MySQL you'll need to create a new account by putting in a super secret password. The wizard will create your MySQL account with the same name as your user-account. We'll also create a new database with an appropriate name by clicking on 'Add database'. In this tutorial we will choose; "wiki", notice that it will be prepended with our username, so we'll end up with a new database named "me_wiki". =Setup your wiki= If all went well, you can access your website at http://username.ulyssis.be/the_folder_you_used and start the setup wizard. In our example, will surf to http://me.ulyssis.be/wiki. The wizard will guide you through some configuration options. Most of them our pretty straight-forward. When in doubt, you can always click the question mark wich will show you some sensible and recommended default... We'll just discuss the page were the wizard asks you for the database. In our example; <pre> Database host: mysql.ulyssis.org Database name: me_wiki // The name of our database; i.e. the name we chose, prepended by our username. Database table prefix: // We can leave this blank. Database user: me // This is the name of our MySQL-user, which was named after our ULLYSIS-username. Database password: supersecretpassword // Please note that this is not your ULLYSIS-password, but the password you used in UCC when creating the MySQL user! </pre> =Creating the wiki= After the setup wizard is complete, you can begin the installation procedure. If all went well, you'll be greeted by a page which congratulates you with your new installation. =Finalizing steps= The setup will offer you a configuration file (containing some settings you specified) that you need to download to your server (more specifically in directory where your MediaWiki-files reside in). You again can do this graphically, or if you prefer a terminal; <pre> homeuser@home:~$ scp path_to_file/LocalSettings.php me@ssh1.ulyssis.org:~/www/wiki enter super secret password: </pre> After this is done, you can finally start using your wiki. !!! Note that this is only a very basic case of a wiki install. Please refer to [http://www.mediawiki.org/wiki/MediaWiki the original MediaWiki wiki] for a more in depth source. !!! !!! Please know that managing a wiki comes with great responsibility, keep your wiki up to date and follow healthy and recommended security practices. !!! 132ffc78e9a440de29b4e0e82374330e76952649 213 212 2014-11-22T05:13:09Z Bert 8 wikitext text/x-wiki This page will go through a basic setup of MediaWiki. It is based on [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wikipage], and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. This tutorial we'll use a ULYSSIS-account with username "me". =Putting setup-files in place= First we'll have to download the setup file which you can find over at [http://www.mediawiki.org/wiki/Download the official MediaWiki website]. It's an archived file, so you need to extract it first and put the files in a subdirectory of your "document root". The default is just a www directory in your home folder. You can also see it by looking at your [https://ucc.ulyssis.org/vhosts vhost configuration]. Putting your files in document_root/wiki/ will make your wiki be located at usersname.ulyssis.be/wiki/. If you prefer, you can do this all graphically; [[Accessing_your_files]]. If you prefer the command line; <pre> homeuser@home:~$ ssh me@ssh1.ulyssis.org enter super secret password: me@zap:~$ wget http://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.6.tar.gz me@zap:~$ tar xvxf mediawiki-1.23.6.tar.gz me@zap:~$ mv mediawiki-1.23.6 www/wiki me@zap:~$ rm -r mediawiki-1.23.6.tar.gz </pre> =Setting up database= Like the [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wiki] tells us, we have three different options to choose from; PostgreSQL, MySQL and SQLite. It's easy to set a PostgreSQL or MySQL database; just go to the UCC. For this tutorial we will continue with a MySQL database (PostgreSQL installation steps are quite similar). Let us visit https://ucc.ulyssis.org/mysql; if this is your first time using MySQL you'll need to create a new account by putting in a super secret password. The wizard will create your MySQL account with the same name as your user-account. We'll also create a new database with an appropriate name by clicking on 'Add database'. In this tutorial we will choose; "wiki", notice that it will be prepended with our username, so we'll end up with a new database named "me_wiki". =Setup your wiki= If all went well, you can access your website at http://username.ulyssis.be/the_folder_you_used and start the setup wizard. In our example, will surf to http://me.ulyssis.be/wiki. The wizard will guide you through some configuration options. Most of them our pretty straight-forward. When in doubt, you can always click the question mark wich will show you some sensible and recommended default... We'll just discuss the page were the wizard asks you for the database. In our example; <pre> Database host: mysql.ulyssis.org Database name: me_wiki // The name of our database; i.e. the name we chose, prepended by our username. Database table prefix: // We can leave this blank. Database user: me // This is the name of our MySQL-user, which was named after our ULLYSIS-username. Database password: supersecretpassword // Please note that this is not your ULLYSIS-password, but the password you used in UCC when creating the MySQL user! </pre> =Creating the wiki= After the setup wizard is complete, you can begin the installation procedure. If all went well, you'll be greeted by a page which congratulates you with your new installation. =Finalizing steps= The setup will offer you a configuration file (containing some settings you specified) that you need to download to your server (more specifically in directory where your MediaWiki-files reside in). You again can do this graphically, or if you prefer a terminal; <pre> homeuser@home:~$ scp path_to_file/LocalSettings.php me@ssh1.ulyssis.org:~/www/wiki enter super secret password: </pre> After this is done, you can finally start using your wiki. !!! Note that this is only a very basic case of a wiki install. Please refer to [http://www.mediawiki.org/wiki/MediaWiki the original MediaWiki wiki] for a more in depth source. !!! !!! Please know that managing a wiki comes with great responsibility, keep your wiki up to date and follow healthy and recommended security practices. !!! 65a0385f5e506d27fcbc3140c01d7ea456900456 214 213 2014-11-22T05:13:31Z Bert 8 wikitext text/x-wiki This page will go through a basic setup of MediaWiki. It is based on [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wikipage], and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. This tutorial we'll use a ULYSSIS-account with username "me". =Putting setup-files in place= First we'll have to download the setup file which you can find over at [http://www.mediawiki.org/wiki/Download the official MediaWiki website]. It's an archived file, so you need to extract it first and put the files in a subdirectory of your "document root". The default is just a www directory in your home folder. Putting your files in document_root/wiki/ will make your wiki be located at usersname.ulyssis.be/wiki/. If you prefer, you can do this all graphically; [[Accessing_your_files]]. If you prefer the command line; <pre> homeuser@home:~$ ssh me@ssh1.ulyssis.org enter super secret password: me@zap:~$ wget http://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.6.tar.gz me@zap:~$ tar xvxf mediawiki-1.23.6.tar.gz me@zap:~$ mv mediawiki-1.23.6 www/wiki me@zap:~$ rm -r mediawiki-1.23.6.tar.gz </pre> =Setting up database= Like the [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wiki] tells us, we have three different options to choose from; PostgreSQL, MySQL and SQLite. It's easy to set a PostgreSQL or MySQL database; just go to the UCC. For this tutorial we will continue with a MySQL database (PostgreSQL installation steps are quite similar). Let us visit https://ucc.ulyssis.org/mysql; if this is your first time using MySQL you'll need to create a new account by putting in a super secret password. The wizard will create your MySQL account with the same name as your user-account. We'll also create a new database with an appropriate name by clicking on 'Add database'. In this tutorial we will choose; "wiki", notice that it will be prepended with our username, so we'll end up with a new database named "me_wiki". =Setup your wiki= If all went well, you can access your website at http://username.ulyssis.be/the_folder_you_used and start the setup wizard. In our example, will surf to http://me.ulyssis.be/wiki. The wizard will guide you through some configuration options. Most of them our pretty straight-forward. When in doubt, you can always click the question mark wich will show you some sensible and recommended default... We'll just discuss the page were the wizard asks you for the database. In our example; <pre> Database host: mysql.ulyssis.org Database name: me_wiki // The name of our database; i.e. the name we chose, prepended by our username. Database table prefix: // We can leave this blank. Database user: me // This is the name of our MySQL-user, which was named after our ULLYSIS-username. Database password: supersecretpassword // Please note that this is not your ULLYSIS-password, but the password you used in UCC when creating the MySQL user! </pre> =Creating the wiki= After the setup wizard is complete, you can begin the installation procedure. If all went well, you'll be greeted by a page which congratulates you with your new installation. =Finalizing steps= The setup will offer you a configuration file (containing some settings you specified) that you need to download to your server (more specifically in directory where your MediaWiki-files reside in). You again can do this graphically, or if you prefer a terminal; <pre> homeuser@home:~$ scp path_to_file/LocalSettings.php me@ssh1.ulyssis.org:~/www/wiki enter super secret password: </pre> After this is done, you can finally start using your wiki. !!! Note that this is only a very basic case of a wiki install. Please refer to [http://www.mediawiki.org/wiki/MediaWiki the original MediaWiki wiki] for a more in depth source. !!! !!! Please know that managing a wiki comes with great responsibility, keep your wiki up to date and follow healthy and recommended security practices. !!! 3e183182a7d2379df26418e0e7817d3834c6d6a8 215 214 2014-11-22T05:18:26Z Bert 8 wikitext text/x-wiki This page will go through a basic setup of MediaWiki. It is based on [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wikipage], and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. This tutorial we'll use a ULYSSIS-account with username "me". =Putting setup-files in place= First we'll have to download the setup file which you can find over at [http://www.mediawiki.org/wiki/Download the official MediaWiki website]. It's an archived file, so you need to extract it first and put the files in a subdirectory of your "document root". The default is just a www directory in your home folder. Putting your files in document_root/wiki/ will make your wiki be located at usersname.ulyssis.be/wiki/. If you prefer, you can do this all graphically using the manual [[Accessing_your_files]]. If you prefer the command line; <pre> homeuser@home:~$ ssh me@ssh1.ulyssis.org enter super secret password: me@zap:~$ wget http://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.6.tar.gz me@zap:~$ tar xvxf mediawiki-1.23.6.tar.gz me@zap:~$ mv mediawiki-1.23.6 www/wiki me@zap:~$ rm -r mediawiki-1.23.6.tar.gz </pre> =Setting up database= Like the [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wiki] tells us, we have three different options to choose from; PostgreSQL, MySQL and SQLite. It's easy to set a PostgreSQL or MySQL database; just go to the UCC. For this tutorial we will continue with a MySQL database (PostgreSQL installation steps are quite similar). Let us visit https://ucc.ulyssis.org/mysql; if this is your first time using MySQL you'll need to create a new account by putting in a super secret password. The wizard will create your MySQL account with the same name as your user-account. We'll also create a new database with an appropriate name by clicking on 'Add database'. In this tutorial we will choose; "wiki", notice that it will be prepended with our username, so we'll end up with a new database named "me_wiki". =Setup your wiki= If all went well, you can access your website at http://username.ulyssis.be/the_folder_you_used and start the setup wizard. In our example, will surf to http://me.ulyssis.be/wiki. The wizard will guide you through some configuration options. Most of them our pretty straight-forward. When in doubt, you can always click the question mark wich will show you some sensible and recommended default... We'll just discuss the page were the wizard asks you for the database. In our example; <pre> Database host: mysql.ulyssis.org Database name: me_wiki // The name of our database; i.e. the name we chose, prepended by our username. Database table prefix: // We can leave this blank. Database user: me // This is the name of our MySQL-user, which was named after our ULLYSIS-username. Database password: supersecretpassword // Please note that this is not your ULLYSIS-password, but the password you used in UCC when creating the MySQL user! </pre> =Creating the wiki= After the setup wizard is complete, you can begin the installation procedure. If all went well, you'll be greeted by a page which congratulates you with your new installation. =Finalizing steps= The setup will offer you a configuration file (containing some settings you specified) that you need to download to your server (more specifically in directory where your MediaWiki-files reside in). You again can do this graphically, or if you prefer a terminal; <pre> homeuser@home:~$ scp path_to_file/LocalSettings.php me@ssh1.ulyssis.org:~/www/wiki enter super secret password: </pre> After this is done, you can finally start using your wiki. !!! Note that this is only a very basic case of a wiki install. Please refer to [http://www.mediawiki.org/wiki/MediaWiki the original MediaWiki wiki] for a more in depth source. !!! !!! Please know that managing a wiki comes with great responsibility, keep your wiki up to date and follow healthy and recommended security practices. !!! b7c84fe3c108da0afd640ef045876ca6ffaee195 0 20 216 130 2014-11-23T22:43:42Z Covert 18 /* Installing wordpress on our servers is definitely easy */ wikitext text/x-wiki ==Installing wordpress on our servers is definitely easy== Installing wordpress on our servers is deffinately easy. You download the install components from the http://wordpress.org wordpress-site. Here you get a compressed file (.tar.gz or .zip) which you have to extract.. You get a folder with files, those files (so no the folder) you copie via filezilla or an other ftp programme to your www-map on your shellaccount. Afterwards you go to your account, I.E username.ulyssis.be, here you get a notification telling you your <code>wp-config.php</code> has to be created, the easiest way is to follow the wizard, so click on “Create a Configuration File”. Afterwards on ''Let's go!'' which will prompt you for your database credentials: *'''Database Name: ''' if you haven't created a mysql database or user on UCC then you have to create it there. The default database is: username_username. *''''User Name: ''' this is the name you gave during the creation of your mysql account, often this is the same as your username with ULYSSIS. *'''Password: ''' the password hat you gave during the creation of your mysql account *'''Database Host: ''' this is <code>mysql.ulyssis.org</code> * You don't change the last field When you're done click on “Run the install” Here you can give the last few details. Afterwards the install will run by it own and thats it, you installed wordpress. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site then you the create a new folder in your homedir from your shell account. Then you make a new virtual host for this directory in UCC. Name: alias.username.ulyssis.be Document root: /home/user/username/new_folder From now on you do al the same steps as for a regular wordpress installation. 6ab98dcdd309632105ba7a37e3d17ac137ae38a2 222 216 2015-02-23T18:51:19Z Covert 18 wikitext text/x-wiki ==Installing wordpress on our servers is definitely easy== Installing wordpress on our servers is deffinately easy. You download the install components from the http://wordpress.org wordpress-site. Here you get a compressed file (.tar.gz or .zip) which you have to extract.. You get a folder with files, those files (so no the folder) you copy via filezilla or an other ftp programme to your www-map on your shellaccount. Afterwards you go to your account, I.E username.ulyssis.be, here you get a notification telling you your <code>wp-config.php</code> has to be created, the easiest way is to follow the wizard, so click on “Create a Configuration File”. Afterwards on ''Let's go!'' which will prompt you for your database credentials: *'''Database Name: ''' if you haven't created a mysql database or user on UCC then you have to create it there. The default database is: username_username. *''''User Name: ''' this is the name you gave during the creation of your mysql account, often this is the same as your username with ULYSSIS. *'''Password: ''' the password hat you gave during the creation of your mysql account *'''Database Host: ''' this is <code>mysql.ulyssis.org</code> * You don't change the last field When you're done click on “Run the install” Here you can give the last few details. Afterwards the install will run by it own and thats it, you installed wordpress. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site then you the create a new folder in your homedir from your shell account. Then you make a new virtual host for this directory in UCC. Name: alias.username.ulyssis.be Document root: /home/user/username/new_folder From now on you do al the same steps as for a regular wordpress installation. d2a16904202193dee8331486606783f23e7f7ca2 1 48 217 2015-01-28T14:51:15Z Robin5210 12 Created page with "There are many aspects to keeping your website secure." wikitext text/x-wiki There are many aspects to keeping your website secure. b64a634d8e5db170a14b2b5ee88d149a77ba523f 218 217 2015-01-28T15:30:47Z Robin5210 12 wikitext text/x-wiki kies een goed wachtwoord, dit is een sql-injectie+doe dus een prepared statement, update uw stuff, laat geen oude rommel rondslingeren, gebruik captcha's, da soort shit There are many aspects to keeping your website secure. = Your password = You have probably heard this ons numerous times. But we can't repeat it enough. Choose a good password containing letter, numbers and other characters. Don't choose something to obvious. When you think your password has been comprimised, don't change it immediately. First try to determine the source of your password leak and fix it. If the leak continous to exist, it's likely that your password will be compromised again in the future. When your password leak has been fixed, it's time to change it. = Updates = Another key aspect of securing your site is keeping it up to date. If you are using a cms, use Google to search how to update it. If you wrote a custom website, lookout for updates for the libraries you used to create your website. 6e99b279868a08136f002c47b3d3ea2cceb89ff4 0 33 219 138 2015-01-29T04:29:15Z Bert 8 wikitext text/x-wiki Shibboleth is the software powering the Central KU Leuven Login. It's a piece of software used by many universities to supply identification and access management. ULYSSIS works together with ICTS to supply limited access to Shibboleth. We are however only able to supply Shibboleth to those approved by ICTS. In practice all faculty unions will be granted access if they can prove they have the technical ability to use Shibboleth in a safe and privacy friendly way. For other organisations it can be more difficult to get access, therefore it is best to write an extensive explenation of what you plan to do with Shibboleth, why your organisation requires it, what your organisation does, and other relevant information. We will then contact ICTS with your request. == How to request == To request Shibboleth access, you first need to make sure the domain you wish to use Shibboleth on has valid SSL certificates. Lately ICTS has been pushing that all traffic to the website is already over HTTPS before Shibboleth is issued. For more info you can check [[Getting SSL]] == Deploying Shibboleth == After you have been granted access you can soon start using Shibboleth. The first step is to add the following lines to your .htaccess ShibDisable Off AuthType Shibboleth require shibboleth ShibRequireSession off We disable certain features of Shibboleth here because it will otherwise interfere with any other HTTP-auth options you might be using. Now that you have added this information to .htaccess you are able to serve requests to Shibboleth.sso, if your request is well-formed the sso will handle communication with the IdP (identity provider) of the KU Leuven. A login link follows the following syntax: https://[YOUR_HOSTNAME]/Shibboleth.sso/WAYF/kuleuven?target=[URLENCODED_RETURN_URL] And logout links: https://[YOUR_HOSTNAME]/Shibboleth.sso/Logout?return=[URLENCODED_DISPLAY_URL] It is important to note that on logout the user will stay on the KU Leuven's IdP-page and your link will only be displayed. The user will NOT be redirected (even though this is the normale behaviour according to the Shibboleth documentation). As soon as a user is logged in, his or hers attributes will be available to your application. Attributes are certain properties that an account may have and that supply further information about them. Some examples are: first name, last name, mail, student id. All of these will be available as HTTP headers. But keep in mind that apache might prefix those with REDIRECT_ multiple times (for example when mod_rewrite is used). For an overview of all attributes you can check out http://shib.kuleuven.be/secure/allAttributes More general information on the KU Leuvens implementation can be found on http://shib.kuleuven.be/ . But be aware of the fact that some of the documentation is very outdated (Most notably information about shib 1.3) abe35509f889d32e472cb22b97ee06fa1cc1c59e 220 219 2015-01-29T04:36:04Z Bert 8 /* How to request */ wikitext text/x-wiki Shibboleth is the software powering the Central KU Leuven Login. It's a piece of software used by many universities to supply identification and access management. ULYSSIS works together with ICTS to supply limited access to Shibboleth. We are however only able to supply Shibboleth to those approved by ICTS. In practice all faculty unions will be granted access if they can prove they have the technical ability to use Shibboleth in a safe and privacy friendly way. For other organisations it can be more difficult to get access, therefore it is best to write an extensive explenation of what you plan to do with Shibboleth, why your organisation requires it, what your organisation does, and other relevant information. We will then contact ICTS with your request. == How to request == To request Shibboleth access, you first need to make sure the domain you wish to use Shibboleth on has valid SSL certificates. Lately ICTS has been pushing that all traffic to the website is already over HTTPS before Shibboleth is issued. For more info you can check [[Getting SSL]] If you have SSL set up you need to send an email request Shibboleth to ulyssis@ulyssis.org. The email must contain the following info: * What domain you wish to use Shibboleth on (this must be a single domain, so keep subdomains and www in mind) * What you will be using Shibboleth for and in general what your application will do. This explenation is required by ICTS. If you fail to convince them they will not grant your domain access. * What attributes you wish to use and what you will do with them (and whether you will store them). You can find the list of attributes on https://admin.kuleuven.be/icts/services/aai/attributes * Explicitly state you grant ULYSSIS permission to edit the .htacccess file to be able to export the required Shibboleth Metadata * If you are not a recognised faculty union you will need to include an extra motivation why you require Shibboleth (as noted above) If your application is complete and correct we will file a formal request. We will of course notify you of ICTS' response. == Deploying Shibboleth == After you have been granted access you can soon start using Shibboleth. The first step is to add the following lines to your .htaccess ShibDisable Off AuthType Shibboleth require shibboleth ShibRequireSession off We disable certain features of Shibboleth here because it will otherwise interfere with any other HTTP-auth options you might be using. Now that you have added this information to .htaccess you are able to serve requests to Shibboleth.sso, if your request is well-formed the sso will handle communication with the IdP (identity provider) of the KU Leuven. A login link follows the following syntax: https://[YOUR_HOSTNAME]/Shibboleth.sso/WAYF/kuleuven?target=[URLENCODED_RETURN_URL] And logout links: https://[YOUR_HOSTNAME]/Shibboleth.sso/Logout?return=[URLENCODED_DISPLAY_URL] It is important to note that on logout the user will stay on the KU Leuven's IdP-page and your link will only be displayed. The user will NOT be redirected (even though this is the normale behaviour according to the Shibboleth documentation). As soon as a user is logged in, his or hers attributes will be available to your application. Attributes are certain properties that an account may have and that supply further information about them. Some examples are: first name, last name, mail, student id. All of these will be available as HTTP headers. But keep in mind that apache might prefix those with REDIRECT_ multiple times (for example when mod_rewrite is used). For an overview of all attributes you can check out http://shib.kuleuven.be/secure/allAttributes More general information on the KU Leuvens implementation can be found on http://shib.kuleuven.be/ . But be aware of the fact that some of the documentation is very outdated (Most notably information about shib 1.3) f5dd9a79e2b94227aebfae61e9a0e7275316c5e4 221 220 2015-01-29T04:36:45Z Bert 8 /* How to request */ wikitext text/x-wiki Shibboleth is the software powering the Central KU Leuven Login. It's a piece of software used by many universities to supply identification and access management. ULYSSIS works together with ICTS to supply limited access to Shibboleth. We are however only able to supply Shibboleth to those approved by ICTS. In practice all faculty unions will be granted access if they can prove they have the technical ability to use Shibboleth in a safe and privacy friendly way. For other organisations it can be more difficult to get access, therefore it is best to write an extensive explenation of what you plan to do with Shibboleth, why your organisation requires it, what your organisation does, and other relevant information. We will then contact ICTS with your request. == How to request == To request Shibboleth access, you first need to make sure the domain you wish to use Shibboleth on has valid SSL certificates. Lately ICTS has been pushing that all traffic to the website is already over HTTPS before Shibboleth is issued. For more info you can check [[Getting SSL]] If you have SSL set up you need to send an email to request Shibboleth to ulyssis@ulyssis.org. The email must contain the following info: * What domain you wish to use Shibboleth on (this must be a single domain, so keep subdomains and www in mind) * What you will be using Shibboleth for and in general what your application will do. This explenation is required by ICTS. If you fail to convince them they will not grant your domain access. * What attributes you wish to use and what you will do with them (and whether you will store them). You can find the list of attributes on https://admin.kuleuven.be/icts/services/aai/attributes * Explicitly state you grant ULYSSIS permission to edit the .htacccess file to be able to export the required Shibboleth Metadata * If you are not a recognised faculty union you will need to include an extra motivation why you require Shibboleth (as noted above) If your application is complete and correct we will file a formal request. We will of course notify you of ICTS' response. == Deploying Shibboleth == After you have been granted access you can soon start using Shibboleth. The first step is to add the following lines to your .htaccess ShibDisable Off AuthType Shibboleth require shibboleth ShibRequireSession off We disable certain features of Shibboleth here because it will otherwise interfere with any other HTTP-auth options you might be using. Now that you have added this information to .htaccess you are able to serve requests to Shibboleth.sso, if your request is well-formed the sso will handle communication with the IdP (identity provider) of the KU Leuven. A login link follows the following syntax: https://[YOUR_HOSTNAME]/Shibboleth.sso/WAYF/kuleuven?target=[URLENCODED_RETURN_URL] And logout links: https://[YOUR_HOSTNAME]/Shibboleth.sso/Logout?return=[URLENCODED_DISPLAY_URL] It is important to note that on logout the user will stay on the KU Leuven's IdP-page and your link will only be displayed. The user will NOT be redirected (even though this is the normale behaviour according to the Shibboleth documentation). As soon as a user is logged in, his or hers attributes will be available to your application. Attributes are certain properties that an account may have and that supply further information about them. Some examples are: first name, last name, mail, student id. All of these will be available as HTTP headers. But keep in mind that apache might prefix those with REDIRECT_ multiple times (for example when mod_rewrite is used). For an overview of all attributes you can check out http://shib.kuleuven.be/secure/allAttributes More general information on the KU Leuvens implementation can be found on http://shib.kuleuven.be/ . But be aware of the fact that some of the documentation is very outdated (Most notably information about shib 1.3) becad297a8bcc9e2d48d3a568f60cac010feb52f 0 49 223 2015-02-24T18:05:31Z Covert 18 Created page with "==Installing Joomla on our servers is definitely easy== Installing Joomla on our servers is deffinately easy. You download the install components from the http://joomla.org ..." wikitext text/x-wiki ==Installing Joomla on our servers is definitely easy== Installing Joomla on our servers is deffinately easy. You download the install components from the http://joomla.org joomla-site. Here you get a compressed file (.zip) which you have to extract.. You get a folder with files, those files (so no the folder) you copy via filezilla or an other ftp programme to your www-map on your shellaccount. Afterwards you go to your account, I.E username.ulyssis.be, here you get a notification telling you your <code>wp-config.php</code> has to be created, the easiest way is to follow the wizard, so click on “Create a Configuration File”. Afterwards on ''Let's go!'' which will prompt you for your database credentials: *'''Database Name: ''' if you haven't created a mysql database or user on UCC then you have to create it there. The default database is: username_username. *''''User Name: ''' this is the name you gave during the creation of your mysql account, often this is the same as your username with ULYSSIS. *'''Password: ''' the password hat you gave during the creation of your mysql account *'''Database Host: ''' this is <code>mysql.ulyssis.org</code> * You don't change the last field When you're done click on “Run the install” Here you can give the last few details. Afterwards the install will run by it own and thats it, you installed Joomla. ==Setting up multiple instances of Joomla== If you want to have multiple instances of a Joomla site then you the create a new folder in your homedir from your shell account. Then you make a new virtual host for this directory in UCC. Name: alias.username.ulyssis.be Document root: /home/user/username/new_folder From now on you do al the same steps as for a regular Joomla installation. a61431d124a5ae0a187b8054c347bead31e05fdd 224 223 2015-02-24T18:16:59Z Covert 18 wikitext text/x-wiki ==Installing Joomla on our servers is definitely easy== Installing Joomla on our servers is deffinately easy. You download the install components from the http://joomla.org joomla-site. Here you get a compressed file (.zip) which you have to extract.. You get a folder with files, those files (so no the folder) you copy via filezilla or an other ftp programme to your www-map on your shellaccount. Afterwards you go to your account, I.E username.ulyssis.be, here you get a notification telling you your needs to be configured. The fist part is the "main configuration" which will be individual for every user. Afterwards click on ''Next'' which will prompt you for your database credentials & information: *'''Databasetype: ''' Select ''MySQL'' from the dropdown. *''''Hostname: ''' this is the location of the database server, use <code>mysql.ulyssis.org</code>. *''''Username: ''' this is the name you gave during the creation of your mysql account, often this is the same as your username with ULYSSIS. *'''password: ''' the password hat you gave during the creation of your mysql account * You don't change the last two fields When you're done click on “Next” twice since ftp is already configured. Here you can see the last few details. Afterwards the install will run by it own and thats it, you installed Joomla. ==Setting up multiple instances of Joomla== If you want to have multiple instances of a Joomla site then you the create a new folder in your homedir from your shell account. Then you make a new virtual host for this directory in UCC. Name: alias.username.ulyssis.be Document root: /home/user/username/new_folder From now on you do al the same steps as for a regular Joomla installation. 02f3af802493959ac6dd80f6bf784659d2978d3a 0 50 225 2015-02-24T18:49:06Z Covert 18 Created page with "==Installing Drupal on our servers is definitely easy== Installing Drupal on our servers is deffinately easy. You download the install components from the http://drupal.org ..." wikitext text/x-wiki ==Installing Drupal on our servers is definitely easy== Installing Drupal on our servers is deffinately easy. You download the install components from the http://drupal.org drupal-site. Here you get a compressed file (.tar.gz or .zip) which you have to extract.. You get a folder with files, those files (so no the folder) you copy via filezilla or an other ftp programme to your www-map on your shellaccount. Afterwards you go to your account, I.E username.ulyssis.be, here you get a notification telling you to select a profile, if you do not know which to choose select the standard one. Afterwards click on ''Save and Continue'' which will prompt you for your langauge settings. Click on ''Save and Continue'' again when finished. follow the steps detaild in the ''Verify requirements'' page and continue. Now the installer will ask you for your database configuration: *'''Database Name: ''' if you haven't created a mysql database or user on UCC then you have to create it there. The default database is: username_username. *''''User Name: ''' this is the name you gave during the creation of your mysql account, often this is the same as your username with ULYSSIS. *'''Password: ''' the password hat you gave during the creation of your mysql account *'''Database Host: ''' this is <code>mysql.ulyssis.org</code> When you're done click on “Save and Continue” Here you can give the last few details. Afterwards the install will run by it own and ask you some basic questions about the site and login for drupal,there it is your Drupal installation. ==Setting up multiple instances of Drupal== If you want to have multiple instances of a Wordpress site then you the create a new folder in your homedir from your shell account. Then you make a new virtual host for this directory in UCC. Name: alias.username.ulyssis.be Document root: /home/user/username/new_folder From now on you do al the same steps as for a regular wordpress installation. 787e6fd826e79147107bbba48077eff3f0873098 0 13 226 131 2015-04-21T01:44:13Z Bert 8 wikitext text/x-wiki If you want to use [http://git-scm.com/ git] for version control to work privately on personal projects, or collaborate with others on projects, you can use GitLab for central repositories, and for tracking bugs. = Accessing GitLab = You can access our GitLab server at https://gitlab.ulyssis.org. You can log in with your standard ULYSSIS username and password. = Getting started with Git = If you want to get acquainted with git, these are good free resources: * [https://try.github.io Try Git]: an interactive introduction to git * [http://git-scm.com/book Pro Git]: a book that you can read for free online * [http://git-scm.com/docs The official Git reference documentation] = Guest users = Sadly, we do not provide automated guest user support for GitLab yet, as we do for Subversion. If not everyone who works on your project has their own ULYSSIS account, you can request a Gitlab guest account via email. You simply send an email with the guest account's username and email address to ulyssis@ulyssis.org and we will create it. 4cc5beb6ee71676768231e50ba231a4e13ebbdd6 0 50 240 225 2015-09-01T02:36:47Z Bert 8 /* Setting up multiple instances of Drupal */ wikitext text/x-wiki ==Installing Drupal on our servers is definitely easy== Installing Drupal on our servers is deffinately easy. You download the install components from the http://drupal.org drupal-site. Here you get a compressed file (.tar.gz or .zip) which you have to extract.. You get a folder with files, those files (so no the folder) you copy via filezilla or an other ftp programme to your www-map on your shellaccount. Afterwards you go to your account, I.E username.ulyssis.be, here you get a notification telling you to select a profile, if you do not know which to choose select the standard one. Afterwards click on ''Save and Continue'' which will prompt you for your langauge settings. Click on ''Save and Continue'' again when finished. follow the steps detaild in the ''Verify requirements'' page and continue. Now the installer will ask you for your database configuration: *'''Database Name: ''' if you haven't created a mysql database or user on UCC then you have to create it there. The default database is: username_username. *''''User Name: ''' this is the name you gave during the creation of your mysql account, often this is the same as your username with ULYSSIS. *'''Password: ''' the password hat you gave during the creation of your mysql account *'''Database Host: ''' this is <code>mysql.ulyssis.org</code> When you're done click on “Save and Continue” Here you can give the last few details. Afterwards the install will run by it own and ask you some basic questions about the site and login for drupal,there it is your Drupal installation. ==Setting up multiple instances of Drupal== If you want to have multiple instances of a Drupal site there are two options. The multiple instances can either share drupal code or be fully seperate. For fully seperate installs you can simply create a (sub)folder to store another copy of the drupal code in. You can then access it either from your default domain or have us attach another domain to it for you, more info about that on [[Adding domain names]] If you wish for multiple websites to share the same codebase it is easiest to use multiple domains. More information about how to set this up in your drupal is available in the drupal documentation: https://www.drupal.org/documentation/install/multi-site. As soon as you have made your preperations you can contact us about hooking up the domain name, more info about that on [[Adding domain names]] 95d70b21be644a87f8676021e97945248fd02c02 250 240 2015-10-27T12:02:53Z Vincenttc 21 wikitext text/x-wiki ==Installing Drupal on our servers is definitely easy== Installing Drupal on our servers is definitely easy. You download the install components from the http://drupal.org drupal-site. Here you get a compressed file (.tar.gz or .zip) which you have to extract.. You get a folder with files, those files (so no the folder) you copy via filezilla or an other ftp programme to your www-map on your shellaccount. Afterwards you go to your account, I.E username.ulyssis.be, here you get a notification telling you to select a profile, if you do not know which to choose select the standard one. Afterwards click on ''Save and Continue'' which will prompt you for your langauge settings. Click on ''Save and Continue'' again when finished. follow the steps detaild in the ''Verify requirements'' page and continue. Now the installer will ask you for your database configuration: *'''Database Name: ''' if you haven't created a mysql database or user on UCC then you have to create it there. The default database is: username_username. *''''User Name: ''' this is the name you gave during the creation of your mysql account, often this is the same as your username with ULYSSIS. *'''Password: ''' the password hat you gave during the creation of your mysql account *'''Database Host: ''' this is <code>mysql.ulyssis.org</code> When you're done click on “Save and Continue” Here you can give the last few details. Afterwards the install will run by it own and ask you some basic questions about the site and login for drupal,there it is your Drupal installation. ==Setting up multiple instances of Drupal== If you want to have multiple instances of a Drupal site there are two options. The multiple instances can either share drupal code or be fully seperate. For fully seperate installs you can simply create a (sub)folder to store another copy of the drupal code in. You can then access it either from your default domain or have us attach another domain to it for you, more info about that on [[Adding domain names]] If you wish for multiple websites to share the same codebase it is easiest to use multiple domains. More information about how to set this up in your drupal is available in the drupal documentation: https://www.drupal.org/documentation/install/multi-site. As soon as you have made your preperations you can contact us about hooking up the domain name, more info about that on [[Adding domain names]] 39d1a03657b8803725f3aa2c5da31371f816525f 0 20 241 222 2015-09-03T18:43:44Z Andreas 20 wikitext text/x-wiki ==Installing wordpress on our servers is definitely easy== Installing wordpress on our servers is deffinately easy. You download the install components from the http://wordpress.org wordpress-site. Here you get a compressed file (.tar.gz or .zip) which you have to extract.. You get a folder with files, those files (so no the folder) you copy via filezilla or an other ftp programme to your www-map on your shellaccount. Afterwards you go to your account, I.E username.ulyssis.be, here you get a notification telling you your <code>wp-config.php</code> has to be created, the easiest way is to follow the wizard, so click on “Create a Configuration File”. Afterwards on ''Let's go!'' which will prompt you for your database credentials: *'''Database Name: ''' if you haven't created a mysql database or user on UCC then you have to create it there. The default database is: username_username. *''''User Name: ''' this is the name you gave during the creation of your mysql account, often this is the same as your username with ULYSSIS. *'''Password: ''' the password hat you gave during the creation of your mysql account *'''Database Host: ''' this is <code>mysql.ulyssis.org</code> * You don't change the last field When you're done click on “Run the install” Here you can give the last few details. Afterwards the install will run by it own and thats it, you installed wordpress. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site then you the create a new folder in your homedir from your shell account. You need a new virtual host, send us an email and we will create one for you. After your new virtual host has been configured, you need to do al the same steps as for a regular wordpress installation. 0c9c181eb02f88407e805e7a8f984fdd95e1c86e 242 241 2015-09-03T18:52:22Z Andreas 20 wikitext text/x-wiki ==Installing wordpress on our servers is definitely easy== Installing wordpress on our servers is deffinately easy. You download the install components from the http://wordpress.org wordpress-site. Here you get a compressed file (.tar.gz or .zip) which you have to extract.. You get a folder with files, those files (so no the folder) you copy via filezilla or an other ftp programme to your www-map on your shellaccount. Afterwards you go to your account, I.E username.ulyssis.be, here you get a notification telling you your <code>wp-config.php</code> has to be created, the easiest way is to follow the wizard, so click on “Create a Configuration File”. Afterwards on ''Let's go!'' which will prompt you for your database credentials: *'''Database Name: ''' if you haven't created a mysql database or user on UCC then you have to create it there. The default database is: username_username. *''''User Name: ''' this is the name you gave during the creation of your mysql account, often this is the same as your username with ULYSSIS. *'''Password: ''' the password hat you gave during the creation of your mysql account *'''Database Host: ''' this is <code>mysql.ulyssis.org</code> * You don't change the last field When you're done click on “Run the install” Here you can give the last few details. Afterwards the install will run by it own and thats it, you installed wordpress. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site then you the create a new folder in your homedir from your shell account. You need a new virtual host, send us an email and we will create one for you. After your new virtual host has been configured, you need to do al the same steps as for a regular wordpress installation. You could also use the Wordpress https://wordpress.org/support/forum/multisite multisite option. 043f510f1e69f96ce80033f60aed3d96fe00835a 243 242 2015-09-03T18:54:22Z Andreas 20 /* Setting up multiple instances of Wordpress */ wikitext text/x-wiki ==Installing wordpress on our servers is definitely easy== Installing wordpress on our servers is deffinately easy. You download the install components from the http://wordpress.org wordpress-site. Here you get a compressed file (.tar.gz or .zip) which you have to extract.. You get a folder with files, those files (so no the folder) you copy via filezilla or an other ftp programme to your www-map on your shellaccount. Afterwards you go to your account, I.E username.ulyssis.be, here you get a notification telling you your <code>wp-config.php</code> has to be created, the easiest way is to follow the wizard, so click on “Create a Configuration File”. Afterwards on ''Let's go!'' which will prompt you for your database credentials: *'''Database Name: ''' if you haven't created a mysql database or user on UCC then you have to create it there. The default database is: username_username. *''''User Name: ''' this is the name you gave during the creation of your mysql account, often this is the same as your username with ULYSSIS. *'''Password: ''' the password hat you gave during the creation of your mysql account *'''Database Host: ''' this is <code>mysql.ulyssis.org</code> * You don't change the last field When you're done click on “Run the install” Here you can give the last few details. Afterwards the install will run by it own and thats it, you installed wordpress. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site then you the create a new folder in your homedir from your shell account. You need a new virtual host, send us an email and we will create one for you. After your new virtual host has been configured, you need to do al the same steps as for a regular wordpress installation. You could also use the Wordpress [https://wordpress.org/support/forum/multisite multisite] option. 425dda36c74e8153956092d56465b64d28cfb294 244 243 2015-09-03T18:55:49Z Andreas 20 /* Setting up multiple instances of Wordpress */ wikitext text/x-wiki ==Installing wordpress on our servers is definitely easy== Installing wordpress on our servers is deffinately easy. You download the install components from the http://wordpress.org wordpress-site. Here you get a compressed file (.tar.gz or .zip) which you have to extract.. You get a folder with files, those files (so no the folder) you copy via filezilla or an other ftp programme to your www-map on your shellaccount. Afterwards you go to your account, I.E username.ulyssis.be, here you get a notification telling you your <code>wp-config.php</code> has to be created, the easiest way is to follow the wizard, so click on “Create a Configuration File”. Afterwards on ''Let's go!'' which will prompt you for your database credentials: *'''Database Name: ''' if you haven't created a mysql database or user on UCC then you have to create it there. The default database is: username_username. *''''User Name: ''' this is the name you gave during the creation of your mysql account, often this is the same as your username with ULYSSIS. *'''Password: ''' the password hat you gave during the creation of your mysql account *'''Database Host: ''' this is <code>mysql.ulyssis.org</code> * You don't change the last field When you're done click on “Run the install” Here you can give the last few details. Afterwards the install will run by it own and thats it, you installed wordpress. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site then you the create a new folder in your homedir from your shell account. You need a new virtual host, send us an email and we will create one for you. After your new virtual host has been configured, you need to do al the same steps as for a regular wordpress installation. You could also use the Wordpress [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about the multisite option [https://wordpress.org/support/forum/multisite here]. 01fe23d78275f5da2c0a76c121548af8c650ff9a 249 244 2015-10-27T12:02:21Z Vincenttc 21 wikitext text/x-wiki ==Installing wordpress on our servers is definitely easy== Installing wordpress on our servers is definitely easy. You download the install components from the http://wordpress.org wordpress-site. Here you get a compressed file (.tar.gz or .zip) which you have to extract.. You get a folder with files, those files (so no the folder) you copy via filezilla or an other ftp programme to your www-map on your shellaccount. Afterwards you go to your account, I.E username.ulyssis.be, here you get a notification telling you your <code>wp-config.php</code> has to be created, the easiest way is to follow the wizard, so click on “Create a Configuration File”. Afterwards on ''Let's go!'' which will prompt you for your database credentials: *'''Database Name: ''' if you haven't created a mysql database or user on UCC then you have to create it there. The default database is: username_username. *''''User Name: ''' this is the name you gave during the creation of your mysql account, often this is the same as your username with ULYSSIS. *'''Password: ''' the password hat you gave during the creation of your mysql account *'''Database Host: ''' this is <code>mysql.ulyssis.org</code> * You don't change the last field When you're done click on “Run the install” Here you can give the last few details. Afterwards the install will run by it own and thats it, you installed wordpress. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site then you the create a new folder in your homedir from your shell account. You need a new virtual host, send us an email and we will create one for you. After your new virtual host has been configured, you need to do al the same steps as for a regular wordpress installation. You could also use the Wordpress [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about the multisite option [https://wordpress.org/support/forum/multisite here]. 19ef6260c36be900a645201092ac2144c99ff5ca 0 49 245 224 2015-09-03T18:58:13Z Andreas 20 wikitext text/x-wiki ==Installing Joomla on our servers is definitely easy== Installing Joomla on our servers is deffinately easy. You download the install components from the http://joomla.org joomla-site. Here you get a compressed file (.zip) which you have to extract.. You get a folder with files, those files (so no the folder) you copy via filezilla or an other ftp programme to your www-map on your shellaccount. Afterwards you go to your account, I.E username.ulyssis.be, here you get a notification telling you your needs to be configured. The fist part is the "main configuration" which will be individual for every user. Afterwards click on ''Next'' which will prompt you for your database credentials & information: *'''Databasetype: ''' Select ''MySQL'' from the dropdown. *''''Hostname: ''' this is the location of the database server, use <code>mysql.ulyssis.org</code>. *''''Username: ''' this is the name you gave during the creation of your mysql account, often this is the same as your username with ULYSSIS. *'''password: ''' the password hat you gave during the creation of your mysql account * You don't change the last two fields When you're done click on “Next” twice since ftp is already configured. Here you can see the last few details. Afterwards the install will run by it own and thats it, you installed Joomla. ==Setting up multiple instances of Joomla== If you want to have multiple instances of a Joomla site then you the create a new folder in your homedir from your shell account. You need a new virtual host, you can send us an [mailto:ulyssis@ulyssis.org email] and we will create one for you. After your new virtual host is ready, you need to do all the same steps as for a regular Joomla installation. 36d9e86419227294cc51f3dbcdba973659475aff 246 245 2015-09-03T19:00:17Z Andreas 20 wikitext text/x-wiki ==Installing Joomla on our servers is definitely easy== Installing Joomla on our servers is deffinately easy. You download the install components from the http://joomla.org joomla-site. Here you get a compressed file (.zip) which you have to extract.. You get a folder with files, those files (so no the folder) you copy via filezilla or an other ftp programme to your www-map on your shellaccount. Afterwards you go to your account, I.E username.ulyssis.be, here you get a notification telling you your needs to be configured. The fist part is the "main configuration" which will be individual for every user. Afterwards click on ''Next'' which will prompt you for your database credentials & information: *'''Databasetype: ''' Select ''MySQL'' from the dropdown. *''''Hostname: ''' this is the location of the database server, use <code>mysql.ulyssis.org</code>. *''''Username: ''' this is the name you gave during the creation of your mysql account, often this is the same as your username with ULYSSIS. *'''password: ''' the password hat you gave during the creation of your mysql account * You don't change the last two fields When you're done click on “Next” twice since ftp is already configured. Here you can see the last few details. Afterwards the install will run by it own and thats it, you installed Joomla. ==Setting up multiple instances of Joomla== If you want to have multiple instances of a Joomla site then you the create a new folder in your homedir from your shell account. You need a new virtual host, you can send us an [mailto:ulyssis@ulyssis.org email] and we will create one for you. After your new virtual host is ready, you need to do all the same steps as for a regular Joomla installation. Another option is to use the Joomla [https://docs.joomla.org/Multiple_Domains_and_Web_Sites_in_a_single_Joomla!_installation multisite] option. 3e756d8d70e06cda01360160d2a71be9f29ef3c2 251 246 2015-10-27T12:03:21Z Vincenttc 21 wikitext text/x-wiki ==Installing Joomla on our servers is definitely easy== Installing Joomla on our servers is definitely easy. You download the install components from the http://joomla.org joomla-site. Here you get a compressed file (.zip) which you have to extract.. You get a folder with files, those files (so no the folder) you copy via filezilla or an other ftp programme to your www-map on your shellaccount. Afterwards you go to your account, I.E username.ulyssis.be, here you get a notification telling you your needs to be configured. The fist part is the "main configuration" which will be individual for every user. Afterwards click on ''Next'' which will prompt you for your database credentials & information: *'''Databasetype: ''' Select ''MySQL'' from the dropdown. *''''Hostname: ''' this is the location of the database server, use <code>mysql.ulyssis.org</code>. *''''Username: ''' this is the name you gave during the creation of your mysql account, often this is the same as your username with ULYSSIS. *'''password: ''' the password hat you gave during the creation of your mysql account * You don't change the last two fields When you're done click on “Next” twice since ftp is already configured. Here you can see the last few details. Afterwards the install will run by it own and thats it, you installed Joomla. ==Setting up multiple instances of Joomla== If you want to have multiple instances of a Joomla site then you the create a new folder in your homedir from your shell account. You need a new virtual host, you can send us an [mailto:ulyssis@ulyssis.org email] and we will create one for you. After your new virtual host is ready, you need to do all the same steps as for a regular Joomla installation. Another option is to use the Joomla [https://docs.joomla.org/Multiple_Domains_and_Web_Sites_in_a_single_Joomla!_installation multisite] option. 9d771fa3bfdeb1a6971dadcd8c7729df5df645a8 0 3 247 234 2015-09-09T22:52:29Z Warreee 10 /* Webserver */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2014]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Keeping your website secure]] * [[Preventing spam on your website]] * [[Preventing spam on Wordpress]] * [[Preventing spam on MediaWiki]] * [[Preventing spam on forums]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Add an alias in Gmail]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 5d3fdcf84f472c8e96c0530a25c8cd07454db8f6 263 247 2016-02-16T12:07:53Z Covert 18 /* Security & anti-spam */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2014]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Keeping your website secure]] * [[Preventing spam on your website]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Preventing spam on forums]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Add an alias in Gmail]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> </div> __NOTOC__ b6fc0b9d87e7ae8583367c7ea2c9664a71f6d623 274 263 2016-03-29T16:20:38Z Covert 18 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2014]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Keeping your website secure]] * [[Preventing spam on your website]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Preventing spam on forums]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Add an alias in Gmail]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Development == * [[Local web development]] </div><div style="width:45%;float:left"> </div> __NOTOC__ 6a2913b09efdce99f0f269cd34696df7d0bc77b3 0 53 248 2015-09-09T23:03:51Z Warreee 10 Basic authentication in PHP with CGI workaround wikitext text/x-wiki Because in our webserversetup PHP is installed as a common gateway interface (CGI) basic authentication will not work in its usual way. There is however a workaround. First add a .htaccess file with following code in it: ''' <IfModule mod_rewrite.c> RewriteEngine on \n RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization},L] </IfModule> ''' Next add the following line to your script right before the authentication: ''' list($_SERVER['PHP_AUTH_USER'], $_SERVER['PHP_AUTH_PW']) = explode(':' , base64_decode(substr($_SERVER['HTTP_AUTHORIZATION'], 6))); ''' Now your script should work with basic authentication. 5562838af0fa58c4c5d827ccf945bbd888fee05c 0 37 252 179 2015-12-06T09:21:02Z Rockinroel 9 /* Example: Django */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</pre> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. In order to do that, you have to set the modification date of the starter script to a more recent date: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.fastcgi import runfastcgi runfastcgi(method="threaded", daemonize="false")</pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/1.6/intro/tutorial01/ The Django tutorial] * [https://docs.djangoproject.com/en/1.6/howto/deployment/fastcgi/#apache-shared-hosting Running Django on a shared-hosting provider with Apache] a956c530a8c6e9c4e16213ff16a35168bc0e7e78 253 252 2015-12-06T09:25:40Z Rockinroel 9 /* Restarting your application */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</pre> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than were it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.fastcgi import runfastcgi runfastcgi(method="threaded", daemonize="false")</pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/1.6/intro/tutorial01/ The Django tutorial] * [https://docs.djangoproject.com/en/1.6/howto/deployment/fastcgi/#apache-shared-hosting Running Django on a shared-hosting provider with Apache] 2530d516c9dfab2812294c237ebf705df18d2eeb 264 253 2016-02-22T19:57:54Z Rockinroel 9 wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</pre> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than were it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> Or, for Python 3: <pre>virtualenv ~/.venv --python=python3</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/1.6/intro/tutorial01/ The Django tutorial] * [https://docs.djangoproject.com/en/1.6/howto/deployment/fastcgi/#apache-shared-hosting Running Django on a shared-hosting provider with Apache] 7a79409ffcb28941e539301e56cc1c7c15402733 267 264 2016-02-22T20:04:53Z Rockinroel 9 wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</pre> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than were it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> Or, for Python 3: <pre>virtualenv ~/.venv --python=python3</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [https://docs.djangoproject.com/en/stable/howto/deployment/fastcgi/#apache-shared-hosting Running Django on a shared-hosting provider with Apache] 8888b20eed72af04cd847c1b64ae79fd928071a8 268 267 2016-02-22T20:06:04Z Rockinroel 9 wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</pre> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than were it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> Or, for Python 3: <pre>virtualenv ~/.venv --python=python3</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [http://flask.pocoo.org/docs/0.10/deploying/fastcgi/ Flask documentation for FastCGI] 0e60ab69176674f0b95a67225e57f24ba57b910f 0 54 254 2015-12-18T19:14:32Z Covert 18 Created page with "==google's recaptcha== ===What is recaptcha and how/will it help prevent spam ?=== For answers to those questions you can look at google's page about recaptcha(https://google...." wikitext text/x-wiki ==google's recaptcha== ===What is recaptcha and how/will it help prevent spam ?=== For answers to those questions you can look at google's page about recaptcha(https://google.com/recaptcha) ===Instalation=== This instalation guide requires mediawiki '''1.26''' or higher * Go to google's recaptcha administrator page(https://www.google.com/recaptcha/admin) and register your site * Open your *LocalSettings.php* file which is in your mediawiki instalation folder ** put the following piece of text in the above mentioned file <code> require_once "$IP/extensions/ConfirmEdit/ConfirmEdit.php"; wfLoadExtension( 'ConfirmEdit/ReCaptchaNoCaptcha' ); $wgCaptchaClass = 'ReCaptchaNoCaptcha'; $wgReCaptchaSiteKey = ' '''your public/site key here''' '; $wgReCaptchaSecretKey = ' '''your private key here''' '; </code> exmaple of public and private key (https://i.imgur.com/vGJKEXx.png) * mediawiki wil start loading recaptcha in the background and once done wil start using recaptcha for defending you from bots b759b4a22dd4e92838f6cd39c116f0410f28905d 256 254 2016-02-07T21:37:23Z Covert 18 /* google's recaptcha */ wikitext text/x-wiki ==google's recaptcha== ===What is recaptcha and how/will it help prevent spam ?=== For answers to those questions you can look at google's page about recaptcha(https://google.com/recaptcha) ===Installation=== This installation guide requires mediawiki '''1.26''' or higher * Go to google's recaptcha administrator page(https://www.google.com/recaptcha/admin) and register your site * Open your *LocalSettings.php* file which is in your mediawiki instalation folder ** put the following piece of text in the above mentioned file <code> require_once "$IP/extensions/ConfirmEdit/ConfirmEdit.php"; wfLoadExtension( 'ConfirmEdit/ReCaptchaNoCaptcha' ); $wgCaptchaClass = 'ReCaptchaNoCaptcha'; $wgReCaptchaSiteKey = ' '''your public/site key here''' '; $wgReCaptchaSecretKey = ' '''your private key here''' '; </code> example of public and private key (https://i.imgur.com/vGJKEXx.png) * mediawiki wil start loading recaptcha in the background and once done wil start using recaptcha for defending you from bots 6b5cb678f0d142bbd83d2b6ae7e3b6acef001027 257 256 2016-02-07T21:37:47Z Covert 18 /* google's recaptcha */ wikitext text/x-wiki ==Google's recaptcha== ===What is recaptcha and how/will it help prevent spam ?=== For answers to those questions you can look at google's page about recaptcha(https://google.com/recaptcha) ===Installation=== This installation guide requires mediawiki '''1.26''' or higher * Go to google's recaptcha administrator page(https://www.google.com/recaptcha/admin) and register your site * Open your *LocalSettings.php* file which is in your mediawiki instalation folder ** put the following piece of text in the above mentioned file <code> require_once "$IP/extensions/ConfirmEdit/ConfirmEdit.php"; wfLoadExtension( 'ConfirmEdit/ReCaptchaNoCaptcha' ); $wgCaptchaClass = 'ReCaptchaNoCaptcha'; $wgReCaptchaSiteKey = ' '''your public/site key here''' '; $wgReCaptchaSecretKey = ' '''your private key here''' '; </code> example of public and private key (https://i.imgur.com/vGJKEXx.png) * mediawiki wil start loading recaptcha in the background and once done wil start using recaptcha for defending you from bots b214d8f25b87d2b4cc8134cb26d629fd934f757b 261 257 2016-02-07T21:40:01Z Covert 18 /* Installation */ wikitext text/x-wiki ==Google's recaptcha== ===What is recaptcha and how/will it help prevent spam ?=== For answers to those questions you can look at google's page about recaptcha(https://google.com/recaptcha) ===Installation=== This installation guide requires mediawiki '''1.26''' or higher * Go to google's recaptcha administrator page(https://www.google.com/recaptcha/admin) and register your site * Open your *LocalSettings.php* file which is in your mediawiki instalation folder ** Put the following piece of text in the above mentioned file <code> require_once "$IP/extensions/ConfirmEdit/ConfirmEdit.php"; wfLoadExtension( 'ConfirmEdit/ReCaptchaNoCaptcha' ); $wgCaptchaClass = 'ReCaptchaNoCaptcha'; $wgReCaptchaSiteKey = ' '''your public/site key here''' '; $wgReCaptchaSecretKey = ' '''your private key here''' '; </code> example of public and private key (https://i.imgur.com/vGJKEXx.png) * mediawiki wil start loading recaptcha in the background and once done wil start using recaptcha for defending you from bots 08bb14607c9006ea509b2fbe1808720971f0556a 0 55 255 2016-02-07T21:32:11Z Covert 18 Created page with "==google's recaptcha== ===What is recaptcha and how/will it help prevent spam ?=== For answers to those questions you can look at google's page about recaptcha(https://google...." wikitext text/x-wiki ==google's recaptcha== ===What is recaptcha and how/will it help prevent spam ?=== For answers to those questions you can look at google's page about recaptcha(https://google.com/recaptcha) ===Installation=== This installation guide requires Wordpress '''3.8''' or higher * Go to the Wordpress recaptcha plugin site (https://wordpress.org/plugins/google-captcha/) and download the latest version on our site in to the Wordpress installation folder * extract the contents of the archive in to '''./wp-content/plugins/ ''' * Navigate to the Wordpress admin dashword and select the plugin link (on the left side of the dashboard) * activate the google recaptcha plugin * this wil give you a link to the configuration page of the plugin or you can select the settings link located below the plugin * follow the instruction on the page and depending on you configuration recaptcha wil start ===Video instructions=== The makers of the Wordpress recaptcha have a video tutorial. This will supplement the above instructions, particularly the last step. (https://youtu.be/RUJ9VwZLFSY) 2c5ede922fe26df4585091882d7d9bab8cc4d46c 258 255 2016-02-07T21:38:09Z Covert 18 /* google's recaptcha */ wikitext text/x-wiki ==Google's recaptcha== ===What is recaptcha and how/will it help prevent spam ?=== For answers to those questions you can look at google's page about recaptcha(https://google.com/recaptcha) ===Installation=== This installation guide requires Wordpress '''3.8''' or higher * go to the Wordpress recaptcha plugin site (https://wordpress.org/plugins/google-captcha/) and download the latest version on our site in to the Wordpress installation folder * extract the contents of the archive in to '''./wp-content/plugins/ ''' * Navigate to the Wordpress admin dashword and select the plugin link (on the left side of the dashboard) * activate the google recaptcha plugin * this wil give you a link to the configuration page of the plugin or you can select the settings link located below the plugin * follow the instruction on the page and depending on you configuration recaptcha wil start ===Video instructions=== The makers of the Wordpress recaptcha have a video tutorial. This will supplement the above instructions, particularly the last step. (https://youtu.be/RUJ9VwZLFSY) 09702a1bafa00425995cb48e3412e4f23f2624e6 259 258 2016-02-07T21:38:56Z Covert 18 /* Installation */ wikitext text/x-wiki ==Google's recaptcha== ===What is recaptcha and how/will it help prevent spam ?=== For answers to those questions you can look at google's page about recaptcha(https://google.com/recaptcha) ===Installation=== This installation guide requires Wordpress '''3.8''' or higher * Go to the Wordpress recaptcha plugin site (https://wordpress.org/plugins/google-captcha/) and download the latest version on our site in to the Wordpress installation folder * Extract the contents of the archive in to '''./wp-content/plugins/ ''' * Navigate to the Wordpress admin dashword and select the plugin link (on the left side of the dashboard) * Activate the google recaptcha plugin * This wil give you a link to the configuration page of the plugin or you can select the settings link located below the plugin * Follow the instruction on the page and depending on you configuration recaptcha wil start ===Video instructions=== The makers of the Wordpress recaptcha have a video tutorial. This will supplement the above instructions, particularly the last step. (https://youtu.be/RUJ9VwZLFSY) 400ef8b9826f56abe562c153329fa58406d1ec83 260 259 2016-02-07T21:39:09Z Covert 18 /* Installation */ wikitext text/x-wiki ==Google's recaptcha== ===What is recaptcha and how/will it help prevent spam ?=== For answers to those questions you can look at google's page about recaptcha(https://google.com/recaptcha) ===Installation=== This installation guide requires Wordpress '''3.8''' or higher * Go to the Wordpress recaptcha plugin site (https://wordpress.org/plugins/google-captcha/) and download the latest version on our site in to the Wordpress installation folder * Extract the contents of the archive in to '''./wp-content/plugins/ ''' * Navigate to the Wordpress admin dashbord and select the plugin link (on the left side of the dashboard) * Activate the google recaptcha plugin * This wil give you a link to the configuration page of the plugin or you can select the settings link located below the plugin * Follow the instruction on the page and depending on you configuration recaptcha wil start ===Video instructions=== The makers of the Wordpress recaptcha have a video tutorial. This will supplement the above instructions, particularly the last step. (https://youtu.be/RUJ9VwZLFSY) dc01e5232f41a456e75454534d90ebe996aed0e3 262 260 2016-02-07T21:41:35Z Covert 18 /* Installation */ wikitext text/x-wiki ==Google's recaptcha== ===What is recaptcha and how/will it help prevent spam ?=== For answers to those questions you can look at google's page about recaptcha(https://google.com/recaptcha) ===Installation=== This installation guide requires Wordpress '''3.8''' or higher * Go to the Wordpress recaptcha plugin site (https://wordpress.org/plugins/google-captcha/) and download the latest version on our site in to the Wordpress installation folder * Extract the contents of the archive in to '''./wp-content/plugins/ ''' * Navigate to the Wordpress admin dashbord and select the plugin link (on the left side of the dashboard) * Activate the google recaptcha plugin * This will give you a link to the configuration page of the plugin or you can select the settings link located below the plugin * Follow the instructions on the page and depending on your configuration recaptcha will start ===Video instructions=== The makers of the Wordpress recaptcha have a video tutorial. This will supplement the above instructions, particularly the last step. (https://youtu.be/RUJ9VwZLFSY) 2daa8ca5259d42413547d92f9200cde157cd89cb 0 56 265 2016-02-22T19:58:55Z Covert 18 Created page with "==Google's recaptcha== ===What is recaptcha and how/will it help prevent spam ?=== For answers to those questions you can look at google's page about recaptcha(https://google...." wikitext text/x-wiki ==Google's recaptcha== ===What is recaptcha and how/will it help prevent spam ?=== For answers to those questions you can look at google's page about recaptcha(https://google.com/recaptcha) ===Installation=== This installation guide requires drupal '''6,7 or preferably 8''' (or higher). '''Note this installation requires captcha and recaptcha, these are different plugins and not a type error.''' * Go to google's recaptcha administrator page(https://www.google.com/recaptcha/admin) and register your site * Go to drupal's captcha page and download the appropriate version at the bottom of the page (https://www.drupal.org/project/captcha) * Go to drupal's recaptcha page and download the appropriate version at the bottom of the page (https://www.drupal.org/project/recaptcha) ** Extract the archives into '''sites/all/modules/[recaptcha/captcha]'''respectively and relative to your own drupal installation '''(this folder may need to be created manually)''' * Now navigate to your drupal administration page in your browser (/admin/modules) ** Search for captcha and enable it ** Search for recaptcha and enable it * Once complete it is advisable to configure your captcha setting in the web interface (/admin/config/people/captcha) 328d7091670493a3c6796f60962173b6a0e8d658 266 265 2016-02-22T20:02:05Z Covert 18 /* Installation */ wikitext text/x-wiki ==Google's recaptcha== ===What is recaptcha and how/will it help prevent spam ?=== For answers to those questions you can look at google's page about recaptcha(https://google.com/recaptcha) ===Installation=== This installation guide requires drupal '''6,7 or preferably 8''' (or higher). '''Note this installation requires captcha and recaptcha, these are different plugins and not a type error.''' * Go to drupal's captcha page and download the appropriate version at the bottom of the page (https://www.drupal.org/project/captcha) * Go to drupal's recaptcha page and download the appropriate version at the bottom of the page (https://www.drupal.org/project/recaptcha) ** Extract the archives into '''sites/all/modules/[recaptcha/captcha]'''respectively and relative to your own drupal installation '''(this folder may need to be created manually)''' * Now navigate to your drupal administration page in your browser (/admin/modules) ** Search for captcha and enable it ** Search for recaptcha and enable it * Once complete it is '''critical''' to configure your captcha setting in the web interface (/admin/config/people/captcha) '''and do not forget to enable the captcha-points (/admin/config/people/captcha/captcha-points). 2dab5989938a9f038f1f8160c7ac5ed9eee49904 0 57 269 2016-02-23T14:47:34Z Covert 18 Created page with "==Google's recaptcha== ===What is recaptcha and how/will it help prevent spam ?=== For answers to those questions you can look at google's page about recaptcha(https://google...." wikitext text/x-wiki ==Google's recaptcha== ===What is recaptcha and how/will it help prevent spam ?=== For answers to those questions you can look at google's page about recaptcha(https://google.com/recaptcha) ===Installation=== This installation guide requires joomla '''3.4''' (or higher). '''Note this installation requires captcha and recaptcha, these are different plugins and not a type error.''' * Go to drupal's captcha page and download the appropriate version at the bottom of the page (https://www.drupal.org/project/captcha) * Go to drupal's recaptcha page and download the appropriate version at the bottom of the page (https://www.drupal.org/project/recaptcha) ** Extract the archives into '''sites/all/modules/[recaptcha/captcha]'''respectively and relative to your own drupal installation '''(this folder may need to be created manually)''' * Now navigate to your drupal administration page in your browser (/admin/modules) ** Search for captcha and enable it ** Search for recaptcha and enable it * Once complete it is '''critical''' to configure your captcha setting in the web interface (/admin/config/people/captcha) '''and do not forget to enable the captcha-points (/admin/config/people/captcha/captcha-points). a814b7402262f3938c140c9e83e1b6949d3e1881 270 269 2016-02-23T15:22:02Z Covert 18 /* Installation */ wikitext text/x-wiki ==Google's recaptcha== ===What is recaptcha and how/will it help prevent spam ?=== For answers to those questions you can look at google's page about recaptcha(https://google.com/recaptcha) ===Installation=== This installation guide requires joomla '''3.4''' (or higher). * Go to google's recaptcha administrator page(https://www.google.com/recaptcha/admin) and register your site **example of public and private key (https://i.imgur.com/vGJKEXx.png) * Navigate to the admin pannel of your joomla instalation ** Select plugins from the extentions pane in the to menu. * Search for recaptcha in the search box ** Enable recaptcha by clicking on the status icon next to recaptcha * One complete it is '''critical''' that you configure your recaptcha properly ** Go to recaptcah's configuration page by selecting recaptcha in the abovementioned pane ** '''make sure you select version 2 (default is version 1)''' ** Fill in the required keys you got on google's recaptcha administrator page * Once done joomla wil begin to require recaptcha's 00a1e24fb91e2231c1ce0687dcc1889eb6824806 271 270 2016-02-23T15:26:44Z Covert 18 /* Installation */ wikitext text/x-wiki ==Google's recaptcha== ===What is recaptcha and how/will it help prevent spam ?=== For answers to those questions you can look at google's page about recaptcha(https://google.com/recaptcha) ===Installation=== This installation guide requires joomla '''3.4''' (or higher). * Go to google's recaptcha administrator page(https://www.google.com/recaptcha/admin) and register your site **example of public and private key (https://i.imgur.com/vGJKEXx.png) * Navigate to the admin pannel of your joomla instalation ** Select plugins from the extentions pane in the top menu. * Search for recaptcha in the search box ** Enable recaptcha by clicking on the status icon next to recaptcha * One complete it is '''critical''' that you configure your recaptcha properly ** Go to recaptcah's configuration page by selecting recaptcha in the abovementioned pane ** '''make sure you select version 2 (default is version 1)''' ** Fill in the required keys you got on google's recaptcha administrator page * Once done joomla wil begin to require recaptcha's 8b1c9495aad478131b2ddc395ad1a1aa8d73da86 272 271 2016-02-23T15:29:25Z Covert 18 /* Google's recaptcha */ wikitext text/x-wiki ==Google's recaptcha== ===What is recaptcha and how does/will it help prevent spam ?=== For answers to those questions you can look at google's page about recaptcha(https://google.com/recaptcha) ===Installation=== This installation guide requires joomla '''3.4''' (or higher). * Go to google's recaptcha administrator page(https://www.google.com/recaptcha/admin) and register your site **example of public and private key (https://i.imgur.com/vGJKEXx.png) * Navigate to the admin panel of your joomla instalation ** Select plugins from the extentions panel in the top menu. * Search for recaptcha in the search box ** Enable recaptcha by clicking on the status icon next to recaptcha * One complete it is '''critical''' that you configure your recaptcha properly ** Go to recaptcha's configuration page by selecting recaptcha in the above mentioned panel ** '''make sure you select version 2 (default is version 1)''' ** Fill in the required keys you got on google's recaptcha's administrator page * Once done joomla will begin to require recaptcha's 47267fbb61872b040ee783015e7cc20c5231b81b 0 43 273 193 2016-02-29T21:36:34Z Vincenttc 21 wikitext text/x-wiki You may want to receive e-mail from ulyssis on another email provider. It is very easy to set this up. = Change the forwarders for your @ulyssis email address = # Go to ucc.ulyssis.org and log in with your username and password. # On the right side, click on '''Mail'''. # Under '''Address forward''' you can change the forward address of your ULYSSIS mail by clicking on '''edit'''. # Choose '''forward''' and enter the email address you want to forward your ULYSSIS mail to and save the changes. # If you forward it to your Gmail account, it is recommended to [[Add an alias in Gmail]] so you can send mails from your ULYSSIS accout using Gmail. = Change the forwarders for other domains = # Go to ucc.ulyssis.org and log in with your username and password. # On the right side, click on '''Mail'''. # Under '''Virtual Domains''', click on the domain you want to change. # You can change a forwarder by clicking on '''edit''' or on '''Add alias''' and add the forwarders you want. # Save your changes db8e3fcae00639b7440505cd49bf9e5f4dd6e4e0 0 5 275 159 2016-04-12T18:25:34Z Vincenttc 21 wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in the "Places" menu, choose "Connect to server." using the following options: <ul> <li>Service type: SSH</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave this blank</li> <li>Folder: your home folder as described above (this is optional, this will save you clicking to your home folder)</li> </ul> This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value (22)</li> <li>Protocol (dropdown menu): SFTP (SSH File Transfer Protocol)</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> ===Mac=== Download the free and open source program [http://cyberduck.ch/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. afc138c2c630c16faa110b7c0614e9cbb2ad7374 277 275 2016-04-12T18:37:49Z Vincenttc 21 /* Using the quickconnect bar */ wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in the "Places" menu, choose "Connect to server." using the following options: <ul> <li>Service type: SSH</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave this blank</li> <li>Folder: your home folder as described above (this is optional, this will save you clicking to your home folder)</li> </ul> This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value (22)</li> <li>Protocol (dropdown menu): SFTP (SSH File Transfer Protocol)</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> ===Mac=== Download the free and open source program [http://cyberduck.ch/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. 4d1058a473cfa3668fbe6c7324100483af63e37a 279 277 2016-04-12T18:40:30Z Vincenttc 21 /* Using the site manager */ wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in the "Places" menu, choose "Connect to server." using the following options: <ul> <li>Service type: SSH</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave this blank</li> <li>Folder: your home folder as described above (this is optional, this will save you clicking to your home folder)</li> </ul> This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value (22)</li> <li>Protocol (dropdown menu): SFTP (SSH File Transfer Protocol)</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ===Mac=== Download the free and open source program [http://cyberduck.ch/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. d9ef55493e7ce94fa2613c8b10708fd8d27bee5f 280 279 2016-04-12T18:41:46Z Vincenttc 21 /* Windows */ wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in the "Places" menu, choose "Connect to server." using the following options: <ul> <li>Service type: SSH</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave this blank</li> <li>Folder: your home folder as described above (this is optional, this will save you clicking to your home folder)</li> </ul> This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP (SSH File Transfer Protocol)</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ===Mac=== Download the free and open source program [http://cyberduck.ch/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. 062f979ece67b2cbb489a71ee1c6a1a243003641 281 280 2016-04-15T17:41:18Z Vincenttc 21 /* Using the site manager */ wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in the "Places" menu, choose "Connect to server." using the following options: <ul> <li>Service type: SSH</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave this blank</li> <li>Folder: your home folder as described above (this is optional, this will save you clicking to your home folder)</li> </ul> This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ===Mac=== Download the free and open source program [http://cyberduck.ch/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. 4eb2c6eb466b12967efddff21f679d895cdc9562 284 281 2016-04-16T09:24:03Z Vincenttc 21 /* Linux */ wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. [[File:UbuntuConnectToServer.png|left]] ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ===Mac=== Download the free and open source program [http://cyberduck.ch/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. 786a15b628d050e5ee990d2849410cfd2ee2444e 285 284 2016-04-16T09:24:15Z Vincenttc 21 /* Linux */ wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. [[File:UbuntuConnectToServer.png]] ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ===Mac=== Download the free and open source program [http://cyberduck.ch/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. 173766aabfdf1db72dae29650f22a2e95f2e0cba 286 285 2016-04-16T09:38:03Z Joachim 23 /* Mac */ wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. [[File:UbuntuConnectToServer.png]] ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ===Mac=== Currently working on an upgraded version :) Download the free and open source program [http://cyberduck.ch/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. 462eb8ba5a63a2a5b5415b17775ca22ed5be387f 287 286 2016-04-16T09:40:36Z Joachim 23 /* Mac */ wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. [[File:UbuntuConnectToServer.png]] ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ===Mac=== Currently working on an upgraded version :) Download the free and open source program [http://cyberduck.ch/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. If you want to connect again later on, you can just click the Bookmarks icon on the top left. Next you click on History. And then you can double click to re-open the connection. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. 27e378c59369399fe5e5e5c686de7c2b1e815d62 288 287 2016-04-16T14:44:11Z Vincenttc 21 /* Linux */ wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. If your distribution does not contain an option to connect to a server, you can use [https://filezilla-project.org/ FileZilla], which is completely free. See the instructions under [[Accessing_your_files#Windows|Windows]]. [[File:UbuntuConnectToServer.png]] ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ===Mac=== Currently working on an upgraded version :) Download the free and open source program [http://cyberduck.ch/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. If you want to connect again later on, you can just click the Bookmarks icon on the top left. Next you click on History. And then you can double click to re-open the connection. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. b8a78253c6d2febbbc5c4ba117d81baa04035612 290 288 2016-04-27T23:25:14Z Joachim 23 /* Mac */ wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. If your distribution does not contain an option to connect to a server, you can use [https://filezilla-project.org/ FileZilla], which is completely free. See the instructions under [[Accessing_your_files#Windows|Windows]]. [[File:UbuntuConnectToServer.png]] ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ===Mac=== Currently working on an upgraded version :) Download the free and open source program [http://cyberduck.ch/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> [[File:fullcyberduck.png|Right]] Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. If you want to connect again later on, you can just click the Bookmarks icon on the top left. Next you click on History. And then you can double click to re-open the connection. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. 74c18aadaeba0fbbcdf86f18e2520ed7aa0d7742 291 290 2016-04-27T23:25:39Z Joachim 23 /* Mac */ wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. If your distribution does not contain an option to connect to a server, you can use [https://filezilla-project.org/ FileZilla], which is completely free. See the instructions under [[Accessing_your_files#Windows|Windows]]. [[File:UbuntuConnectToServer.png]] ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ===Mac=== Currently working on an upgraded version :) Download the free and open source program [http://cyberduck.ch/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> [[File:fullcyberduck.png|200px|Right]] Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. If you want to connect again later on, you can just click the Bookmarks icon on the top left. Next you click on History. And then you can double click to re-open the connection. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. 2bad0c5ac210fba21913cf8b726b219c6adfc95a 6 58 276 2016-04-12T18:36:47Z Vincenttc 21 Voorbeeld van een ingevulde quickconnect in FileZilla wikitext text/x-wiki Voorbeeld van een ingevulde quickconnect in FileZilla 14fe0d9b165a4dc114132a01a1e8bcea85f54093 6 59 278 2016-04-12T18:39:10Z Vincenttc 21 Voorbeeld van Site Manager in FileZilla wikitext text/x-wiki Voorbeeld van Site Manager in FileZilla 7ed94a065a00d2bc468d2dc9160c4d3ca69228a8 6 60 282 2016-04-16T09:22:15Z Vincenttc 21 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 5 292 291 2016-04-27T23:26:00Z Joachim 23 /* Mac */ wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. If your distribution does not contain an option to connect to a server, you can use [https://filezilla-project.org/ FileZilla], which is completely free. See the instructions under [[Accessing_your_files#Windows|Windows]]. [[File:UbuntuConnectToServer.png]] ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ===Mac=== Download the free and open source program [http://cyberduck.ch/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> [[File:fullcyberduck.png|200px]] Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. If you want to connect again later on, you can just click the Bookmarks icon on the top left. Next you click on History. And then you can double click to re-open the connection. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. 0e537cb19e2031395b54130858cc9e24a626ac3f 294 292 2016-04-27T23:40:34Z Joachim 23 /* Mac */ wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. If your distribution does not contain an option to connect to a server, you can use [https://filezilla-project.org/ FileZilla], which is completely free. See the instructions under [[Accessing_your_files#Windows|Windows]]. [[File:UbuntuConnectToServer.png]] ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ===Mac=== Download the free and open source program [http://cyberduck.ch/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> [[File:usernamepassword2.png|200px]] Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. If you want to connect again later on, you can just click the Bookmarks icon on the top left. Next you click on History. And then you can double click to re-open the connection. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. 1dedd11ce1fab78d54f198a09b703ad0b611e541 295 294 2016-04-27T23:40:46Z Joachim 23 /* Mac */ wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. If your distribution does not contain an option to connect to a server, you can use [https://filezilla-project.org/ FileZilla], which is completely free. See the instructions under [[Accessing_your_files#Windows|Windows]]. [[File:UbuntuConnectToServer.png]] ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ===Mac=== Download the free and open source program [http://cyberduck.ch/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> [[File:usernamepassword2.png]] Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. If you want to connect again later on, you can just click the Bookmarks icon on the top left. Next you click on History. And then you can double click to re-open the connection. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. 0617b4fcdfba2cc70bdae10abab3421ee5598c63 296 295 2016-04-27T23:41:40Z Joachim 23 /* Mac */ wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. If your distribution does not contain an option to connect to a server, you can use [https://filezilla-project.org/ FileZilla], which is completely free. See the instructions under [[Accessing_your_files#Windows|Windows]]. [[File:UbuntuConnectToServer.png]] ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ===Mac=== Download the free and open source program [http://cyberduck.ch/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> [[File:usernamepassword2.png|450px]] Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. If you want to connect again later on, you can just click the Bookmarks icon on the top left. Next you click on History. And then you can double click to re-open the connection. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. a6850167a91d579dafe5162484fb1b66fc953ab1 298 296 2016-04-27T23:43:00Z Joachim 23 /* Mac */ wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. If your distribution does not contain an option to connect to a server, you can use [https://filezilla-project.org/ FileZilla], which is completely free. See the instructions under [[Accessing_your_files#Windows|Windows]]. [[File:UbuntuConnectToServer.png]] ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ===Mac=== Download the free and open source program [http://cyberduck.ch/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> [[File:usernamepassword3.png]] Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. If you want to connect again later on, you can just click the Bookmarks icon on the top left. Next you click on History. And then you can double click to re-open the connection. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. 506bb520d63278229580996562b280ab89a709d6 300 298 2016-04-27T23:48:37Z Joachim 23 /* Mac */ wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. If your distribution does not contain an option to connect to a server, you can use [https://filezilla-project.org/ FileZilla], which is completely free. See the instructions under [[Accessing_your_files#Windows|Windows]]. [[File:UbuntuConnectToServer.png]] ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ===Mac=== Download the free and open source program [http://cyberduck.ch/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> [[File:maccyberduck.png]] Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. If you want to connect again later on, you can just click the Bookmarks icon on the top left. Next you click on History. And then you can double click to re-open the connection. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. bc14d29c8fb5c077d12a0752942733db559c35b3 301 300 2016-04-27T23:49:10Z Joachim 23 /* Mac */ wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. If your distribution does not contain an option to connect to a server, you can use [https://filezilla-project.org/ FileZilla], which is completely free. See the instructions under [[Accessing_your_files#Windows|Windows]]. [[File:UbuntuConnectToServer.png]] ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ===Mac=== Download the free and open source program [http://cyberduck.ch/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> [[File:maccyberduck.png|400px]] Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. If you want to connect again later on, you can just click the Bookmarks icon on the top left. Next you click on History. And then you can double click to re-open the connection. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. 059cb3f902de7e832cf22746b202efd2f65b3f68 303 301 2016-04-27T23:50:34Z Joachim 23 /* Mac */ wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. If your distribution does not contain an option to connect to a server, you can use [https://filezilla-project.org/ FileZilla], which is completely free. See the instructions under [[Accessing_your_files#Windows|Windows]]. [[File:UbuntuConnectToServer.png]] ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ===Mac=== Download the free and open source program [http://cyberduck.ch/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> [[File:maccyberduck2.png|400px]] Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. If you want to connect again later on, you can just click the Bookmarks icon on the top left. Next you click on History. And then you can double click to re-open the connection. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. b3c731464ec6889b8f0c0f70bf41cb6d2f285e49 305 303 2016-04-27T23:51:36Z Joachim 23 /* Mac */ wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. If your distribution does not contain an option to connect to a server, you can use [https://filezilla-project.org/ FileZilla], which is completely free. See the instructions under [[Accessing_your_files#Windows|Windows]]. [[File:UbuntuConnectToServer.png]] ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ===Mac=== Download the free and open source program [http://cyberduck.ch/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> [[File:maccyberduck3.png]] Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. If you want to connect again later on, you can just click the Bookmarks icon on the top left. Next you click on History. And then you can double click to re-open the connection. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. 78c90d0937059194d9d6a96cce122dac9843e320 306 305 2016-04-27T23:52:18Z Joachim 23 /* Mac */ wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. If your distribution does not contain an option to connect to a server, you can use [https://filezilla-project.org/ FileZilla], which is completely free. See the instructions under [[Accessing_your_files#Windows|Windows]]. [[File:UbuntuConnectToServer.png]] ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ===Mac=== Download the free and open source program [http://cyberduck.ch/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> [[File:maccyberduck3.png]] Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. If you want to connect again later on, you can just click the Bookmarks icon on the top left. Next you click on History. And then you can double click to re-open the connection. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. cd28a875c2ecc2cc532282579968088684d8036c 6 67 304 2016-04-27T23:51:15Z Joachim 23 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 3 307 274 2016-05-02T12:24:54Z Covert 18 /* Security & anti-spam */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2014]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Regular updates on a CMS]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Anti-spam policies]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Add an alias in Gmail]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Development == * [[Local web development]] </div><div style="width:45%;float:left"> </div> __NOTOC__ 59bc563aecde1052bbcb2f91d9f08ae97f90c856 332 307 2016-06-12T11:35:51Z Vincenttc 21 /* Webserver */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2016]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Regular updates on a CMS]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Anti-spam policies]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Add an alias in Gmail]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Development == * [[Local web development]] </div><div style="width:45%;float:left"> </div> __NOTOC__ 5eb9e6ae042a8baff8e4d7da79e11af78e9ac0f6 354 332 2016-07-06T02:11:20Z Bert 8 /* Webserver */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2016]] * [[Temporary PHP 5.5 server]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Regular updates on a CMS]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Anti-spam policies]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Add an alias in Gmail]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Development == * [[Local web development]] </div><div style="width:45%;float:left"> </div> __NOTOC__ 3a84e5c8abce313d9fa05f523298750af9bea3f7 361 354 2016-09-18T22:30:47Z Tim 25 /* Mail */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2016]] * [[Temporary PHP 5.5 server]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Regular updates on a CMS]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Anti-spam policies]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Development == * [[Local web development]] </div><div style="width:45%;float:left"> </div> __NOTOC__ f33fa6c6e8d1eda545c0b6071227ac453a9bacf3 362 361 2016-09-18T22:32:54Z Tim 25 /* Mail */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2016]] * [[Temporary PHP 5.5 server]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Regular updates on a CMS]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Anti-spam policies]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Development == * [[Local web development]] </div><div style="width:45%;float:left"> </div> __NOTOC__ 066a1ffac039a97c78461b4a2daf4a4671e71ff3 368 362 2016-10-26T11:26:27Z Tim 25 Add LaTeX section wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2016]] * [[Temporary PHP 5.5 server]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Regular updates on a CMS]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Anti-spam policies]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Development == * [[Local web development]] </div><div style="width:45%;float:left"> == LaTeX == * [[Using the kulemt package on Windows]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 0a7a65da4a7b06883ac5ecf49fe44d8d1d7e02e4 373 368 2016-10-26T11:50:29Z Tim 25 /* LaTeX */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2016]] * [[Temporary PHP 5.5 server]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Regular updates on a CMS]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Anti-spam policies]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Development == * [[Local web development]] </div><div style="width:45%;float:left"> == LaTeX == * [[Using the kulemt package]] </div> <div style="clear:both;"></div> </div> __NOTOC__ bbe93bbf9d6c92b2306d4de42e35afb5bff51861 0 7 356 56 2016-07-06T02:30:47Z Lesderid 24 Add web IRC section wikitext text/x-wiki ULYSSIS hosts its own IRC server. (IRC stands for Internet Relay Chat, [http://en.wikipedia.org/wiki/Internet_Relay_Chat IRC on wikipedia]) ==Contact us on IRC== The public channel is simply called ulyssis, if you have a question, you can use IRC as a fast way to contact us. Details: Server: irc.ulyssis.org Channel: #ulyssis To use IRC you'll need an IRC client, we advise the terminal based [http://irssi.org/ irssi] for Linux (just use sudo apt-get install) and [http://www.mirc.com/ mIRC] for Windows, but there are a lot of other free options. ==Using our web IRC client== If you won't regularly use our IRC or if you just want to check it out, you can use our web IRC client instead. You can find it at [https://webirc.ulyssis.org/ webirc.ulyssis.org]. ==Using irssi in a Screen== Our IRC server isn't very crowded and as you only see messages when you're connected, we advise you to run irssi in a screen. Members can run a screen on our shellservers, as they keep running 24/7 you can use them to keep track of your conversations. ===Connect to the shellserver=== Use the ssh command in the linux or mac terminal or PuTTY to connect on windows. Extensive information on how to do so can be found on [[Accessing shell servers over SSH]]. ===Start irssi in a screen=== *When on the shellserver, enter <code>screen</code> to start a screen. *Enter <code>irssi</code> to start irssi in that screen. *Connect to the IRC server: <code>/server irc.ulyssis.org</code> *Connect to the public channel: <code>/join #ulyssis</code> ===Screen usage=== *To exit the screen: press Ctrl-A and press D ('detach') to return to the shellserver. *To reconnect: enter <code>screen -r</code> or <code>screen -DR</code> (the latter will create a new screen if it wasn't already made). *Help I can't connect to my screen! **Check if you are on the right shellserver and didn't make a typing error. **If everything is correct, your screen may have been stopped by a crash of our shellserver. You can check the [http://www.ulyssis.org/status status] section of our website for more information about possible downtimes. 3d460d6f992088877907c9d19392e7a23fa57f18 357 356 2016-07-06T03:01:03Z Lesderid 24 Add tmux information wikitext text/x-wiki ULYSSIS hosts its own IRC server. (IRC stands for Internet Relay Chat, [http://en.wikipedia.org/wiki/Internet_Relay_Chat IRC on wikipedia]) ==Contact us on IRC== The public channel is simply called ulyssis, if you have a question, you can use IRC as a fast way to contact us. Details: Server: irc.ulyssis.org Channel: #ulyssis To use IRC you'll need an IRC client, we advise the terminal based [http://irssi.org/ irssi] for Linux (just use sudo apt-get install) and [http://www.mirc.com/ mIRC] for Windows, but there are a lot of other free options. ==Using our web IRC client== If you won't regularly use our IRC or if you just want to check it out, you can use our web IRC client instead. You can find it at [https://webirc.ulyssis.org/ webirc.ulyssis.org]. ==Using irssi in a Screen== Our IRC server isn't very crowded and as you only see messages when you're connected, we advise you to run irssi in either a screen or a tmux session. Members can run screen or tmux on our shellservers, as they keep running 24/7 you can use them to keep track of your conversations. Screen and tmux are similar programs. Screen has been around for longer and is more tested, while tmux is more modern with new features and being easier to use for beginners. ===Connect to the shellserver=== Use the ssh command in the linux or mac terminal or PuTTY to connect on windows. Extensive information on how to do so can be found on [[Accessing shell servers over SSH]]. ===Start irssi in a screen=== *When on the shellserver, enter <code>screen</code> to start a screen session, or <code>tmux</code> to start a tmux session. *Enter <code>irssi</code> to start irssi. *Connect to the IRC server: <code>/server irc.ulyssis.org</code> *Connect to the public channel: <code>/join #ulyssis</code> ===Screen usage=== *To exit the screen: press Ctrl-A and press D ('detach') to return to the shellserver. *To reconnect: enter <code>screen -r</code> or <code>screen -DR</code> (the latter will create a new screen if it wasn't already made). ===Tmux usage=== *To exit the tmux session: press Ctrl-B and press D ('detach') to return to the shellserver. *To reconnect: enter <code>tmux attach</code> ===Help, I can't reconnect to my session!=== *Check if you are on the right shellserver and didn't make a typing error. *If everything is correct, your screen may have been stopped by a crash of our shellserver. You can check the [http://www.ulyssis.org/status status] section of our website for more information about possible downtimes. *Make sure you use the right program (<code>screen</code> if you started a screen session and <code>tmux</code> if you started a tmux session) a96d68fd10fc5b5e44a957a25eb85ef2532b3db9 358 357 2016-07-06T03:01:31Z Lesderid 24 wikitext text/x-wiki ULYSSIS hosts its own IRC server. (IRC stands for Internet Relay Chat, [http://en.wikipedia.org/wiki/Internet_Relay_Chat IRC on wikipedia]) ==Contact us on IRC== The public channel is simply called ulyssis, if you have a question, you can use IRC as a fast way to contact us. Details: Server: irc.ulyssis.org Channel: #ulyssis To use IRC you'll need an IRC client, we advise the terminal based [http://irssi.org/ irssi] for Linux (just use sudo apt-get install) and [http://www.mirc.com/ mIRC] for Windows, but there are a lot of other free options. ==Using our web IRC client== If you won't regularly use our IRC or if you just want to check it out, you can use our web IRC client instead. You can find it at [https://webirc.ulyssis.org/ webirc.ulyssis.org]. ==Using irssi in a Screen== Our IRC server isn't very crowded and as you only see messages when you're connected, we advise you to run irssi in either a screen or a tmux session. Members can run screen or tmux on our shellservers, as they keep running 24/7 you can use them to keep track of your conversations. Screen and tmux are similar programs. Screen has been around for longer and is more tested, while tmux is more modern with new features and being easier to use for beginners. ===Connect to the shellserver=== Use the ssh command in your Linux or OS X terminal, or use PuTTY to connect on windows. Extensive information on how to do so can be found on [[Accessing shell servers over SSH]]. ===Start irssi in a screen=== *When on the shellserver, enter <code>screen</code> to start a screen session, or <code>tmux</code> to start a tmux session. *Enter <code>irssi</code> to start irssi. *Connect to the IRC server: <code>/server irc.ulyssis.org</code> *Connect to the public channel: <code>/join #ulyssis</code> ===Screen usage=== *To exit the screen: press Ctrl-A and press D ('detach') to return to the shellserver. *To reconnect: enter <code>screen -r</code> or <code>screen -DR</code> (the latter will create a new screen if it wasn't already made). ===Tmux usage=== *To exit the tmux session: press Ctrl-B and press D ('detach') to return to the shellserver. *To reconnect: enter <code>tmux attach</code> ===Help, I can't reconnect to my session!=== *Check if you are on the right shellserver and didn't make a typing error. *If everything is correct, your screen may have been stopped by a crash of our shellserver. You can check the [http://www.ulyssis.org/status status] section of our website for more information about possible downtimes. *Make sure you use the right program (<code>screen</code> if you started a screen session and <code>tmux</code> if you started a tmux session) 7e404533f7918ebcb918d3a6d5b6d69eff934741 359 358 2016-07-06T03:02:44Z Lesderid 24 wikitext text/x-wiki ULYSSIS hosts its own IRC server. (IRC stands for Internet Relay Chat, [http://en.wikipedia.org/wiki/Internet_Relay_Chat IRC on wikipedia]) ==Contact us on IRC== The public channel is simply called ulyssis, if you have a question, you can use IRC as a fast way to contact us. Details: Server: irc.ulyssis.org Channel: #ulyssis To use IRC you'll need an IRC client, we advise the terminal based [http://irssi.org/ irssi] for Linux (just use sudo apt-get install) and [http://www.mirc.com/ mIRC] for Windows, but there are a lot of other free options. ==Using our web IRC client== If you won't regularly use our IRC or if you just want to check it out, you can use our web IRC client instead. You can find it at [https://webirc.ulyssis.org/ webirc.ulyssis.org]. ==Using irssi in a screen or tmux session== Our IRC server isn't very crowded and as you only see messages when you're connected, we advise you to run irssi in either a screen or a tmux session. Members can run screen or tmux on our shellservers, as they keep running 24/7 you can use them to keep track of your conversations. Screen and tmux are similar programs. Screen has been around for longer and is more tested, while tmux is more modern with new features and being easier to use for beginners. ===Connect to the shellserver=== Use the ssh command in your Linux or OS X terminal, or use PuTTY to connect on windows. Extensive information on how to do so can be found on [[Accessing shell servers over SSH]]. ===Start irssi in a screen=== *When on the shellserver, enter <code>screen</code> to start a screen session, or <code>tmux</code> to start a tmux session. *Enter <code>irssi</code> to start irssi. *Connect to the IRC server: <code>/server irc.ulyssis.org</code> *Connect to the public channel: <code>/join #ulyssis</code> ===Screen usage=== *To exit the screen: press Ctrl-A and press D ('detach') to return to the shellserver. *To reconnect: enter <code>screen -r</code> or <code>screen -DR</code> (the latter will create a new screen if it wasn't already made). ===Tmux usage=== *To exit the tmux session: press Ctrl-B and press D ('detach') to return to the shellserver. *To reconnect: enter <code>tmux attach</code> ===Help, I can't reconnect to my session!=== *Check if you are on the right shellserver and didn't make a typing error. *If everything is correct, your screen may have been stopped by a crash of our shellserver. You can check the [http://www.ulyssis.org/status status] section of our website for more information about possible downtimes. *Make sure you use the right program (<code>screen</code> if you started a screen session and <code>tmux</code> if you started a tmux session) 40522960b48e10f65015a8a9cdb30434d5a7d7b1 0 8 360 66 2016-07-25T13:59:54Z Bert 8 wikitext text/x-wiki PHP errors are not displayed by default. If an error occurs, you will simply get a blank page. This is for security reasons: this way, an attacker doesn't know about possible vulnerabilities of your website. If you want to see PHP errors, you can log them to a file, or enable the display of errors. = Logging errors to a file = If your username is ''foobar'', create a <code>.htaccess</code> file (for example: <code>~/www/.htaccess</code>) with this content, if you are a regular user: php_flag log_errors on php_value error_log /home/user/foobar/php_error.log Or if you are an organization: php_flag log_errors on php_value error_log /home/org/foobar/php_error.log = Displaying errors = Create a <code>.htaccess</code> file (for example: <code>~/www/.htaccess</code>) with this content: php_flag display_errors on 2e38d9ad147494e394d82d72335047f495a1f489 0 72 363 2016-09-18T23:06:39Z Tim 25 Created page with "You may want to send e-mail from Hotmail using your @ulyssis.org address, or another domain name that you use for your account. Hotmail allows you to do this by configuring a ..." wikitext text/x-wiki You may want to send e-mail from Hotmail using your @ulyssis.org address, or another domain name that you use for your account. Hotmail allows you to do this by configuring a few settings. Because you should only be able to send mails from an e-mail address you actually own, make sure that you configured receiving mails before starting this process. Hotmail will send a confirmation mail to the provided e-mail address to confirm that you own it. Note that Outlook's SMTP will still add your original address as "Sender" in the mail headers. Depending on the recipient's mail client, he might still see this. If you use a local mail client, you might be able to avoid this by using a custom SMTP server. #Click on the gear icon at the top right and³ choose "Connected accounts" (Dutch: "Verbonden accounts") #At the bottom you see the title "" (Dutch: "E-mailaliassen") with a link "" (Dutch: "Primaire alias beheren of kiezen") below. Click it. You will have to log in again to proceed. #Click on "" (Dutch: "E-mailadres toevoegen") and choose the second option: "" (Dutch: "Een bestaand e-mailadres als een Microsoft-accountalias toevoegen"). Fill in the e-mail address you want to use to send mail from, and click "" (Dutch: "Alias toevoegen") #At this point, you should receive an e-mail on the address you just provided. It will contain a URL to confirm adding the alias. Click it. #At this point, you have confirmed that you are the owner of the e-mail address. Congratulations, you can now use it to send mail! 7a4572ec14e385cbdee6ab211630a1a19d81b9bb 364 363 2016-09-18T23:09:04Z Tim 25 wikitext text/x-wiki You may want to send e-mail from Hotmail using your @ulyssis.org address, or another domain name that you use for your account. Hotmail allows you to do this by configuring a few settings. Because you should only be able to send mails from an e-mail address you actually own, make sure that you configured receiving mails before starting this process. Hotmail will send a confirmation mail to the provided e-mail address to confirm that you own it. Note that Outlook's SMTP will still add your original address as "Sender" in the mail headers. Depending on the recipient's mail client, he might still see this. If you use a local mail client, you might be able to avoid this by using a custom SMTP server. #Click on the gear icon at the top right and choose "Connected accounts" (Dutch: "Verbonden accounts") #At the bottom you see the title "Email aliases" (Dutch: "E-mailaliassen") with a link "Manage or choose a primary alias" (Dutch: "Primaire alias beheren of kiezen") below. Click it. You will have to log in again to proceed. #Click on "Add Email" (Dutch: "E-mailadres toevoegen") and choose the second option: "Add an existing email address as a Microsoft account alias" (Dutch: "Een bestaand e-mailadres als een Microsoft-accountalias toevoegen"). Fill in the e-mail address you want to use to send mail from, and click "Add alias" (Dutch: "Alias toevoegen") #At this point, you should receive an e-mail on the address you just provided. It will contain a URL to confirm adding the alias. Click it. #At this point, you have confirmed that you are the owner of the e-mail address. Congratulations, you can now use it to send mail! 472afd0233a40ee2fd0e6187ca37613911bb4a09 365 364 2016-09-18T23:21:32Z Tim 25 wikitext text/x-wiki You may want to send e-mail from Hotmail using your @ulyssis.org address, or another domain name that you use for your account. Hotmail allows you to do this by configuring a few settings. Because you should only be able to send mails from an e-mail address you actually own, make sure that you configured receiving mails before starting this process. Hotmail will send a confirmation mail to the provided e-mail address to confirm that you own it. Note that Outlook's SMTP will still add your original address as "Sender" in the mail headers. Depending on the recipient's mail client, he might still see this. If you use a local mail client, you might be able to avoid this by using a custom SMTP server. #Click on the gear icon at the top right and choose '''Connected accounts''' (Dutch: '''Verbonden accounts''') #At the bottom you see the title '''Email aliases''' (Dutch: '''E-mailaliassen''') with a link '''Manage or choose a primary alias''' (Dutch: '''Primaire alias beheren of kiezen''') below. Click it. You will have to log in again to proceed. #Click on '''Add Email''' (Dutch: '''E-mailadres toevoegen''') and choose the second option: '''Add an existing email address as a Microsoft account alias''' (Dutch: '''Een bestaand e-mailadres als een Microsoft-accountalias toevoegen'''). Fill in the e-mail address you want to use to send mail from, and click '''Add alias''' (Dutch: '''Alias toevoegen''') #At this point, you should receive an e-mail on the address you just provided. It will contain a URL to confirm adding the alias. Click it. #At this point, you have confirmed that you are the owner of the e-mail address. Congratulations, you can now use it to send mail! df8505958fc2d0ec211d52d01bf407d115ebcd14 0 37 366 268 2016-10-19T23:10:07Z Lars 26 /* FastCGI */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</pre> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than were it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> Or, for Python 3: <pre>virtualenv ~/.venv --python=python3</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [http://flask.pocoo.org/docs/0.10/deploying/fastcgi/ Flask documentation for FastCGI] 101d62c12d9c11e318cf4bf0e6cbcbdd648cba34 367 366 2016-10-19T23:10:26Z Lars 26 /* FastCGI */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</pre> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than were it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> Or, for Python 3: <pre>virtualenv ~/.venv --python=python3</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [http://flask.pocoo.org/docs/0.10/deploying/fastcgi/ Flask documentation for FastCGI] 4d0284c113acf1fc0c00013334afef1c91492cda 0 73 369 2016-10-26T11:31:53Z Tim 25 Created page with "We often get the question at our LaTeX workshop on how to properly install the kulemt package on Windows. For this reason, we have decided to provide a proper guideline. You c..." wikitext text/x-wiki We often get the question at our LaTeX workshop on how to properly install the kulemt package on Windows. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading kulemt-tds.zip from ftp://ftp.esat.kuleuven.be/latex/kulemt/. == One-time use == Most people will only use this package once, for their master thesis. The easiest way is to unzip the downloaded file and go to the directory tex/latex/kulemt. Here, copy the files kulemt{.cfg,.cls,x.sty} and logokul{,eng}.eps to the same directory as your LaTeX file. == System-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package system-wide. When using TeXLive, as we recommend, this involves a bit more work and use of a command-line. Open the Windows command-line by searching for "cmd" in your start menu. The app has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf From the extracted kulemt-tds.zip, copy the entire directory tex to the location given in the previous step. It is possible this folder needs to be created first. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English (in case of a Dutch master)}, udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> 742a89cf9773eaf7a6d734de5c8fe70709c89dc9 370 369 2016-10-26T11:42:34Z Tim 25 wikitext text/x-wiki We often get the question at our LaTeX workshop on how to properly install the kulemt package on Windows. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading "kulemt-tds.zip" from ftp://ftp.esat.kuleuven.be/latex/kulemt/. == One-time use == Most people will only use this package once, for their master thesis. The easiest way is to unzip the downloaded file and go to the directory "tex/latex/kulemt". Here, copy the files kulemt{.cfg,.cls,x.sty} and logokul{,eng}.eps to the same directory as your LaTeX file. == System-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package system-wide. When using TeXLive, as we recommend, this involves a bit more work and use of a command-line. Open the Windows command-line by searching for "cmd" in your start menu. The app has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf From the extracted kulemt-tds.zip, copy the entire directory "tex" to the location given in the previous step. It is possible this folder needs to be created first. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English (in case of a Dutch master)}, udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> 0de75010816fcfceb81b87334164a4844ef1d851 371 370 2016-10-26T11:50:12Z Tim 25 Tim moved page [[Using the kulemt package on Windows]] to [[Using the kulemt package]] wikitext text/x-wiki We often get the question at our LaTeX workshop on how to properly install the kulemt package on Windows. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading "kulemt-tds.zip" from ftp://ftp.esat.kuleuven.be/latex/kulemt/. == One-time use == Most people will only use this package once, for their master thesis. The easiest way is to unzip the downloaded file and go to the directory "tex/latex/kulemt". Here, copy the files kulemt{.cfg,.cls,x.sty} and logokul{,eng}.eps to the same directory as your LaTeX file. == System-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package system-wide. When using TeXLive, as we recommend, this involves a bit more work and use of a command-line. Open the Windows command-line by searching for "cmd" in your start menu. The app has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf From the extracted kulemt-tds.zip, copy the entire directory "tex" to the location given in the previous step. It is possible this folder needs to be created first. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English (in case of a Dutch master)}, udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> 0de75010816fcfceb81b87334164a4844ef1d851 374 371 2016-10-26T11:57:18Z Tim 25 wikitext text/x-wiki We often get the question at our LaTeX workshop on how to properly install the kulemt package. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading "kulemt-tds.zip" from ftp://ftp.esat.kuleuven.be/latex/kulemt/. == One-time use == Most people will only use this package once, for their master thesis. The easiest way is to unzip the downloaded file and go to the directory "tex/latex/kulemt". Here, copy the files kulemt{.cfg,.cls,x.sty} and logokul{,eng}.eps to the same directory as your LaTeX file. == System-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package system-wide. When using TeXLive, as we recommend, this involves a bit more work and use of a command-line. === Windows === Open the Windows command-line by searching for "cmd" in your start menu. The app has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf From the extracted kulemt-tds.zip, copy the entire directory "tex" to the location given in the previous step. It is possible this folder needs to be created first. === UNIX-like OSes === You can follow the general guidelines provided by the department: ftp://ftp.esat.kuleuven.be/latex/kulemt/README. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English (in case of a Dutch master)}, udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> 7ac51faee34568acaac6d658529dbea95cb460d0 375 374 2016-10-26T13:34:09Z Tim 25 /* Windows */ wikitext text/x-wiki We often get the question at our LaTeX workshop on how to properly install the kulemt package. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading "kulemt-tds.zip" from ftp://ftp.esat.kuleuven.be/latex/kulemt/. == One-time use == Most people will only use this package once, for their master thesis. The easiest way is to unzip the downloaded file and go to the directory "tex/latex/kulemt". Here, copy the files kulemt{.cfg,.cls,x.sty} and logokul{,eng}.eps to the same directory as your LaTeX file. == System-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package system-wide. When using TeXLive, as we recommend, this involves a bit more work and use of a command-line. === Windows === First, you should find where to install the packages for your user. By default, this will be in the folder "texmf" in your %USERPROFILE% (C:\Users\YourUsername). It is possible that this folder needs to be created first. From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location (note: the directory itself, not its contents). In case this does not work, this folder might be different for you for some reason. It is possible to retrieve the correct location through the Windows command-line. Open the Windows command-line by searching for "cmd" in your start menu. The app has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf From the extracted kulemt-tds.zip, copy the entire directory "tex" to the location given in the previous step. It is possible this folder needs to be created first. === UNIX-like OSes === You can follow the general guidelines provided by the department: ftp://ftp.esat.kuleuven.be/latex/kulemt/README. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English (in case of a Dutch master)}, udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> 1543cec98a14e3da58c175cc8be7ca9f8f738abb 376 375 2016-10-26T13:36:00Z Tim 25 /* Windows */ wikitext text/x-wiki We often get the question at our LaTeX workshop on how to properly install the kulemt package. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading "kulemt-tds.zip" from ftp://ftp.esat.kuleuven.be/latex/kulemt/. == One-time use == Most people will only use this package once, for their master thesis. The easiest way is to unzip the downloaded file and go to the directory "tex/latex/kulemt". Here, copy the files kulemt{.cfg,.cls,x.sty} and logokul{,eng}.eps to the same directory as your LaTeX file. == System-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package system-wide. When using TeXLive, as we recommend, this involves a bit more work and use of a command-line. === Windows === First, you should find where to install the packages for your user. By default, this will be in the folder "texmf" in your %USERPROFILE% (C:\Users\YourUsername). It is possible that this folder needs to be created first. From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location (note: the directory itself, not its contents). In case this does not work, this folder might be different for you for some reason. It is possible to retrieve the correct location through the Windows command-line. Open the Windows command-line by searching for "cmd" in your start menu. The app has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf If you have found this folder, copy the entire "tex" directory from the extracted kulemt-tds.zip to this location, as stated before. Create the folder if needed. === UNIX-like OSes === You can follow the general guidelines provided by the department: ftp://ftp.esat.kuleuven.be/latex/kulemt/README. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English (in case of a Dutch master)}, udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> 899ed017bedef80b2f213ce0d2af77b41693bdc7 377 376 2016-10-26T13:44:44Z Tim 25 wikitext text/x-wiki We often get the question at our LaTeX workshop on how to properly install the kulemt package. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading "kulemt-tds.zip" from ftp://ftp.esat.kuleuven.be/latex/kulemt/. == One-time use == Most people will only use this package once, for their master thesis. The easiest way is to unzip the downloaded file and go to the directory "tex/latex/kulemt". Here, copy the files kulemt{.cfg,.cls,x.sty} and logokul{,eng}.eps to the same directory as your LaTeX file. == User-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package in a central place for your user. When using TeXLive, as we recommend, this involves a bit more work and use of a command-line. === Windows === First, you should find where to install the packages for your user. By default, this will be in the folder "texmf" in your %USERPROFILE% (C:\Users\YourUsername). From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location. It is possible that this folder needs to be created first. In case this does not work, this folder might be different for you for some reason. It is possible to retrieve the correct location through the Windows command-line. Open the Windows command-line by searching for "cmd" in your start menu. The app has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf If you have found this folder, copy the entire "tex" directory from the extracted kulemt-tds.zip to this location, as stated before. Create the folder if needed. === UNIX-like OSes === On UNIX-like OSes, such as Linux or macOS, the steps are similar to Windows. First, find your TEXMFHOME. This is the folder in which you can install LaTeX packages for your user. By default, this is "~/texmf". You can check this with the following command: kpsewhich -expand-var='$TEXMFHOME' An example output would be: /home/ulyssis/texmf Copy the entire "tex" directory (the folder itself, not its contents) from the extracted kulemt-tds.zip to this directory. It is possible that you need to create this folder first. For a more detailed overview, you can follow the general guidelines provided by the department: ftp://ftp.esat.kuleuven.be/latex/kulemt/README. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English (in case of a Dutch master)}, udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> 420035fdc58bd8d620dae07329939110bf723d2f 378 377 2016-10-26T13:46:59Z Tim 25 wikitext text/x-wiki We often get the question at our LaTeX workshop on how to properly install the kulemt package. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading "kulemt-tds.zip" from ftp://ftp.esat.kuleuven.be/latex/kulemt/. == One-time use == Most people will only use this package once, for their master thesis. The easiest way is to unzip the downloaded file and go to the directory "tex/latex/kulemt". Here, copy the files kulemt{.cfg,.cls,x.sty} and logokul{,eng}.eps to the same directory as your LaTeX file. == User-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package in a central place for your user. When using TeXLive, as we recommend, this involves a bit more work and use of a command-line. === Windows === First, you should find where to install the packages for your user. By default, this will be in the folder "texmf" in your %USERPROFILE% (C:\Users\YourUsername). From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location (note: the directory itself, not its contents). It is possible that this folder needs to be created first. In case this does not work, this folder might be different for you for some reason. It is possible to retrieve the correct location through the Windows command-line. Open the Windows command-line by searching for "cmd" in your start menu. The app has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf If you have found this folder, copy the entire "tex" directory from the extracted kulemt-tds.zip to this location, as stated before. Create the folder if needed. === UNIX-like OSes === On UNIX-like OSes, such as Linux or macOS, the steps are similar to Windows. First, find your TEXMFHOME. This is the folder in which you can install LaTeX packages for your user. By default, this is "~/texmf". You can check this with the following command: kpsewhich -expand-var='$TEXMFHOME' An example output would be: /home/ulyssis/texmf Copy the entire "tex" directory (the folder itself, not its contents) from the extracted kulemt-tds.zip to this directory. It is possible that you need to create this folder first. For a more detailed overview, you can follow the general guidelines provided by the department: ftp://ftp.esat.kuleuven.be/latex/kulemt/README. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English (in case of a Dutch master)}, udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> 5373c065446f86c1067d0bc353ea175158fa5b56 379 378 2016-10-26T13:52:43Z Tim 25 /* UNIX-like OSes */ wikitext text/x-wiki We often get the question at our LaTeX workshop on how to properly install the kulemt package. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading "kulemt-tds.zip" from ftp://ftp.esat.kuleuven.be/latex/kulemt/. == One-time use == Most people will only use this package once, for their master thesis. The easiest way is to unzip the downloaded file and go to the directory "tex/latex/kulemt". Here, copy the files kulemt{.cfg,.cls,x.sty} and logokul{,eng}.eps to the same directory as your LaTeX file. == User-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package in a central place for your user. When using TeXLive, as we recommend, this involves a bit more work and use of a command-line. === Windows === First, you should find where to install the packages for your user. By default, this will be in the folder "texmf" in your %USERPROFILE% (C:\Users\YourUsername). From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location (note: the directory itself, not its contents). It is possible that this folder needs to be created first. In case this does not work, this folder might be different for you for some reason. It is possible to retrieve the correct location through the Windows command-line. Open the Windows command-line by searching for "cmd" in your start menu. The app has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf If you have found this folder, copy the entire "tex" directory from the extracted kulemt-tds.zip to this location, as stated before. Create the folder if needed. === UNIX-like OSes === On UNIX-like OSes, such as Linux or macOS, the steps are similar to Windows. First, find your TEXMFHOME. This is the folder in which you can install LaTeX packages for your user. By default, this is "~/texmf". You can check this with the following command: kpsewhich -var-value=TEXMFHOME An example output would be: /home/ulyssis/texmf Copy the entire "tex" directory (the folder itself, not its contents) from the extracted kulemt-tds.zip to this directory. It is possible that you need to create this folder first. For a more detailed overview, you can follow the general guidelines provided by the department: ftp://ftp.esat.kuleuven.be/latex/kulemt/README. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English (in case of a Dutch master)}, udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> 13692d64469334e57874cce9bae1adade100a5df 380 379 2016-10-26T14:47:16Z Tim 25 wikitext text/x-wiki We often get the question at our LaTeX workshop how to properly install the kulemt package. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading "kulemt-tds.zip" from ftp://ftp.esat.kuleuven.be/latex/kulemt/. == One-time use == Most people will only use this package once, for their master thesis. In this case, you can just put the necessary files in the same folder as your LaTeX project. The easiest way to accomplish this, is to unzip the downloaded file and in the unzipped folder, navigate to the directory "tex/latex/kulemt". Here, copy the following files to the same directory as your LaTeX project: kulemt.cfg, kulemt.cls, kulemtx.sty, logokul.eps and logokuleng.eps. == User-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package in a central location where LaTeX can find it autonomously. When using TeXLive, as we recommend, this involves a bit more work. === Windows === First, you should find where to install the packages for your user. This is called the TEXMFHOME. By default, this will be in the folder "texmf" in your %USERPROFILE% (C:\Users\YourUsername). It is possible that this folder needs to %be created first. From the extracted kulemt-tds.zip, copy the entire directory %"tex" to this location (note: the directory itself, not only its contents). If this does not work, or if you want to check first, please refer to the "Finding the TEXMFHOME" section of this document. === UNIX-like OSes === On UNIX-like OSes, such as Linux or macOS, the steps are similar to Windows. First, find your TEXMFHOME. This is the folder in which you can install LaTeX packages for your user. By default, this is "~/texmf". If this does not work, or if you want to check first, please refer to the "Finding the TEXMFHOME" section of this document. For a more detailed overview, you can follow the general guidelines provided by the department: ftp://ftp.esat.kuleuven.be/latex/kulemt/README. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English (in case of a Dutch master)}, udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> == Finding the TEXMFHOME == In case the default location for the TEXMFHOME as stated above does not work, you can find the correct directory through command-line. In Linux and macOS, look for an app called "Terminal". In Windows, search for "cmd" using the start menu. The program has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf If you have found this folder, copy the entire "tex" directory from the extracted kulemt-tds.zip to this location, as stated before. Create the folder if needed. 18e497014cf429b96c8b234a57fb9dc9b7d8ef26 381 380 2016-10-26T14:53:22Z Tim 25 /* Windows */ wikitext text/x-wiki We often get the question at our LaTeX workshop how to properly install the kulemt package. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading "kulemt-tds.zip" from ftp://ftp.esat.kuleuven.be/latex/kulemt/. == One-time use == Most people will only use this package once, for their master thesis. In this case, you can just put the necessary files in the same folder as your LaTeX project. The easiest way to accomplish this, is to unzip the downloaded file and in the unzipped folder, navigate to the directory "tex/latex/kulemt". Here, copy the following files to the same directory as your LaTeX project: kulemt.cfg, kulemt.cls, kulemtx.sty, logokul.eps and logokuleng.eps. == User-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package in a central location where LaTeX can find it autonomously. When using TeXLive, as we recommend, this involves a bit more work. === Windows === First, you should find where to install the packages for your user. This is called the TEXMFHOME. By default, this will be in the folder "texmf" in your %USERPROFILE% (C:\Users\YourUsername). It is possible that this folder needs to be created first. From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location (note: the directory itself, not only its contents). If this does not work, or if you want to check first, please refer to the "Finding the TEXMFHOME" section of this document. === UNIX-like OSes === On UNIX-like OSes, such as Linux or macOS, the steps are similar to Windows. First, find your TEXMFHOME. This is the folder in which you can install LaTeX packages for your user. By default, this is "~/texmf". If this does not work, or if you want to check first, please refer to the "Finding the TEXMFHOME" section of this document. For a more detailed overview, you can follow the general guidelines provided by the department: ftp://ftp.esat.kuleuven.be/latex/kulemt/README. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English (in case of a Dutch master)}, udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> == Finding the TEXMFHOME == In case the default location for the TEXMFHOME as stated above does not work, you can find the correct directory through command-line. In Linux and macOS, look for an app called "Terminal". In Windows, search for "cmd" using the start menu. The program has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf If you have found this folder, copy the entire "tex" directory from the extracted kulemt-tds.zip to this location, as stated before. Create the folder if needed. 4f6d87c9abcd5a8b1e683b6a1122777b4fd236ab 382 381 2016-10-26T14:56:29Z Tim 25 /* UNIX-like OSes */ wikitext text/x-wiki We often get the question at our LaTeX workshop how to properly install the kulemt package. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading "kulemt-tds.zip" from ftp://ftp.esat.kuleuven.be/latex/kulemt/. == One-time use == Most people will only use this package once, for their master thesis. In this case, you can just put the necessary files in the same folder as your LaTeX project. The easiest way to accomplish this, is to unzip the downloaded file and in the unzipped folder, navigate to the directory "tex/latex/kulemt". Here, copy the following files to the same directory as your LaTeX project: kulemt.cfg, kulemt.cls, kulemtx.sty, logokul.eps and logokuleng.eps. == User-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package in a central location where LaTeX can find it autonomously. When using TeXLive, as we recommend, this involves a bit more work. === Windows === First, you should find where to install the packages for your user. This is called the TEXMFHOME. By default, this will be in the folder "texmf" in your %USERPROFILE% (C:\Users\YourUsername). It is possible that this folder needs to be created first. From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location (note: the directory itself, not only its contents). If this does not work, or if you want to check first, please refer to the "Finding the TEXMFHOME" section of this document. === UNIX-like OSes === On UNIX-like OSes, such as Linux or macOS, the steps are similar to Windows. First, find your TEXMFHOME. This is the folder in which you can install LaTeX packages for your user. By default, this is "~/texmf". From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location (note: the directory itself, not its contents). It is possible that this folder needs to be created first. If this does not work, or if you want to check first, please refer to the "Finding the TEXMFHOME" section of this document. For a more detailed overview, you can follow the general guidelines provided by the department: ftp://ftp.esat.kuleuven.be/latex/kulemt/README. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English (in case of a Dutch master)}, udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> == Finding the TEXMFHOME == In case the default location for the TEXMFHOME as stated above does not work, you can find the correct directory through command-line. In Linux and macOS, look for an app called "Terminal". In Windows, search for "cmd" using the start menu. The program has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf If you have found this folder, copy the entire "tex" directory from the extracted kulemt-tds.zip to this location, as stated before. Create the folder if needed. 408cfcfdc3ddb09293b390a84f1fb9784866a65c 383 382 2016-10-26T14:56:40Z Tim 25 /* UNIX-like OSes */ wikitext text/x-wiki We often get the question at our LaTeX workshop how to properly install the kulemt package. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading "kulemt-tds.zip" from ftp://ftp.esat.kuleuven.be/latex/kulemt/. == One-time use == Most people will only use this package once, for their master thesis. In this case, you can just put the necessary files in the same folder as your LaTeX project. The easiest way to accomplish this, is to unzip the downloaded file and in the unzipped folder, navigate to the directory "tex/latex/kulemt". Here, copy the following files to the same directory as your LaTeX project: kulemt.cfg, kulemt.cls, kulemtx.sty, logokul.eps and logokuleng.eps. == User-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package in a central location where LaTeX can find it autonomously. When using TeXLive, as we recommend, this involves a bit more work. === Windows === First, you should find where to install the packages for your user. This is called the TEXMFHOME. By default, this will be in the folder "texmf" in your %USERPROFILE% (C:\Users\YourUsername). It is possible that this folder needs to be created first. From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location (note: the directory itself, not only its contents). If this does not work, or if you want to check first, please refer to the "Finding the TEXMFHOME" section of this document. === UNIX-like OSes === On UNIX-like OSes, such as Linux or macOS, the steps are similar to Windows. First, find your TEXMFHOME. This is the folder in which you can install LaTeX packages for your user. By default, this is "~/texmf". From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location (note: the directory itself, not its contents). It is possible that this folder needs to be created first. If this does not work, or if you want to check first, please refer to the "Finding the TEXMFHOME" section of this document. For a more detailed overview, you can follow the general guidelines provided by the department: ftp://ftp.esat.kuleuven.be/latex/kulemt/README. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English (in case of a Dutch master)}, udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> == Finding the TEXMFHOME == In case the default location for the TEXMFHOME as stated above does not work, you can find the correct directory through command-line. In Linux and macOS, look for an app called "Terminal". In Windows, search for "cmd" using the start menu. The program has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf If you have found this folder, copy the entire "tex" directory from the extracted kulemt-tds.zip to this location, as stated before. Create the folder if needed. c0e4727087877d7d22b4e0d0cec8033a3ad81c17 384 383 2016-10-26T15:16:57Z Tim 25 /* UNIX-like OSes */ wikitext text/x-wiki We often get the question at our LaTeX workshop how to properly install the kulemt package. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading "kulemt-tds.zip" from ftp://ftp.esat.kuleuven.be/latex/kulemt/. == One-time use == Most people will only use this package once, for their master thesis. In this case, you can just put the necessary files in the same folder as your LaTeX project. The easiest way to accomplish this, is to unzip the downloaded file and in the unzipped folder, navigate to the directory "tex/latex/kulemt". Here, copy the following files to the same directory as your LaTeX project: kulemt.cfg, kulemt.cls, kulemtx.sty, logokul.eps and logokuleng.eps. == User-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package in a central location where LaTeX can find it autonomously. When using TeXLive, as we recommend, this involves a bit more work. === Windows === First, you should find where to install the packages for your user. This is called the TEXMFHOME. By default, this will be in the folder "texmf" in your %USERPROFILE% (C:\Users\YourUsername). It is possible that this folder needs to be created first. From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location (note: the directory itself, not only its contents). If this does not work, or if you want to check first, please refer to the "Finding the TEXMFHOME" section of this document. === Linux === On Linux, the steps are similar to Windows. First, find your TEXMFHOME. This is the folder in which you can install LaTeX packages for your user. By default, this is "~/texmf". From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location (note: the directory itself, not its contents). It is possible that this folder needs to be created first. If this does not work, or if you want to check first, please refer to the "Finding the TEXMFHOME" section of this document. For a more detailed overview, you can follow the general guidelines provided by the department: ftp://ftp.esat.kuleuven.be/latex/kulemt/README. === OS X/macOS === On OS X/macOS, the steps are similar to the previous two OSes. First, find your TEXMFHOME. This is the folder in which you can install LaTeX packages for your user. By default, this is "~/Library/texmf". From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location (note: the directory itself, not its contents). It is possible that this folder needs to be created first. If this does not work, or if you want to check first, please refer to the "Finding the TEXMFHOME" section of this document. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English (in case of a Dutch master)}, udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> == Finding the TEXMFHOME == In case the default location for the TEXMFHOME as stated above does not work, you can find the correct directory through command-line. In Linux and macOS, look for an app called "Terminal". In Windows, search for "cmd" using the start menu. The program has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf If you have found this folder, copy the entire "tex" directory from the extracted kulemt-tds.zip to this location, as stated before. Create the folder if needed. 75bd3214125cf2f2c90718acd1c4a198547f90bb 385 384 2016-10-26T15:19:46Z Tim 25 Undo revision 384 by [[Special:Contributions/Tim|Tim]] ([[User talk:Tim|talk]]) wikitext text/x-wiki We often get the question at our LaTeX workshop how to properly install the kulemt package. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading "kulemt-tds.zip" from ftp://ftp.esat.kuleuven.be/latex/kulemt/. == One-time use == Most people will only use this package once, for their master thesis. In this case, you can just put the necessary files in the same folder as your LaTeX project. The easiest way to accomplish this, is to unzip the downloaded file and in the unzipped folder, navigate to the directory "tex/latex/kulemt". Here, copy the following files to the same directory as your LaTeX project: kulemt.cfg, kulemt.cls, kulemtx.sty, logokul.eps and logokuleng.eps. == User-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package in a central location where LaTeX can find it autonomously. When using TeXLive, as we recommend, this involves a bit more work. === Windows === First, you should find where to install the packages for your user. This is called the TEXMFHOME. By default, this will be in the folder "texmf" in your %USERPROFILE% (C:\Users\YourUsername). It is possible that this folder needs to be created first. From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location (note: the directory itself, not only its contents). If this does not work, or if you want to check first, please refer to the "Finding the TEXMFHOME" section of this document. === UNIX-like OSes === On UNIX-like OSes, such as Linux or macOS, the steps are similar to Windows. First, find your TEXMFHOME. This is the folder in which you can install LaTeX packages for your user. By default, this is "~/texmf". From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location (note: the directory itself, not its contents). It is possible that this folder needs to be created first. If this does not work, or if you want to check first, please refer to the "Finding the TEXMFHOME" section of this document. For a more detailed overview, you can follow the general guidelines provided by the department: ftp://ftp.esat.kuleuven.be/latex/kulemt/README. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English (in case of a Dutch master)}, udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> == Finding the TEXMFHOME == In case the default location for the TEXMFHOME as stated above does not work, you can find the correct directory through command-line. In Linux and macOS, look for an app called "Terminal". In Windows, search for "cmd" using the start menu. The program has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf If you have found this folder, copy the entire "tex" directory from the extracted kulemt-tds.zip to this location, as stated before. Create the folder if needed. c0e4727087877d7d22b4e0d0cec8033a3ad81c17 386 385 2016-10-27T22:49:12Z Tim 25 /* User-wide installation */ wikitext text/x-wiki We often get the question at our LaTeX workshop how to properly install the kulemt package. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading "kulemt-tds.zip" from ftp://ftp.esat.kuleuven.be/latex/kulemt/. == One-time use == Most people will only use this package once, for their master thesis. In this case, you can just put the necessary files in the same folder as your LaTeX project. The easiest way to accomplish this, is to unzip the downloaded file and in the unzipped folder, navigate to the directory "tex/latex/kulemt". Here, copy the following files to the same directory as your LaTeX project: kulemt.cfg, kulemt.cls, kulemtx.sty, logokul.eps and logokuleng.eps. == User-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package in a central location where LaTeX can find it autonomously. When using TeXLive, as we recommend, this involves a bit more work. First, you should find where to install the packages for your user. This is called the TEXMFHOME. The default location of this folder is: * For Windows, this is the folder "texmf" in your %USERPROFILE% (C:\Users\YourUsername). * For Linux, this is "~/texmf" * For OS X/macOS, this is "~/Library/texmf" It is possible that this folder needs to be created first. From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location (note: the directory itself, not only its contents). If this does not work, or if you want to check the directory first, please refer to the section [[#Finding the TEXMFHOME]] at the bottom of this document. For a more detailed overview, you can follow the general guidelines provided by the department: ftp://ftp.esat.kuleuven.be/latex/kulemt/README. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English (in case of a Dutch master)}, udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> == Finding the TEXMFHOME == In case the default location for the TEXMFHOME as stated above does not work, you can find the correct directory through command-line. In Linux and macOS, look for an app called "Terminal". In Windows, search for "cmd" using the start menu. The program has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf If you have found this folder, copy the entire "tex" directory from the extracted kulemt-tds.zip to this location, as stated before. Create the folder if needed. 42ab8d7717aa21d96f672dde17ac10cc1cc7ee9b 387 386 2016-10-27T22:52:00Z Tim 25 /* User-wide installation */ wikitext text/x-wiki We often get the question at our LaTeX workshop how to properly install the kulemt package. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading "kulemt-tds.zip" from ftp://ftp.esat.kuleuven.be/latex/kulemt/. == One-time use == Most people will only use this package once, for their master thesis. In this case, you can just put the necessary files in the same folder as your LaTeX project. The easiest way to accomplish this, is to unzip the downloaded file and in the unzipped folder, navigate to the directory "tex/latex/kulemt". Here, copy the following files to the same directory as your LaTeX project: kulemt.cfg, kulemt.cls, kulemtx.sty, logokul.eps and logokuleng.eps. == User-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package in a central location where LaTeX can find it autonomously. When using TeXLive, as we recommend, this involves a bit more work. First, you should find where to install the packages for your user. This is called the TEXMFHOME. The default location of this folder is: * For Windows, this is the folder "texmf" in your %USERPROFILE% (C:\Users\YourUsername for Windows Vista and up). * For Linux, this is "~/texmf" * For OS X/macOS, this is "~/Library/texmf" It is possible that this folder needs to be created first. From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location (note: the directory itself, not only its contents). If this does not work, or if you want to check the directory first, please refer to the section [[#Finding the TEXMFHOME]] at the bottom of this document. For a more detailed overview, you can follow the general guidelines provided by the department: ftp://ftp.esat.kuleuven.be/latex/kulemt/README. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English (in case of a Dutch master)}, udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> == Finding the TEXMFHOME == In case the default location for the TEXMFHOME as stated above does not work, you can find the correct directory through command-line. In Linux and macOS, look for an app called "Terminal". In Windows, search for "cmd" using the start menu. The program has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf If you have found this folder, copy the entire "tex" directory from the extracted kulemt-tds.zip to this location, as stated before. Create the folder if needed. c5d174b7860ea3a5a2dc4f0cc459888507190b9d 388 387 2016-10-27T22:52:27Z Tim 25 /* User-wide installation */ wikitext text/x-wiki We often get the question at our LaTeX workshop how to properly install the kulemt package. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading "kulemt-tds.zip" from ftp://ftp.esat.kuleuven.be/latex/kulemt/. == One-time use == Most people will only use this package once, for their master thesis. In this case, you can just put the necessary files in the same folder as your LaTeX project. The easiest way to accomplish this, is to unzip the downloaded file and in the unzipped folder, navigate to the directory "tex/latex/kulemt". Here, copy the following files to the same directory as your LaTeX project: kulemt.cfg, kulemt.cls, kulemtx.sty, logokul.eps and logokuleng.eps. == User-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package in a central location where LaTeX can find it autonomously. When using TeXLive, as we recommend, this involves a bit more work. First, you should find where to install the packages for your user. This is called the TEXMFHOME. The default location of this folder is: * For Windows, this is the folder "texmf" in your %USERPROFILE% (C:\Users\YourUsername for Windows Vista and up). * For Linux, this is "~/texmf" * For OS X/macOS, this is "~/Library/texmf" It is possible that this folder needs to be created first. From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location (note: the directory itself, not only its contents). If this does not work, or if you want to check the directory first, please refer to the section [[#Finding the TEXMFHOME]] at the bottom of this document. For a more detailed overview, you can follow the general guidelines provided by the department: ftp://ftp.esat.kuleuven.be/latex/kulemt/README. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English (in case of a Dutch master)}, udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> == Finding the TEXMFHOME == In case the default location for the TEXMFHOME as stated above does not work, you can find the correct directory through command-line. In Linux and macOS, look for an app called "Terminal". In Windows, search for "cmd" using the start menu. The program has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf If you have found this folder, copy the entire "tex" directory from the extracted kulemt-tds.zip to this location, as stated before. Create the folder if needed. d85ae15310bbd2cda936686d23681b18e1b1d43c 389 388 2016-10-27T22:56:10Z Tim 25 /* User-wide installation */ wikitext text/x-wiki We often get the question at our LaTeX workshop how to properly install the kulemt package. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading "kulemt-tds.zip" from ftp://ftp.esat.kuleuven.be/latex/kulemt/. == One-time use == Most people will only use this package once, for their master thesis. In this case, you can just put the necessary files in the same folder as your LaTeX project. The easiest way to accomplish this, is to unzip the downloaded file and in the unzipped folder, navigate to the directory "tex/latex/kulemt". Here, copy the following files to the same directory as your LaTeX project: kulemt.cfg, kulemt.cls, kulemtx.sty, logokul.eps and logokuleng.eps. == User-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package in a central location where LaTeX can find it autonomously. When using TeXLive, as we recommend, this involves a bit more work. First, you should find where to install the packages for your user. This is called the TEXMFHOME. The default location of this folder is: * For Windows, this is the folder "texmf" in your %USERPROFILE% (C:\Users\YourUsername for Windows Vista and up). * For Linux, this is "~/texmf" * For OS X/macOS, this is "~/Library/texmf" It is possible that this folder needs to be created first. From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location (note: the directory itself, not only its contents). If this does not work, or if you want to check the directory first, please refer to the section [[#Finding the TEXMFHOME]] at the bottom of this document. For a more technical overview, you can follow the general guidelines provided by the department: ftp://ftp.esat.kuleuven.be/latex/kulemt/README. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English (in case of a Dutch master)}, udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> == Finding the TEXMFHOME == In case the default location for the TEXMFHOME as stated above does not work, you can find the correct directory through command-line. In Linux and macOS, look for an app called "Terminal". In Windows, search for "cmd" using the start menu. The program has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf If you have found this folder, copy the entire "tex" directory from the extracted kulemt-tds.zip to this location, as stated before. Create the folder if needed. 380301cbae712c646d6c5bbdd5c1c660615ef2bf 390 389 2016-10-28T10:01:27Z Tim 25 /* Using the kulemt package */ wikitext text/x-wiki We often get the question at our LaTeX workshop how to properly install the kulemt package. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading "kulemt-tds.zip" from ftp://ftp.esat.kuleuven.be/latex/kulemt/. == One-time use == Most people will only use this package once, for their master thesis. In this case, you can just put the necessary files in the same folder as your LaTeX project. The easiest way to accomplish this, is to unzip the downloaded file and in the unzipped folder, navigate to the directory "tex/latex/kulemt". Here, copy the following files to the same directory as your LaTeX project: kulemt.cfg, kulemt.cls, kulemtx.sty, logokul.eps and logokuleng.eps. == User-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package in a central location where LaTeX can find it autonomously. When using TeXLive, as we recommend, this involves a bit more work. First, you should find where to install the packages for your user. This is called the TEXMFHOME. The default location of this folder is: * For Windows, this is the folder "texmf" in your %USERPROFILE% (C:\Users\YourUsername for Windows Vista and up). * For Linux, this is "~/texmf" * For OS X/macOS, this is "~/Library/texmf" It is possible that this folder needs to be created first. From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location (note: the directory itself, not only its contents). If this does not work, or if you want to check the directory first, please refer to the section [[#Finding the TEXMFHOME]] at the bottom of this document. For a more technical overview, you can follow the general guidelines provided by the department: ftp://ftp.esat.kuleuven.be/latex/kulemt/README. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English}, % in case of a Dutch master udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> == Finding the TEXMFHOME == In case the default location for the TEXMFHOME as stated above does not work, you can find the correct directory through command-line. In Linux and macOS, look for an app called "Terminal". In Windows, search for "cmd" using the start menu. The program has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf If you have found this folder, copy the entire "tex" directory from the extracted kulemt-tds.zip to this location, as stated before. Create the folder if needed. af78686b3fc7a92523b159fdaf20a47ee31123d9 0 74 372 2016-10-26T11:50:12Z Tim 25 Tim moved page [[Using the kulemt package on Windows]] to [[Using the kulemt package]] wikitext text/x-wiki #REDIRECT [[Using the kulemt package]] ce06386145ae6c8154e7b5b0b22e1995976d4ab2 6 75 391 2016-11-06T16:59:52Z Tim 25 KU Leuven SMTPS settings for Thunderbird wikitext text/x-wiki KU Leuven SMTPS settings for Thunderbird 1b391a1b30c768f885b2d2e2564324442116210e 6 75 392 391 2016-11-06T17:03:05Z Tim 25 Tim uploaded a new version of &quot;[[File:Thunderbird-SMTPS.png]]&quot; wikitext text/x-wiki KU Leuven SMTPS settings for Thunderbird 1b391a1b30c768f885b2d2e2564324442116210e 6 76 393 2016-11-06T17:12:08Z Tim 25 Custom identity settings for Thunderbird wikitext text/x-wiki Custom identity settings for Thunderbird 8627e95877e0d33ef9c377c44c81647cbbcee077 0 43 394 273 2016-11-07T13:49:19Z Vincenttc 21 wikitext text/x-wiki You may want to receive e-mail from ulyssis on another email provider. It is very easy to set this up. = Change the forwarders for your @ulyssis email address = # Go to ucc.ulyssis.org and log in with your username and password. # On the right side, click on '''Mail'''. # Under '''Address forward''' you can change the forward address of your ULYSSIS mail by clicking on '''edit'''. # Choose '''forward''' and enter the email address you want to forward your ULYSSIS mail to and save the changes. # If you forward it to your Gmail account, it is recommended to [[Add an alias in Gmail]] so you can send mails from your ULYSSIS accout using Gmail. = Change the forwarders for other domains = # Go to ucc.ulyssis.org and log in with your username and password. # On the right side, click on '''Mail'''. # Under '''Virtual Domains''', click on the domain you want to change. # You can change a forwarder by clicking on '''edit''' or on '''Add alias''' and add the forwarders you want. # Save your changes = Use your mailbox and forwarders at the same time = An alternative way to set the forwarders, that will also allow you to use your mailbox and the webinterface, is to use a .forward file. On each line of this file, you can specify to wich addresses you want to forward the email. If one of the addresses is the same as your @ulyssis address, then the mail will also be placed in your ULYSSIS mailbox. In the following example, your @ulyssis email address is <code>user@ulyssis.org</code>. Example .forward file: user@ulyssis.org example@gmail.com example2@skynet.be This will place the email in your ULYSSIS mailbox so that you can access it from the webinterface or your local mailclient. It will also forward the mail to <code>example@gmail.com</code> and <code>example2@skynet.be</code>. To use this, place a .forward file with the prefered in your homedir, see [[Accessing your files]], and set your forwarder to 'Inbox' in https://ucc.ulyssis.org/mail 0e9e5884a868e77b2cce7395d30b18ad1d995c0e 396 394 2016-11-07T17:25:38Z Marnik 28 wikitext text/x-wiki You may want to receive e-mail from ulyssis on another email provider. It is very easy to set this up. = Change the forwarders for your @ulyssis email address = # Go to ucc.ulyssis.org and log in with your username and password. # On the right side, click on '''Mail'''. # Under '''Address forward''' you can change the forward address of your ULYSSIS mail by clicking on '''edit'''. # Choose '''forward''' and enter the email address you want to forward your ULYSSIS mail to and save the changes. # If you forward it to your Gmail account, it is recommended to [[Add an alias in Gmail]] so you can send mails from your ULYSSIS accout using Gmail. = Change the forwarders for other domains = # Go to ucc.ulyssis.org and log in with your username and password. # On the right side, click on '''Mail'''. # Under '''Virtual Domains''', click on the domain you want to change. # You can change a forwarder by clicking on '''edit''' or on '''Add alias''' and add the forwarders you want. # Save your changes = Use your mailbox and forwarders at the same time = An alternative way to set the forwarders, that will also allow you to use your mailbox and the webinterface, is to use a .forward file. On each line of this file, you can specify to wich addresses you want to forward the email. If one of the addresses is the same as your @ulyssis address, then the mail will also be placed in your ULYSSIS mailbox. In the following example, your @ulyssis email address is <code>user@ulyssis.org</code>. Example .forward file: user@ulyssis.org example@gmail.com example2@skynet.be This will place the email in your ULYSSIS mailbox so that you can access it from the webinterface or your local mailclient. It will also forward the mail to <code>example@gmail.com</code> and <code>example2@skynet.be</code>. To use this, place a .forward file with the prefered email addresses in your homedir, see [[Accessing your files]], and set your forwarder to 'Inbox' in https://ucc.ulyssis.org/mail cc8c68a8631419683ab093f67027e45981c47883 0 77 395 2016-11-07T13:57:38Z Tim 25 Created page with "You may want to send e-mail from Thunderbird using your @ulyssis.org-address, or another domain name that you use for your account. Thunderbird allows you to do this, but to c..." wikitext text/x-wiki You may want to send e-mail from Thunderbird using your @ulyssis.org-address, or another domain name that you use for your account. Thunderbird allows you to do this, but to configure this properly, you should not use your provider's SMTP server. They will add an extra header stating the original e-mail address the e-mail is sent from. Some e-mail clients show this information, which might be unwanted. The KU Leuven also provides an SMTP server which you can use as a student. It accepts e-mail originating from any e-mail adress, and can therefore be used for this purpose. It should be noted that this is an '''authenticated''' server, so any potential abuse can be tracked back to you. You should '''not''' use this for any malicious purpose. == Adding the KU Leuven SMTP server in Thunderbird == If you already have set up your KU Leuven e-mail in Thunderbird, you can skip this step and proceed to [[#Configure an identity for your e-mail account]] below. Go to your '''Account Settings''' (Edit > Account Settings or Tools > Account Settings, depending on your operating system). At the bottom of the left sidebar, you will find an entry named '''Outgoing Server (SMTP)'''. Click this to access your SMTP settings. In your SMTP settings, you should see a list of existing SMTP servers. We want to add a new entry, so click the '''Add...''' button. In the screen that pops up, fill in the settings as in the example screenshot below. Replace the displayed user name with your own student number. You will have to fill in the corresponding password on first use. [[File:Thunderbird-SMTPS.png]] == Configure an identity for your e-mail account == Back in the '''Account Settings''' screen, click on your e-mail address (not on any of its children). In the screen that opens, there will be a button '''Manage Identities...''' at the bottom. Click it. In the new screen, there will be one existing identity already: the default identity corresponding with your normal e-mail address. We want to add a new identity, so click the '''Add...''' button. In the screen that pops up, fill the name and e-mail address you wish to use. At the bottom, make sure you choose the SMTP server of your student account. This is shown in the image below. [[File:Thunderbird-Identity.png]] == Sending your first e-mail == When you compose a new e-mail, you can change the sender in the "From" field to the identity you just configured. If everything was installed correctly, Thunderbird will show you a pop-up to enter your KU Leuven password when you try to send the e-mail. In this pop-up, you can choose to save this password for later use. d5a9e1a499c17a34008f10a805417cd797cb1c00 403 395 2016-11-11T16:08:28Z Vincenttc 21 Vincenttc moved page [[Sending e-mail from an alias in Thunderbird]] to [[Add an alias in Thunderbird]] wikitext text/x-wiki You may want to send e-mail from Thunderbird using your @ulyssis.org-address, or another domain name that you use for your account. Thunderbird allows you to do this, but to configure this properly, you should not use your provider's SMTP server. They will add an extra header stating the original e-mail address the e-mail is sent from. Some e-mail clients show this information, which might be unwanted. The KU Leuven also provides an SMTP server which you can use as a student. It accepts e-mail originating from any e-mail adress, and can therefore be used for this purpose. It should be noted that this is an '''authenticated''' server, so any potential abuse can be tracked back to you. You should '''not''' use this for any malicious purpose. == Adding the KU Leuven SMTP server in Thunderbird == If you already have set up your KU Leuven e-mail in Thunderbird, you can skip this step and proceed to [[#Configure an identity for your e-mail account]] below. Go to your '''Account Settings''' (Edit > Account Settings or Tools > Account Settings, depending on your operating system). At the bottom of the left sidebar, you will find an entry named '''Outgoing Server (SMTP)'''. Click this to access your SMTP settings. In your SMTP settings, you should see a list of existing SMTP servers. We want to add a new entry, so click the '''Add...''' button. In the screen that pops up, fill in the settings as in the example screenshot below. Replace the displayed user name with your own student number. You will have to fill in the corresponding password on first use. [[File:Thunderbird-SMTPS.png]] == Configure an identity for your e-mail account == Back in the '''Account Settings''' screen, click on your e-mail address (not on any of its children). In the screen that opens, there will be a button '''Manage Identities...''' at the bottom. Click it. In the new screen, there will be one existing identity already: the default identity corresponding with your normal e-mail address. We want to add a new identity, so click the '''Add...''' button. In the screen that pops up, fill the name and e-mail address you wish to use. At the bottom, make sure you choose the SMTP server of your student account. This is shown in the image below. [[File:Thunderbird-Identity.png]] == Sending your first e-mail == When you compose a new e-mail, you can change the sender in the "From" field to the identity you just configured. If everything was installed correctly, Thunderbird will show you a pop-up to enter your KU Leuven password when you try to send the e-mail. In this pop-up, you can choose to save this password for later use. d5a9e1a499c17a34008f10a805417cd797cb1c00 0 78 397 2016-11-08T14:14:01Z Lars 26 Created page with "While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. # Set up agenda sync as describ..." wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. # Set up agenda sync as described in the [https://icts.kuleuven.be/docs/at/cm/ep/s/uurrooster/agenda ICTS manual]. You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.kuleuven.be (Note: there is no ''student'' in there) and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (Agenda) # On the top right (below the menu bar), click the '''Share''' (Delen) button. A side-panel appears. # Enter a non-KU Leuven email address in the '''Share with''' (Delen met) textfield # Make sure '''Full details''' (?) is selected in the dropdown next to your email address # Click the '''Send''' (?) button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> a255bc602fa49ed5cefbbb059f2e121a5decb3b4 398 397 2016-11-08T15:18:44Z Lars 26 wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. # Set up agenda sync as described in the [https://icts.kuleuven.be/docs/at/cm/ep/s/uurrooster/agenda ICTS manual]. You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (Agenda) # On the top right (below the menu bar), click the '''Share''' (Delen) button. A side-panel appears. # Enter a non-KU Leuven email address in the '''Share with''' (Delen met) textfield # Make sure '''Full details''' (?) is selected in the dropdown next to your email address # Click the '''Send''' (?) button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> 5c709fc81013b9464b3d2eb5bba5875bdd687efb 399 398 2016-11-08T15:25:20Z Tim 25 wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. # Set up agenda sync as described in the [https://icts.kuleuven.be/docs/at/cm/ep/s/uurrooster/agenda ICTS manual]. You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (Agenda) # On the top right (below the menu bar), click the '''Share''' (Delen) button. A side-panel appears. # Enter a non-KU Leuven email address in the '''Share with''' (Delen met) textfield # Make sure '''Full details''' (Volledige informatie) is selected in the dropdown next to your email address # Click the '''Send''' (Verzenden) button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> 32ae8eaa7812b62a6c14520831fd3e28739b1729 400 399 2016-11-08T15:27:27Z Lars 26 wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. # Set up agenda sync as described in the [https://icts.kuleuven.be/docs/at/cm/ep/s/uurrooster/agenda ICTS manual]. You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (Agenda) # On the top right (below the menu bar), click the '''Share''' (Delen) button. A side-panel appears. # Enter a non-KU Leuven email address in the '''Share with''' (Delen met) textfield. After filling the email address, press the enter key. # Make sure '''Full details''' (Volledige informatie) is selected in the dropdown next to your email address # Click the '''Send''' (Verzenden) button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> f9bab3fafa2a27059b4118fb911ac98f7346f730 413 400 2016-12-19T10:56:59Z Lars 26 wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. # Set up agenda sync on KU Loket ## Visit [https://kuloket.be/ KU Loket] ## Go to the '''Education & Students''' (Onderwijs & studenten) tab ## Click '''Agenda sync''' ## Click '''Configure agenda''' (Agenda instellen) ## Change the switch '''Show schedule in my agenda''' (Toon uurrooster in mijn agenda) to '''On'''. You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (Agenda) # On the top right (below the menu bar), click the '''Share''' (Delen) button. A side-panel appears. # Enter a non-KU Leuven email address in the '''Share with''' (Delen met) textfield. After filling the email address, press the enter key. # Make sure '''Full details''' (Volledige informatie) is selected in the dropdown next to your email address # Click the '''Send''' (Verzenden) button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> 3aa6a9457b90598afc90fbefd8c71683cd10236f 417 413 2016-12-19T11:19:06Z Lars 26 wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. # Set up agenda sync on KU Loket ## Visit [https://kuloket.be/ KU Loket] ## Go to the '''Education & Students''' (Onderwijs & studenten) tab [[File:KULoket-Agenda-Step1.png|thumb|200px]] ## Click '''Agenda sync''' ## Click '''Configure agenda''' (Agenda instellen) [[File:KULoket-Agenda-Step2.png|thumb|200px]] ## Change the switch '''Show schedule in my agenda''' (Toon uurrooster in mijn agenda) to '''On'''. [[File:KULoket-Agenda-Step3.png|thumb|200px]] You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (Agenda) # On the top right (below the menu bar), click the '''Share''' (Delen) button. A side-panel appears. # Enter a non-KU Leuven email address in the '''Share with''' (Delen met) textfield. After filling the email address, press the enter key. # Make sure '''Full details''' (Volledige informatie) is selected in the dropdown next to your email address # Click the '''Send''' (Verzenden) button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> 90a60348a3f64fdbde4786b0e0fb799576975ced 0 73 401 390 2016-11-08T15:57:11Z Dmrs 29 wikitext text/x-wiki We often get the question at our LaTeX workshop how to properly install the kulemt package. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading "kulemt-tds.zip" from ftp://ftp.esat.kuleuven.be/latex/kulemt/. == One-time use == Most people will only use this package once, for their master thesis. In this case, you can just put the necessary files in the same folder as your LaTeX project. The easiest way to accomplish this, is to unzip the downloaded file and in the unzipped folder, navigate to the directory "tex/latex/kulemt". Here, copy the following files to the same directory as your LaTeX project: kulemt.cfg, kulemt.cls, kulemtx.sty, logokul.eps and logokuleng.eps. == User-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package in a central location where LaTeX can find it autonomously. When using TeXLive, as we recommend, this involves a bit more work. First, you should find where to install the packages for your user. This is called the TEXMFHOME. The default location of this folder is: * For Windows, this is the folder "texmf" in your %USERPROFILE% (C:\Users\YourUsername for Windows Vista and up). * For Linux, this is "~/texmf" * For OS X/macOS, this is "~/Library/texmf" It is possible that this folder needs to be created first. From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location (note: the directory itself, not only its contents). If this does not work, or if you want to check the directory first, please refer to the section [[#Finding the TEXMFHOME]] at the bottom of this document. For a more technical overview, you can follow the general guidelines provided by the department: ftp://ftp.esat.kuleuven.be/latex/kulemt/README. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English}, % in case of a Dutch master udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> == Finding the TEXMFHOME == In case the default location for the TEXMFHOME as stated above does not work, you can find the correct directory through command-line. In Linux and macOS, look for an app called "Terminal". In Windows, search for "cmd" using the start menu. The program has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf If you have found this folder, copy the entire "tex" directory from the extracted kulemt-tds.zip to this location, as stated before. Create the folder if needed. == Troubleshooting == The kulemt package requires the memoir package. Make sure you have this package by installing the 2016 version of TeXLive. The version of TeXLive that you can find pre-installed on many Linux distro's is not the 2016 version of TeXLive. You can upgrade to the latest version of TeXLive by running the following commands in a terminal. <nowiki> sudo add-apt-repository ppa:jonathonf/texlive-2016 sudo apt-get update sudo apt-get install texlive </nowiki> a13acb3c54ab6f972d3f99de97ade4cfda496175 420 401 2017-01-24T18:01:43Z Tim 25 /* Troubleshooting */ wikitext text/x-wiki We often get the question at our LaTeX workshop how to properly install the kulemt package. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading "kulemt-tds.zip" from ftp://ftp.esat.kuleuven.be/latex/kulemt/. == One-time use == Most people will only use this package once, for their master thesis. In this case, you can just put the necessary files in the same folder as your LaTeX project. The easiest way to accomplish this, is to unzip the downloaded file and in the unzipped folder, navigate to the directory "tex/latex/kulemt". Here, copy the following files to the same directory as your LaTeX project: kulemt.cfg, kulemt.cls, kulemtx.sty, logokul.eps and logokuleng.eps. == User-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package in a central location where LaTeX can find it autonomously. When using TeXLive, as we recommend, this involves a bit more work. First, you should find where to install the packages for your user. This is called the TEXMFHOME. The default location of this folder is: * For Windows, this is the folder "texmf" in your %USERPROFILE% (C:\Users\YourUsername for Windows Vista and up). * For Linux, this is "~/texmf" * For OS X/macOS, this is "~/Library/texmf" It is possible that this folder needs to be created first. From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location (note: the directory itself, not only its contents). If this does not work, or if you want to check the directory first, please refer to the section [[#Finding the TEXMFHOME]] at the bottom of this document. For a more technical overview, you can follow the general guidelines provided by the department: ftp://ftp.esat.kuleuven.be/latex/kulemt/README. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English}, % in case of a Dutch master udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> == Finding the TEXMFHOME == In case the default location for the TEXMFHOME as stated above does not work, you can find the correct directory through command-line. In Linux and macOS, look for an app called "Terminal". In Windows, search for "cmd" using the start menu. The program has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf If you have found this folder, copy the entire "tex" directory from the extracted kulemt-tds.zip to this location, as stated before. Create the folder if needed. == Troubleshooting == The kulemt package requires the memoir package. Make sure you have this package. We recommend installing the latex-full package on Ubuntu. When you use our installer for Windows or OS X/macOS, you will automatically have the entire LaTeX suite. 0634905c8cf7601f574796d17f4cc1815bb853e5 421 420 2017-01-24T18:03:30Z Tim 25 /* Troubleshooting */ wikitext text/x-wiki We often get the question at our LaTeX workshop how to properly install the kulemt package. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading "kulemt-tds.zip" from ftp://ftp.esat.kuleuven.be/latex/kulemt/. == One-time use == Most people will only use this package once, for their master thesis. In this case, you can just put the necessary files in the same folder as your LaTeX project. The easiest way to accomplish this, is to unzip the downloaded file and in the unzipped folder, navigate to the directory "tex/latex/kulemt". Here, copy the following files to the same directory as your LaTeX project: kulemt.cfg, kulemt.cls, kulemtx.sty, logokul.eps and logokuleng.eps. == User-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package in a central location where LaTeX can find it autonomously. When using TeXLive, as we recommend, this involves a bit more work. First, you should find where to install the packages for your user. This is called the TEXMFHOME. The default location of this folder is: * For Windows, this is the folder "texmf" in your %USERPROFILE% (C:\Users\YourUsername for Windows Vista and up). * For Linux, this is "~/texmf" * For OS X/macOS, this is "~/Library/texmf" It is possible that this folder needs to be created first. From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location (note: the directory itself, not only its contents). If this does not work, or if you want to check the directory first, please refer to the section [[#Finding the TEXMFHOME]] at the bottom of this document. For a more technical overview, you can follow the general guidelines provided by the department: ftp://ftp.esat.kuleuven.be/latex/kulemt/README. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English}, % in case of a Dutch master udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> == Finding the TEXMFHOME == In case the default location for the TEXMFHOME as stated above does not work, you can find the correct directory through command-line. In Linux and macOS, look for an app called "Terminal". In Windows, search for "cmd" using the start menu. The program has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf If you have found this folder, copy the entire "tex" directory from the extracted kulemt-tds.zip to this location, as stated before. Create the folder if needed. == Troubleshooting == The kulemt package requires the memoir package. Make sure you have this package. We recommend installing the texlive-full package on Ubuntu. When you use our installer for Windows or OS X/macOS, you will automatically have the entire LaTeX suite. 8252896dfe914f8a4da61e37a3cb4b0374907429 447 421 2017-03-01T11:35:49Z Tim 25 /* Troubleshooting */ wikitext text/x-wiki We often get the question at our LaTeX workshop how to properly install the kulemt package. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading "kulemt-tds.zip" from ftp://ftp.esat.kuleuven.be/latex/kulemt/. == One-time use == Most people will only use this package once, for their master thesis. In this case, you can just put the necessary files in the same folder as your LaTeX project. The easiest way to accomplish this, is to unzip the downloaded file and in the unzipped folder, navigate to the directory "tex/latex/kulemt". Here, copy the following files to the same directory as your LaTeX project: kulemt.cfg, kulemt.cls, kulemtx.sty, logokul.eps and logokuleng.eps. == User-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package in a central location where LaTeX can find it autonomously. When using TeXLive, as we recommend, this involves a bit more work. First, you should find where to install the packages for your user. This is called the TEXMFHOME. The default location of this folder is: * For Windows, this is the folder "texmf" in your %USERPROFILE% (C:\Users\YourUsername for Windows Vista and up). * For Linux, this is "~/texmf" * For OS X/macOS, this is "~/Library/texmf" It is possible that this folder needs to be created first. From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location (note: the directory itself, not only its contents). If this does not work, or if you want to check the directory first, please refer to the section [[#Finding the TEXMFHOME]] at the bottom of this document. For a more technical overview, you can follow the general guidelines provided by the department: ftp://ftp.esat.kuleuven.be/latex/kulemt/README. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English}, % in case of a Dutch master udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> == Finding the TEXMFHOME == In case the default location for the TEXMFHOME as stated above does not work, you can find the correct directory through command-line. In Linux and macOS, look for an app called "Terminal". In Windows, search for "cmd" using the start menu. The program has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf If you have found this folder, copy the entire "tex" directory from the extracted kulemt-tds.zip to this location, as stated before. Create the folder if needed. == Troubleshooting == The kulemt package requires the memoir package. Make sure you have this package. We recommend installing the texlive-full package on Ubuntu. When you use the installer from [ftp://ftp.ulyssis.org/LaTeX-Workshop/installers/ our FTP server] for Windows or OS X/macOS, you will automatically have the entire LaTeX suite. 5005728544aed9805ccbf299272990bf4be349cf 0 3 402 373 2016-11-08T23:24:40Z Tim 25 /* Mail */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2016]] * [[Temporary PHP 5.5 server]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Regular updates on a CMS]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Anti-spam policies]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Fetch your KU Leuven email into another email address]] * [[Sending e-mail from an alias in Thunderbird]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Development == * [[Local web development]] </div><div style="width:45%;float:left"> == LaTeX == * [[Using the kulemt package]] </div> <div style="clear:both;"></div> </div> __NOTOC__ ccef0a3bc6b8ed91725791b5a9292685c0a8605c 412 402 2016-11-12T03:21:14Z Vincenttc 21 /* Mail */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2016]] * [[Temporary PHP 5.5 server]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Regular updates on a CMS]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Anti-spam policies]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Development == * [[Local web development]] </div><div style="width:45%;float:left"> == LaTeX == * [[Using the kulemt package]] </div> <div style="clear:both;"></div> </div> __NOTOC__ c1f24e6dc83e613fb6488f3d17a569e38fae8e5f 425 412 2017-02-01T21:41:48Z Andreas 20 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2016]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Regular updates on a CMS]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Anti-spam policies]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Development == * [[Local web development]] </div><div style="width:45%;float:left"> == LaTeX == * [[Using the kulemt package]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 5825561c636a4fba02908a445f36be6e469cd0f0 446 425 2017-02-27T23:53:23Z Yoa 30 /* Shell */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2016]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Regular updates on a CMS]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Anti-spam policies]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Development == * [[Local web development]] </div><div style="width:45%;float:left"> == LaTeX == * [[Using the kulemt package]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 1ddfe9746440bb21fadc254ff76d2b4ff169e296 0 79 404 2016-11-11T16:08:28Z Vincenttc 21 Vincenttc moved page [[Sending e-mail from an alias in Thunderbird]] to [[Add an alias in Thunderbird]] wikitext text/x-wiki #REDIRECT [[Add an alias in Thunderbird]] d4346fec95f46eb9d835fbe9df4d6cbbf3b0d7f8 0 80 405 2016-11-11T16:53:12Z Vincenttc 21 Created page with "You may want to send an email from one of your forwarders. You can do this using the [https://webmail.ulyssis.org ULYSSIS Webmail] (for other clients see Add an alias in Gma..." wikitext text/x-wiki You may want to send an email from one of your forwarders. You can do this using the [https://webmail.ulyssis.org ULYSSIS Webmail] (for other clients see [[Add an alias in Gmail]], [[Add an alias in Thunderbird]] and [[Add an alias in Hotmail/Outlook]]) # Login into the webinterface using your ulyssis account and passsword # Go to '''Settings''' (dutch: '''Instellingen''') in the top right # Go to '''Identities''' (dutch: '''Identiteiten''') # Click on the plus sign in the bottom left # Fill the alias you want to use in in the '''Email''' (dutch: '''E-mail''') field and the name you want to be displayed in front of the address in the '''Display Name''' (dutch: '''Weergavenaam''') field. All the other fields are optional. # Click on '''Save''' (dutch: '''Opslaan''') You can now select the alias when creating an email in the webinterface. a747514817d84dc9e3032e152dab52102dcb7f79 406 405 2016-11-11T16:54:51Z Vincenttc 21 Vincenttc moved page [[Sending an Email fom an alias]] to [[Sending an Email fom a forwarder]] wikitext text/x-wiki You may want to send an email from one of your forwarders. You can do this using the [https://webmail.ulyssis.org ULYSSIS Webmail] (for other clients see [[Add an alias in Gmail]], [[Add an alias in Thunderbird]] and [[Add an alias in Hotmail/Outlook]]) # Login into the webinterface using your ulyssis account and passsword # Go to '''Settings''' (dutch: '''Instellingen''') in the top right # Go to '''Identities''' (dutch: '''Identiteiten''') # Click on the plus sign in the bottom left # Fill the alias you want to use in in the '''Email''' (dutch: '''E-mail''') field and the name you want to be displayed in front of the address in the '''Display Name''' (dutch: '''Weergavenaam''') field. All the other fields are optional. # Click on '''Save''' (dutch: '''Opslaan''') You can now select the alias when creating an email in the webinterface. a747514817d84dc9e3032e152dab52102dcb7f79 408 406 2016-11-11T21:53:33Z Vincenttc 21 wikitext text/x-wiki You may want to send an email from your @ulyssis address or one of your forwarders. You can do this using the [https://webmail.ulyssis.org ULYSSIS Webmail] (for other clients see [[Add an alias in Gmail]], [[Add an alias in Thunderbird]] and [[Add an alias in Hotmail/Outlook]]) # Login into the webinterface using your ulyssis account and passsword # Go to '''Settings''' (dutch: '''Instellingen''') in the top right # Go to '''Identities''' (dutch: '''Identiteiten''') # Click on the plus sign in the bottom left # Fill the alias you want to use in in the '''Email''' (dutch: '''E-mail''') field and the name you want to be displayed in front of the address in the '''Display Name''' (dutch: '''Weergavenaam''') field. All the other fields are optional. # Click on '''Save''' (dutch: '''Opslaan''') You can now select the alias when creating an email in the webinterface. 6c4d38aca0a052fac2de2e3c2277838d2f428041 409 408 2016-11-11T21:53:58Z Vincenttc 21 wikitext text/x-wiki You may want to send an email from your @ulyssis address or one of your forwarders. You can do this using the [https://webmail.ulyssis.org ULYSSIS Webmail] (for other clients see [[Add an alias in Gmail]], [[Add an alias in Thunderbird]] and [[Add an alias in Hotmail/Outlook]]) # Login into the [https://webmail.ulyssis.org webinterface] using your ulyssis account and passsword # Go to '''Settings''' (dutch: '''Instellingen''') in the top right # Go to '''Identities''' (dutch: '''Identiteiten''') # Click on the plus sign in the bottom left # Fill the alias you want to use in in the '''Email''' (dutch: '''E-mail''') field and the name you want to be displayed in front of the address in the '''Display Name''' (dutch: '''Weergavenaam''') field. All the other fields are optional. # Click on '''Save''' (dutch: '''Opslaan''') You can now select the alias when creating an email in the webinterface. d55670ae708f51b309c5761f70c38798e6222aab 410 409 2016-11-12T03:20:58Z Vincenttc 21 Vincenttc moved page [[Sending an Email fom a forwarder]] to [[Using a forwarder as an alias]] wikitext text/x-wiki You may want to send an email from your @ulyssis address or one of your forwarders. You can do this using the [https://webmail.ulyssis.org ULYSSIS Webmail] (for other clients see [[Add an alias in Gmail]], [[Add an alias in Thunderbird]] and [[Add an alias in Hotmail/Outlook]]) # Login into the [https://webmail.ulyssis.org webinterface] using your ulyssis account and passsword # Go to '''Settings''' (dutch: '''Instellingen''') in the top right # Go to '''Identities''' (dutch: '''Identiteiten''') # Click on the plus sign in the bottom left # Fill the alias you want to use in in the '''Email''' (dutch: '''E-mail''') field and the name you want to be displayed in front of the address in the '''Display Name''' (dutch: '''Weergavenaam''') field. All the other fields are optional. # Click on '''Save''' (dutch: '''Opslaan''') You can now select the alias when creating an email in the webinterface. d55670ae708f51b309c5761f70c38798e6222aab 0 81 407 2016-11-11T16:54:51Z Vincenttc 21 Vincenttc moved page [[Sending an Email fom an alias]] to [[Sending an Email fom a forwarder]] wikitext text/x-wiki #REDIRECT [[Sending an Email fom a forwarder]] b06a81f629928281d12e83e6404bffb2f44395bc 0 82 411 2016-11-12T03:20:59Z Vincenttc 21 Vincenttc moved page [[Sending an Email fom a forwarder]] to [[Using a forwarder as an alias]] wikitext text/x-wiki #REDIRECT [[Using a forwarder as an alias]] 25b2d98758933760cada2a25796063280ef66c6c 0 54 418 261 2016-12-28T00:35:56Z Vincenttc 21 wikitext text/x-wiki ==Google's recaptcha== ===What is recaptcha and how/will it help prevent spam ?=== For answers to those questions you can look at google's page about recaptcha( https://google.com/recaptcha) ===Installation=== This installation guide requires mediawiki '''1.26''' or higher * Go to google's recaptcha administrator page(https://www.google.com/recaptcha/admin) and register your site * Open your *LocalSettings.php* file which is in your mediawiki instalation folder * Put the following piece of text in the above mentioned file <code> require_once "$IP/extensions/ConfirmEdit/ConfirmEdit.php"; wfLoadExtension( 'ConfirmEdit/ReCaptchaNoCaptcha' ); $wgCaptchaClass = 'ReCaptchaNoCaptcha'; $wgReCaptchaSiteKey = ' '''your public/site key here''' '; $wgReCaptchaSecretKey = ' '''your private key here''' '; </code> example of public and private key (https://i.imgur.com/vGJKEXx.png) * mediawiki wil start loading recaptcha in the background and once done wil start using recaptcha for defending you from bots 3dff20a9d329e453e132f7737b7934417fe62125 0 53 422 248 2017-01-24T18:27:17Z Bert 8 wikitext text/x-wiki Because in our webserversetup PHP is installed as a common gateway interface (CGI) basic authentication will not work in its usual way. There is however a workaround. First add a .htaccess file with following code in it: <IfModule mod_rewrite.c> RewriteEngine on \n RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization},L] </IfModule> Next add the following line to your script right before the authentication: list($_SERVER['PHP_AUTH_USER'], $_SERVER['PHP_AUTH_PW']) = explode(':' , base64_decode(substr($_SERVER['HTTP_AUTHORIZATION'], 6))); Now your script should work with basic authentication. a0c7bb41ad37be7f410befbb80bfca836cf94624 0 10 423 157 2017-01-27T16:40:21Z Bert 8 wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''Katholieke Universiteit Leuven'' or ''KU Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. You can follow the above procedure every time a certificate needs to be replaced. We are however looking into automating this process in the future. 2885df1573982dd97d146781b1b576f4a5e2c910 424 423 2017-01-30T05:14:22Z Bert 8 wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''Katholieke Universiteit Leuven'' or ''KU Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. You can follow the above procedure every time a certificate needs to be replaced. We are however looking into automating this process in the future. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. 77514a66dce13869b642b4158ec950ae8088123f 0 12 426 80 2017-02-08T02:34:01Z Bert 8 wikitext text/x-wiki = Creating a database = You can create one or more PostgreSQL databases in [https://ucc.ulyssis.org UCC]. The first database you create will have the same name as your username. Subsequent databases will be prefixed with "''username''_". = Managing your database = * The easiest way to manage your database is using [https://phppgadmin.ulyssis.org phpPgAdmin]. * You can also access it via the [[Accessing shell servers over SSH|command line]] with: psql -h pgsql.ulyssis.org = Connecting to the database = You can connect to the database with the following details: * Host: <code>pgsql.ulyssis.org</code> * Login: your ULYSSIS username * Password: the PostgreSQL password you chose in UCC * Database: the database you created in UCC Note that some CMSs will assume that you use "localhost" as the host, and will hide the host option under advanced settings in the installation process. If you can't find anywhere to enter the hostname, look under advanced settings. == Connection string == If you are programming your application yourself, PostgreSQL often uses the following connection format: host=$host user=$username password=$password db=$dbname Where you replace the parts starting with <code>$</code> with the above connection details. == pg_connect == If you are using PHP's [http://www.php.net/manual/en/function.pg-connect.php pg_connect] to connect to the database, and your username is "foo", your password is "password" and your database name is "foo": <syntaxhighlight lang="php"> $connection = pg_connect("host=pgsql.ulyssis.org user=foo password=password db=foo"); </syntaxhighlight> == PDO == If you want to connect using [http://be2.php.net/manual/en/intro.pdo.php PDO], your username is "foo", your password is "password" and your database is "foo": <syntaxhighlight lang="php"> $pdo = new PDO('pgsql:host=pgsql.ulyssis.org;dbname=foo', 'foo', 'password'); </syntaxhighlight> =Accessing PostgreSQL from outside of our network= To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH-tunnel. On Linux, Mac OSX and other Unix-like Operating Systems it is easily possible to use the following command to create a tunnel to a local port (in this case 5400): ssh -f username@ssh2.ulyssis.org -L 5400:pgsql.ulyssis.org:5432 -N = PostGIS = If necessary for an application or website you wish to use on ULYSSIS, we can always enable PostGIS for the specific database you wish to use it on. Contact us at ulyssis@ulyssis.org and let us know you would like to get PostGIS enabled and on which specific database. 753c162057f17180c3f1045b30126cdc65dccf8d 0 5 427 306 2017-02-25T15:16:10Z Bcl 27 /* Mac */ wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. If your distribution does not contain an option to connect to a server, you can use [https://filezilla-project.org/ FileZilla], which is completely free. See the instructions under [[Accessing_your_files#Windows|Windows]]. [[File:UbuntuConnectToServer.png]] ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ===Mac=== Download the free and open source program [http://cyberduck.io/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> [[File:maccyberduck3.png]] Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. If you want to connect again later on, you can just click the Bookmarks icon on the top left. Next you click on History. And then you can double click to re-open the connection. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. d2c80756efa75590d64bd9d3815eedd16d9f861d 428 427 2017-02-25T15:25:55Z Bcl 27 /* Mac */ wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. If your distribution does not contain an option to connect to a server, you can use [https://filezilla-project.org/ FileZilla], which is completely free. See the instructions under [[Accessing_your_files#Windows|Windows]]. [[File:UbuntuConnectToServer.png]] ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ===Mac=== ''[https://filezilla-project.org/ FileZilla], which was mentioned above, is also available for Mac. To use it, follow [[#Windows|the instructions for Windows]]. You can also opt for [http://cyberduck.io/ Cyberduck], though. In that case, follow the instructions below.'' Download the free and open source program [http://cyberduck.io/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> [[File:maccyberduck3.png]] Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. If you want to connect again later on, you can just click the Bookmarks icon on the top left. Next you click on History. And then you can double click to re-open the connection. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. 14a1a1e2a3d20ae0975252c4d5bf6ecee1e9f6d2 448 428 2017-03-15T22:43:35Z Yoa 30 wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Connecting=== ====Linux==== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. If your distribution does not contain an option to connect to a server, you can use [https://filezilla-project.org/ FileZilla], which is completely free. See the instructions under [[Accessing_your_files#Windows|Windows]]. [[File:UbuntuConnectToServer.png]] ====Windows==== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ===== Using the quickconnect bar ===== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ===== Using the site manager ===== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ====Mac==== ''[https://filezilla-project.org/ FileZilla], which was mentioned above, is also available for Mac. To use it, follow [[#Windows|the instructions for Windows]]. You can also opt for [http://cyberduck.io/ Cyberduck], though. In that case, follow the instructions below.'' Download the free and open source program [http://cyberduck.io/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> [[File:maccyberduck3.png]] Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. If you want to connect again later on, you can just click the Bookmarks icon on the top left. Next you click on History. And then you can double click to re-open the connection. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. c7c603d5af024bd987094d0aecabcdc952a6d4b9 0 87 437 2017-02-27T22:32:55Z Yoa 30 Created page with "Cron is a job scheduler, a utility that can be used to execute shell commands at specific points in time. These jobs are also called Cron jobs, and can be edited using the Cro..." wikitext text/x-wiki Cron is a job scheduler, a utility that can be used to execute shell commands at specific points in time. These jobs are also called Cron jobs, and can be edited using the Crontab command. =The Crontab Command= To edit the cron table (crontab) file, you will use the Crontab command. The Crontab command has a few options: * <code>crontab -e</code>: Edit the crontab for the current user * <code>crontab -l</code>: List the cron jobs for the current user * <code>crontab -r</code>: Remove all cron jobs for the current user (Use the -i option to prompt before deleting) Additionally, the <code>-u</code> parameter can be used to specify a user. ==Editing The Crontab== Perform these steps to edit the crontab. * Execute the <code>crontab -e</code> * If this is the first time editing the crontab, a prompt will appear asking you to specify your text editor. It is recommended to use <code>nano</code>. * If everything is performed correctly, a file should appear. * You can edit this file. (Remember that everything after # is a comment) To add a new line to the file, you should follow this format: ┌───────────── minute (0 - 59) │ ┌───────────── hour (0 - 23) │ │ ┌───────────── day of month (1 - 31) │ │ │ ┌───────────── month (1 - 12) │ │ │ │ ┌───────────── day of week (0 - 6) (Sunday to Saturday; │ │ │ │ │ 7 is also Sunday) │ │ │ │ │ │ │ │ │ │ * * * * * command to execute For example: <code>0 * * * * python somescript.py</code> will run <code>python somescript.py</code> every hour. <code>1 0 15 * 0 somecommand</code> will run <code>somecommand</code> every month the 15th day '''or if the day is a sunday''', at 1 past midnight (00:01). =Practical Example: Scheduling Drush Updates= Drush and Cron can be used to update Drupal automatically. * First, run the <code>crontab -e</code> command. More info can be found in the previous section. * Next, add the following line to the file: <code>0 0 * * * drush pm-update http://your.website.url</code> This will execute the <code>drush pm-update http://your.website.url</code> command every day, at midnight. You can use the <code>-l</code> parameter for multi-site installs: <code>drush pm-update -l http://your.website.url</code> * Finally, save and exit the file and you're good to go! b0aa00961ce4ec73193fe5401aeb7cf7c1f10866 438 437 2017-02-27T22:33:15Z Yoa 30 wikitext text/x-wiki Cron is a job scheduler, a utility that can be used to execute shell commands at specific points in time. These jobs are also called Cron jobs, and can be edited using the Crontab command. ==The Crontab Command== To edit the cron table (crontab) file, you will use the Crontab command. The Crontab command has a few options: * <code>crontab -e</code>: Edit the crontab for the current user * <code>crontab -l</code>: List the cron jobs for the current user * <code>crontab -r</code>: Remove all cron jobs for the current user (Use the -i option to prompt before deleting) Additionally, the <code>-u</code> parameter can be used to specify a user. =Editing The Crontab= Perform these steps to edit the crontab. * Execute the <code>crontab -e</code> * If this is the first time editing the crontab, a prompt will appear asking you to specify your text editor. It is recommended to use <code>nano</code>. * If everything is performed correctly, a file should appear. * You can edit this file. (Remember that everything after # is a comment) To add a new line to the file, you should follow this format: ┌───────────── minute (0 - 59) │ ┌───────────── hour (0 - 23) │ │ ┌───────────── day of month (1 - 31) │ │ │ ┌───────────── month (1 - 12) │ │ │ │ ┌───────────── day of week (0 - 6) (Sunday to Saturday; │ │ │ │ │ 7 is also Sunday) │ │ │ │ │ │ │ │ │ │ * * * * * command to execute For example: <code>0 * * * * python somescript.py</code> will run <code>python somescript.py</code> every hour. <code>1 0 15 * 0 somecommand</code> will run <code>somecommand</code> every month the 15th day '''or if the day is a sunday''', at 1 past midnight (00:01). ==Practical Example: Scheduling Drush Updates== Drush and Cron can be used to update Drupal automatically. * First, run the <code>crontab -e</code> command. More info can be found in the previous section. * Next, add the following line to the file: <code>0 0 * * * drush pm-update http://your.website.url</code> This will execute the <code>drush pm-update http://your.website.url</code> command every day, at midnight. You can use the <code>-l</code> parameter for multi-site installs: <code>drush pm-update -l http://your.website.url</code> * Finally, save and exit the file and you're good to go! 4c322bf1f684b4c9fd86e83607acbedf29043322 439 438 2017-02-27T23:06:17Z Yoa 30 wikitext text/x-wiki Cron is a job scheduler, a utility that can be used to execute shell commands at specific points in time. These jobs are also called Cron jobs, and can be edited using the crontab command. ==The Crontab Command== To edit the cron table (crontab) file, you will use the crontab command. The crontab command has a few options: * <code>crontab -e</code>: Edit the crontab for the current user * <code>crontab -l</code>: List the cron jobs for the current user * <code>crontab -r</code>: Remove all cron jobs for the current user (Use the -i option to prompt before deleting) Additionally, the <code>-u</code> parameter can be used to specify a user. =Editing The Crontab= Perform these steps to edit the crontab. * Execute the <code>crontab -e</code> * If this is the first time editing the crontab, a prompt will appear asking you to specify your text editor. It is recommended to use <code>nano</code>. * If everything is performed correctly, a file should appear. * You can edit this file. (Remember that everything after # is a comment) To add a new line to the file, you should follow this format: ┌───────────── minute (0 - 59) │ ┌───────────── hour (0 - 23) │ │ ┌───────────── day of month (1 - 31) │ │ │ ┌───────────── month (1 - 12) │ │ │ │ ┌───────────── day of week (0 - 6) (Sunday to Saturday; │ │ │ │ │ 7 is also Sunday) │ │ │ │ │ │ │ │ │ │ * * * * * command to execute You can use an asterisk (*) if a field does not matter. For example: <code>0 * * * * python somescript.py</code> will run <code>python somescript.py</code> every hour. <code>1 0 15 * 0 somecommand</code> will run <code>somecommand</code> every month the 15th day '''or''' if the day is a Sunday, at 1 past midnight (00:01). ==Practical Example: Scheduling Drush Updates== Drush and Cron can be used to update Drupal automatically. * First, run the <code>crontab -e</code> command. More info can be found in the previous section. * Next, add the following line to the file: <code>0 0 * * * cd /path/to/your/drupal/folder/ && drush pm-update -l http://your.website.url</code> This will execute the <code>cd /path/to/your/drupal/folder/</code> command, changing the current directory to your drupal folder, and the <code>drush pm-update -l http://your.website.url</code> command, updating Drupal, every day, at midnight. The <code>&&</code> denotes a new command follows. * Finally, save and exit the file and you're good to go! bf7514aab1348d1aa3c14d7b65bc8d7a4f55b8c7 440 439 2017-02-27T23:06:45Z Yoa 30 /* Practical Example: Scheduling Drush Updates */ wikitext text/x-wiki Cron is a job scheduler, a utility that can be used to execute shell commands at specific points in time. These jobs are also called Cron jobs, and can be edited using the crontab command. ==The Crontab Command== To edit the cron table (crontab) file, you will use the crontab command. The crontab command has a few options: * <code>crontab -e</code>: Edit the crontab for the current user * <code>crontab -l</code>: List the cron jobs for the current user * <code>crontab -r</code>: Remove all cron jobs for the current user (Use the -i option to prompt before deleting) Additionally, the <code>-u</code> parameter can be used to specify a user. =Editing The Crontab= Perform these steps to edit the crontab. * Execute the <code>crontab -e</code> * If this is the first time editing the crontab, a prompt will appear asking you to specify your text editor. It is recommended to use <code>nano</code>. * If everything is performed correctly, a file should appear. * You can edit this file. (Remember that everything after # is a comment) To add a new line to the file, you should follow this format: ┌───────────── minute (0 - 59) │ ┌───────────── hour (0 - 23) │ │ ┌───────────── day of month (1 - 31) │ │ │ ┌───────────── month (1 - 12) │ │ │ │ ┌───────────── day of week (0 - 6) (Sunday to Saturday; │ │ │ │ │ 7 is also Sunday) │ │ │ │ │ │ │ │ │ │ * * * * * command to execute You can use an asterisk (*) if a field does not matter. For example: <code>0 * * * * python somescript.py</code> will run <code>python somescript.py</code> every hour. <code>1 0 15 * 0 somecommand</code> will run <code>somecommand</code> every month the 15th day '''or''' if the day is a Sunday, at 1 past midnight (00:01). ==Practical Example: Scheduling Drush Updates== Drush and Cron can be used to update Drupal automatically. * First, run the <code>crontab -e</code> command. More info can be found in the previous section. * Next, add the following line to the file: <code>0 0 * * * cd /path/to/your/drupal/folder/ && drush pm-update -l http://your.website.url</code> This will execute the <code>cd /path/to/your/drupal/folder/</code> command, changing the current directory to your drupal folder, and the <code>drush pm-update -l http://your.website.url</code> command, updating Drupal, every day, at midnight. The <code>&&</code> indicates a new command follows. * Finally, save and exit the file and you're good to go! 1b0b19cbf13c2b4712dd34ca2aa3d193608fa24c 441 440 2017-02-27T23:08:10Z Yoa 30 /* The Crontab Command */ wikitext text/x-wiki Cron is a job scheduler, a utility that can be used to execute shell commands at specific points in time. These jobs are also called Cron jobs, and can be edited using the crontab command. ==The Crontab Command== To edit the cron table (crontab) file, you will use the crontab command. The crontab command has a few options: * <code>crontab -e</code>: Edit the crontab for the current user * <code>crontab -l</code>: List the cron jobs for the current user * <code>crontab -r</code>: Remove all cron jobs for the current user (Use the -i option to prompt before deleting) =Editing The Crontab= Perform these steps to edit the crontab. * Execute the <code>crontab -e</code> * If this is the first time editing the crontab, a prompt will appear asking you to specify your text editor. It is recommended to use <code>nano</code>. * If everything is performed correctly, a file should appear. * You can edit this file. (Remember that everything after # is a comment) To add a new line to the file, you should follow this format: ┌───────────── minute (0 - 59) │ ┌───────────── hour (0 - 23) │ │ ┌───────────── day of month (1 - 31) │ │ │ ┌───────────── month (1 - 12) │ │ │ │ ┌───────────── day of week (0 - 6) (Sunday to Saturday; │ │ │ │ │ 7 is also Sunday) │ │ │ │ │ │ │ │ │ │ * * * * * command to execute You can use an asterisk (*) if a field does not matter. For example: <code>0 * * * * python somescript.py</code> will run <code>python somescript.py</code> every hour. <code>1 0 15 * 0 somecommand</code> will run <code>somecommand</code> every month the 15th day '''or''' if the day is a Sunday, at 1 past midnight (00:01). ==Practical Example: Scheduling Drush Updates== Drush and Cron can be used to update Drupal automatically. * First, run the <code>crontab -e</code> command. More info can be found in the previous section. * Next, add the following line to the file: <code>0 0 * * * cd /path/to/your/drupal/folder/ && drush pm-update -l http://your.website.url</code> This will execute the <code>cd /path/to/your/drupal/folder/</code> command, changing the current directory to your drupal folder, and the <code>drush pm-update -l http://your.website.url</code> command, updating Drupal, every day, at midnight. The <code>&&</code> indicates a new command follows. * Finally, save and exit the file and you're good to go! eaaa0fd041cb8bc7dbfaad76a9e0de96abd0a39a 442 441 2017-02-27T23:09:09Z Yoa 30 /* Editing The Crontab */ wikitext text/x-wiki Cron is a job scheduler, a utility that can be used to execute shell commands at specific points in time. These jobs are also called Cron jobs, and can be edited using the crontab command. ==The Crontab Command== To edit the cron table (crontab) file, you will use the crontab command. The crontab command has a few options: * <code>crontab -e</code>: Edit the crontab for the current user * <code>crontab -l</code>: List the cron jobs for the current user * <code>crontab -r</code>: Remove all cron jobs for the current user (Use the -i option to prompt before deleting) =Editing The Crontab= Perform these steps to edit the crontab. * Execute the <code>crontab -e</code> command * If this is the first time editing the crontab, a prompt will appear asking you to specify your text editor. It is recommended to use <code>nano</code>. * If everything is performed correctly, a file should appear. * You can edit this file. (Remember that everything after # is a comment) To add a new line to the file, you should follow this format: ┌───────────── minute (0 - 59) │ ┌───────────── hour (0 - 23) │ │ ┌───────────── day of month (1 - 31) │ │ │ ┌───────────── month (1 - 12) │ │ │ │ ┌───────────── day of week (0 - 6) (Sunday to Saturday; │ │ │ │ │ 7 is also Sunday) │ │ │ │ │ │ │ │ │ │ * * * * * command to execute You can use an asterisk (*) if a field does not matter. For example: <code>0 * * * * python somescript.py</code> will run <code>python somescript.py</code> every hour. <code>1 0 15 * 0 somecommand</code> will run <code>somecommand</code> every month the 15th day '''or''' if the day is a Sunday, at 1 past midnight (00:01). ==Practical Example: Scheduling Drush Updates== Drush and Cron can be used to update Drupal automatically. * First, run the <code>crontab -e</code> command. More info can be found in the previous section. * Next, add the following line to the file: <code>0 0 * * * cd /path/to/your/drupal/folder/ && drush pm-update -l http://your.website.url</code> This will execute the <code>cd /path/to/your/drupal/folder/</code> command, changing the current directory to your drupal folder, and the <code>drush pm-update -l http://your.website.url</code> command, updating Drupal, every day, at midnight. The <code>&&</code> indicates a new command follows. * Finally, save and exit the file and you're good to go! 1916fd951df464bf0638dba8d4cdf4df9f751ee5 443 442 2017-02-27T23:09:57Z Yoa 30 /* Editing The Crontab */ wikitext text/x-wiki Cron is a job scheduler, a utility that can be used to execute shell commands at specific points in time. These jobs are also called Cron jobs, and can be edited using the crontab command. ==The Crontab Command== To edit the cron table (crontab) file, you will use the crontab command. The crontab command has a few options: * <code>crontab -e</code>: Edit the crontab for the current user * <code>crontab -l</code>: List the cron jobs for the current user * <code>crontab -r</code>: Remove all cron jobs for the current user (Use the -i option to prompt before deleting) =Editing The Crontab= Perform these steps to edit the crontab. * Execute the <code>crontab -e</code> command * If this is the first time editing the crontab, a prompt will appear asking you to specify your text editor. If you don't know what to reply, we suggest you choose <code>nano</code>. * If everything is performed correctly, a file should appear. * You can edit this file. (Remember that everything after # is a comment) To add a new line to the file, you should follow this format: ┌───────────── minute (0 - 59) │ ┌───────────── hour (0 - 23) │ │ ┌───────────── day of month (1 - 31) │ │ │ ┌───────────── month (1 - 12) │ │ │ │ ┌───────────── day of week (0 - 6) (Sunday to Saturday; │ │ │ │ │ 7 is also Sunday) │ │ │ │ │ │ │ │ │ │ * * * * * command to execute You can use an asterisk (*) if a field does not matter. For example: <code>0 * * * * python somescript.py</code> will run <code>python somescript.py</code> every hour. <code>1 0 15 * 0 somecommand</code> will run <code>somecommand</code> every month the 15th day '''or''' if the day is a Sunday, at 1 past midnight (00:01). ==Practical Example: Scheduling Drush Updates== Drush and Cron can be used to update Drupal automatically. * First, run the <code>crontab -e</code> command. More info can be found in the previous section. * Next, add the following line to the file: <code>0 0 * * * cd /path/to/your/drupal/folder/ && drush pm-update -l http://your.website.url</code> This will execute the <code>cd /path/to/your/drupal/folder/</code> command, changing the current directory to your drupal folder, and the <code>drush pm-update -l http://your.website.url</code> command, updating Drupal, every day, at midnight. The <code>&&</code> indicates a new command follows. * Finally, save and exit the file and you're good to go! c07db9bdb9020f6a3cc5f14c4dde8d9f86ca7774 444 443 2017-02-27T23:12:38Z Yoa 30 /* Practical Example: Scheduling Drush Updates */ wikitext text/x-wiki Cron is a job scheduler, a utility that can be used to execute shell commands at specific points in time. These jobs are also called Cron jobs, and can be edited using the crontab command. ==The Crontab Command== To edit the cron table (crontab) file, you will use the crontab command. The crontab command has a few options: * <code>crontab -e</code>: Edit the crontab for the current user * <code>crontab -l</code>: List the cron jobs for the current user * <code>crontab -r</code>: Remove all cron jobs for the current user (Use the -i option to prompt before deleting) =Editing The Crontab= Perform these steps to edit the crontab. * Execute the <code>crontab -e</code> command * If this is the first time editing the crontab, a prompt will appear asking you to specify your text editor. If you don't know what to reply, we suggest you choose <code>nano</code>. * If everything is performed correctly, a file should appear. * You can edit this file. (Remember that everything after # is a comment) To add a new line to the file, you should follow this format: ┌───────────── minute (0 - 59) │ ┌───────────── hour (0 - 23) │ │ ┌───────────── day of month (1 - 31) │ │ │ ┌───────────── month (1 - 12) │ │ │ │ ┌───────────── day of week (0 - 6) (Sunday to Saturday; │ │ │ │ │ 7 is also Sunday) │ │ │ │ │ │ │ │ │ │ * * * * * command to execute You can use an asterisk (*) if a field does not matter. For example: <code>0 * * * * python somescript.py</code> will run <code>python somescript.py</code> every hour. <code>1 0 15 * 0 somecommand</code> will run <code>somecommand</code> every month the 15th day '''or''' if the day is a Sunday, at 1 past midnight (00:01). ==Real-life Example: Scheduling Drush Updates== Drush and Cron can be used to update Drupal automatically. * First, run the <code>crontab -e</code> command. More info can be found in the previous section. * Next, add the following line to the file: <code>0 0 * * * cd /path/to/your/drupal/folder/ && drush pm-update http://your.website.url</code> This will execute the <code>cd /path/to/your/drupal/folder/</code> command, changing the current directory to your drupal folder, and the <code>drush pm-update -l http://your.website.url</code> command, updating Drupal, every day, at midnight. The <code>&&</code> indicates a new command follows. * Finally, save and exit the file and you're good to go! e5a80e3cc44a79b5d106d2dfb87854352716e575 445 444 2017-02-27T23:19:18Z Yoa 30 /* Real-life Example: Scheduling Drush Updates */ wikitext text/x-wiki Cron is a job scheduler, a utility that can be used to execute shell commands at specific points in time. These jobs are also called Cron jobs, and can be edited using the crontab command. ==The Crontab Command== To edit the cron table (crontab) file, you will use the crontab command. The crontab command has a few options: * <code>crontab -e</code>: Edit the crontab for the current user * <code>crontab -l</code>: List the cron jobs for the current user * <code>crontab -r</code>: Remove all cron jobs for the current user (Use the -i option to prompt before deleting) =Editing The Crontab= Perform these steps to edit the crontab. * Execute the <code>crontab -e</code> command * If this is the first time editing the crontab, a prompt will appear asking you to specify your text editor. If you don't know what to reply, we suggest you choose <code>nano</code>. * If everything is performed correctly, a file should appear. * You can edit this file. (Remember that everything after # is a comment) To add a new line to the file, you should follow this format: ┌───────────── minute (0 - 59) │ ┌───────────── hour (0 - 23) │ │ ┌───────────── day of month (1 - 31) │ │ │ ┌───────────── month (1 - 12) │ │ │ │ ┌───────────── day of week (0 - 6) (Sunday to Saturday; │ │ │ │ │ 7 is also Sunday) │ │ │ │ │ │ │ │ │ │ * * * * * command to execute You can use an asterisk (*) if a field does not matter. For example: <code>0 * * * * python somescript.py</code> will run <code>python somescript.py</code> every hour. <code>1 0 15 * 0 somecommand</code> will run <code>somecommand</code> every month the 15th day '''or''' if the day is a Sunday, at 1 past midnight (00:01). ==Real-life Example: Scheduling Drush Updates== Drush and Cron can be used to update Drupal automatically. * First, run the <code>crontab -e</code> command. More info can be found in the previous section. * Next, add the following line to the file: <code>0 0 * * * cd /path/to/your/drupal/folder/ && drush pm-update</code> This will execute the <code>cd /path/to/your/drupal/folder/</code> command, changing the current directory to your drupal folder, and the <code>drush pm-update</code> command, updating Drupal, every day, at midnight. The <code>&&</code> indicates a new command follows. * Finally, save and exit the file and you're good to go! 143018657ce5a62cb97d5d17a9c7b7739bfc303c 6 88 449 2017-03-15T23:12:39Z Yoa 30 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 89 450 2017-03-15T23:12:54Z Yoa 30 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 90 451 2017-03-15T23:13:02Z Yoa 30 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 91 452 2017-03-15T23:13:13Z Yoa 30 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 92 453 2017-03-15T23:13:25Z Yoa 30 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 93 454 2017-03-15T23:13:39Z Yoa 30 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 5 455 448 2017-03-15T23:13:59Z Yoa 30 wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Connecting=== ====Linux==== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. If your distribution does not contain an option to connect to a server, you can use [https://filezilla-project.org/ FileZilla], which is completely free. See the instructions under [[Accessing_your_files#Windows|Windows]]. [[File:UbuntuConnectToServer.png]] ====Windows==== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ===== Using the quickconnect bar ===== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ===== Using the site manager ===== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ====Mac==== ''[https://filezilla-project.org/ FileZilla], which was mentioned above, is also available for Mac. To use it, follow [[#Windows|the instructions for Windows]]. You can also opt for [http://cyberduck.io/ Cyberduck], though. In that case, follow the instructions below.'' Download the free and open source program [http://cyberduck.io/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> [[File:maccyberduck3.png]] Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. If you want to connect again later on, you can just click the Bookmarks icon on the top left. Next you click on History. And then you can double click to re-open the connection. ===Using FileZilla=== When you connect to a server using FileZilla, the following layout will appear: ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. 612778672c4845ed0d91083097860b61f752dcb6 458 455 2017-03-15T23:29:22Z Yoa 30 /* Graphical methods */ wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Connecting=== ====Linux==== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. If your distribution does not contain an option to connect to a server, you can use [https://filezilla-project.org/ FileZilla], which is completely free. See the instructions under [[Accessing_your_files#Windows|Windows]]. [[File:UbuntuConnectToServer.png]] ====Windows==== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ===== Using the quickconnect bar ===== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ===== Using the site manager ===== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ====Mac==== ''[https://filezilla-project.org/ FileZilla], which was mentioned above, is also available for Mac. To use it, follow [[#Windows|the instructions for Windows]]. You can also opt for [http://cyberduck.io/ Cyberduck], though. In that case, follow the instructions below.'' Download the free and open source program [http://cyberduck.io/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> [[File:maccyberduck3.png]] Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. If you want to connect again later on, you can just click the Bookmarks icon on the top left. Next you click on History. And then you can double click to re-open the connection. ===Using FileZilla=== When you connect to a server using FileZilla, the following layout will appear: [[File:Base_layout.png|Right]] As you can see, the local files are located on the left-hand side, while the remote (server) files are located on the right-hand side. File navigation and paths are also present. [[File:Layout.png|Right]] To transfer a file or folder, you can drag and drop it, either from the local side to the remote side, or from the remote side to the local side. These operations represent uploading and downloading respectively. [[File:Transfer.png|Right]] You can also press enter, while selecting a file, to transfer it. [[File:Transfer2.png|Right]] To open a folder, you can press enter while selecting it. [[File:Open.png|Right]] You can delete files or folders by pressing the delete button while selecting them, or by right-clicking and clicking 'delete'. [[File:Delete.png|Right]] To create files or folders remotely, you can right-click the remote window and click 'create directory' or 'create new file'. [[File:Create_file.png|Right]] [[File:Create_directory.png|Right]] As you can see, the menu has some more interesting options, for example 'rename' or 'view/edit'. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. 19a9782a97f4ef2087c4463032580bff1cb2f4ed 459 458 2017-03-15T23:31:09Z Yoa 30 wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Connecting=== ====Linux==== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. If your distribution does not contain an option to connect to a server, you can use [https://filezilla-project.org/ FileZilla], which is completely free. See the instructions under [[Accessing_your_files#Windows|Windows]]. [[File:UbuntuConnectToServer.png]] ====Windows==== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ===== Using the quickconnect bar ===== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ===== Using the site manager ===== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ====Mac==== ''[https://filezilla-project.org/ FileZilla], which was mentioned above, is also available for Mac. To use it, follow [[#Windows|the instructions for Windows]]. You can also opt for [http://cyberduck.io/ Cyberduck], though. In that case, follow the instructions below.'' Download the free and open source program [http://cyberduck.io/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> [[File:maccyberduck3.png]] Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. If you want to connect again later on, you can just click the Bookmarks icon on the top left. Next you click on History. And then you can double click to re-open the connection. ===Using FileZilla=== When you connect to a server using FileZilla, the following layout will appear: [[File:Base_layout.png|100px|Right]] As you can see, the local files are located on the left-hand side, while the remote (server) files are located on the right-hand side. File navigation and paths are also present. [[File:Layout.png|Right]] To transfer a file or folder, you can drag and drop it, either from the local side to the remote side, or from the remote side to the local side. These operations represent uploading and downloading respectively. [[File:Transfer.png|Right]] You can also press enter, while selecting a file, to transfer it. [[File:Transfer2.png|Right]] To open a folder, you can press enter while selecting it. [[File:Open.png|Right]] You can delete files or folders by pressing the delete button while selecting them, or by right-clicking and clicking 'delete'. [[File:Delete.png|Right]] To create files or folders remotely, you can right-click the remote window and click 'create directory' or 'create new file'. [[File:Create_file.png|Right]] [[File:Create_directory.png|Right]] As you can see, the menu has some more interesting options, for example 'rename' or 'view/edit'. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. 4e06b2bc964737fb070af97d360250646957013a 460 459 2017-03-15T23:32:38Z Yoa 30 /* Using FileZilla */ wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Graphical methods== ===Connecting=== ====Linux==== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. If your distribution does not contain an option to connect to a server, you can use [https://filezilla-project.org/ FileZilla], which is completely free. See the instructions under [[Accessing_your_files#Windows|Windows]]. [[File:UbuntuConnectToServer.png]] ====Windows==== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ===== Using the quickconnect bar ===== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ===== Using the site manager ===== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ====Mac==== ''[https://filezilla-project.org/ FileZilla], which was mentioned above, is also available for Mac. To use it, follow [[#Windows|the instructions for Windows]]. You can also opt for [http://cyberduck.io/ Cyberduck], though. In that case, follow the instructions below.'' Download the free and open source program [http://cyberduck.io/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> [[File:maccyberduck3.png]] Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. If you want to connect again later on, you can just click the Bookmarks icon on the top left. Next you click on History. And then you can double click to re-open the connection. ===Using FileZilla=== When you connect to a server using FileZilla, the following layout will appear: [[File:Base_layout.png|700px|Right]] As you can see, the local files are located on the left-hand side, while the remote (server) files are located on the right-hand side. File navigation and paths are also present. [[File:Layout.png|700px|Right]] To transfer a file or folder, you can drag and drop it, either from the local side to the remote side, or from the remote side to the local side. These operations represent uploading and downloading respectively. [[File:Transfer.png|700px|Right]] You can also press enter, while selecting a file, to transfer it. [[File:Transfer2.png|700px|Right]] To open a folder, you can press enter while selecting it. [[File:Open.png|700px|Right]] You can delete files or folders by pressing the delete button while selecting them, or by right-clicking and clicking 'delete'. [[File:Delete.png|700px|Right]] To create files or folders remotely, you can right-click the remote window and click 'create directory' or 'create new file'. [[File:Create_directory.png|700px|Right]] [[File:Create_file.png|700px|Right]] As you can see, the menu has some more interesting options, for example 'rename' or 'view/edit'. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. b57d10defd39b40dc6f2f276368a6da4c7c65110 461 460 2017-03-16T15:41:24Z Yoa 30 wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Connecting== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. If your distribution does not contain an option to connect to a server, you can use [https://filezilla-project.org/ FileZilla], which is completely free. See the instructions under [[Accessing_your_files#Windows|Windows]]. [[File:UbuntuConnectToServer.png]] ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ===Mac=== ''[https://filezilla-project.org/ FileZilla], which was mentioned above, is also available for Mac. To use it, follow [[#Windows|the instructions for Windows]]. You can also opt for [http://cyberduck.io/ Cyberduck], though. In that case, follow the instructions below.'' Download the free and open source program [http://cyberduck.io/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> [[File:maccyberduck3.png]] Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. If you want to connect again later on, you can just click the Bookmarks icon on the top left. Next you click on History. And then you can double click to re-open the connection. ==Using FileZilla== When you connect to a server using FileZilla, the following layout will appear: [[File:Base_layout.png|700px|Right]] As you can see, the local files are located on the left-hand side, while the remote (server) files are located on the right-hand side. File navigation and paths are also present. [[File:Layout.png|700px|Right]] To transfer a file or folder, you can drag and drop it, either from the local side to the remote side, or from the remote side to the local side. These operations represent uploading and downloading respectively. [[File:Transfer.png|700px|Right]] You can also press enter while selecting a file, or double-click a file, to transfer it. [[File:Transfer2.png|700px|Right]] To open a folder, you can press enter while selecting it. [[File:Open.png|700px|Right]] You can delete files or folders by pressing the delete button while selecting them, or by right-clicking and clicking 'delete'. [[File:Delete.png|700px|Right]] To create files or folders remotely, you can right-click the remote window and click 'create directory' or 'create new file'. [[File:Create_directory.png|700px|Right]] [[File:Create_file.png|700px|Right]] As you can see, the menu has some more interesting options, for example 'rename' or 'view/edit'. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. 18e9b3ae8365dc452d3240e1c3d40dd4cef05f5e 462 461 2017-03-16T20:33:05Z Yoa 30 /* Using FileZilla */ wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Connecting== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. If your distribution does not contain an option to connect to a server, you can use [https://filezilla-project.org/ FileZilla], which is completely free. See the instructions under [[Accessing_your_files#Windows|Windows]]. [[File:UbuntuConnectToServer.png]] ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ===Mac=== ''[https://filezilla-project.org/ FileZilla], which was mentioned above, is also available for Mac. To use it, follow [[#Windows|the instructions for Windows]]. You can also opt for [http://cyberduck.io/ Cyberduck], though. In that case, follow the instructions below.'' Download the free and open source program [http://cyberduck.io/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> [[File:maccyberduck3.png]] Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. If you want to connect again later on, you can just click the Bookmarks icon on the top left. Next you click on History. And then you can double click to re-open the connection. ==Using FileZilla== When you connect to a server using FileZilla, the following layout will appear: [[File:Base_layout.png|700px|Right]] As you can see, the local files are located on the left-hand side, while the remote (server) files are located on the right-hand side. File navigation and paths are also present. [[File:Layout.png|700px|Right]] To transfer a file or folder, you can drag and drop it, either from the local side to the remote side, or from the remote side to the local side. These operations represent uploading and downloading respectively. [[File:Transfer.png|700px|Right]] You can also press enter while selecting a file, or double-click a file, to transfer it. [[File:Transfer2.png|700px|Right]] To open a folder, you can double-click it, or press enter while selecting it. [[File:Open.png|700px|Right]] You can delete files or folders by pressing the delete button while selecting them, or by right-clicking and clicking 'delete'. [[File:Delete.png|700px|Right]] To create files or folders remotely, you can right-click the remote window and click 'create directory' or 'create new file'. [[File:Create_directory.png|700px|Right]] [[File:Create_file.png|700px|Right]] As you can see, the menu has some more interesting options, for example 'rename' or 'view/edit'. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. 6ca4cfcdd381ce225fb245e2a49862ceb4458c24 6 94 456 2017-03-15T23:25:32Z Yoa 30 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 95 457 2017-03-15T23:26:47Z Yoa 30 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 49 463 251 2017-03-17T14:28:49Z Bert 8 wikitext text/x-wiki ==Installing Joomla on our servers is definitely easy== Installing Joomla on our servers is definitely easy. You download the install components from the http://joomla.org joomla-site. Here you get a compressed file (.zip) which you have to extract.. You get a folder with files, those files (so no the folder) you copy via filezilla or an other ftp programme to your www-map on your shellaccount. Afterwards you go to your account, I.E username.ulyssis.be, here you get a notification telling you your needs to be configured. The fist part is the "main configuration" which will be individual for every user. Afterwards click on ''Next'' which will prompt you for your database credentials & information: *'''Databasetype: ''' Select ''MySQL'' from the dropdown. *'''Hostname: ''' this is the location of the database server, use <code>mysql.ulyssis.org</code>. *'''Username: ''' this is the name you gave during the creation of your mysql account, often this is the same as your username with ULYSSIS. *'''password: ''' the password hat you gave during the creation of your mysql account * You don't change the last two fields When you're done click on “Next” twice since ftp is already configured. Here you can see the last few details. Afterwards the install will run by it own and thats it, you installed Joomla. ==Setting up multiple instances of Joomla== If you want to have multiple instances of a Joomla site then you the create a new folder in your homedir from your shell account. You need a new virtual host, you can send us an [mailto:ulyssis@ulyssis.org email] and we will create one for you. After your new virtual host is ready, you need to do all the same steps as for a regular Joomla installation. Another option is to use the Joomla [https://docs.joomla.org/Multiple_Domains_and_Web_Sites_in_a_single_Joomla!_installation multisite] option. 0e24f240e034f09ab9de363e4d89b7d66c6285f5 464 463 2017-03-19T11:20:18Z Joachim 23 /* Installing Joomla on our servers is definitely easy */ wikitext text/x-wiki ==Installing Joomla on our servers is definitely easy== Installing Joomla on our servers is definitely easy. You download the install components from the http://joomla.org joomla-site. Here you get a compressed file (.zip) which you have to extract.. You get a folder with files, those files (so no the folder) you copy via filezilla or an other ftp programme to your www-map on your shellaccount. Afterwards you go to your account, I.E username.ulyssis.be, here you get a notification telling you your MySQL database needs to be configured. The fist part is the "main configuration" which will be individual for every user. Afterwards click on ''Next'' which will prompt you for your database credentials & information: *'''Databasetype: ''' Select ''MySQL'' from the dropdown. *'''Hostname: ''' this is the location of the database server, use <code>mysql.ulyssis.org</code>. *'''Username: ''' this is the name you gave during the creation of your mysql account, often this is the same as your username with ULYSSIS. *'''password: ''' the password hat you gave during the creation of your mysql account * You don't change the last two fields When you're done click on “Next” twice since ftp is already configured. Here you can see the last few details. Afterwards the install will run by it own and thats it, you installed Joomla. ==Setting up multiple instances of Joomla== If you want to have multiple instances of a Joomla site then you the create a new folder in your homedir from your shell account. You need a new virtual host, you can send us an [mailto:ulyssis@ulyssis.org email] and we will create one for you. After your new virtual host is ready, you need to do all the same steps as for a regular Joomla installation. Another option is to use the Joomla [https://docs.joomla.org/Multiple_Domains_and_Web_Sites_in_a_single_Joomla!_installation multisite] option. 5438592c0f5e1888b95b8d1bd77720b45d8aeb61 465 464 2017-03-19T11:23:51Z Joachim 23 /* Installing Joomla on our servers is definitely easy */ wikitext text/x-wiki ==Installing Joomla on our servers is definitely easy== Installing Joomla on our servers is definitely easy. You download the install components from the http://joomla.org joomla-site. Here you get a compressed file (.zip) which you have to extract.. You get a folder with files, those files (so no the folder) you copy via filezilla or an other ftp programme to your www-map on your shellaccount. Afterwards you go to your account, I.E username.ulyssis.be, here you get a notification telling you your MySQL database needs to be configured. The fist part is the "main configuration" which will be individual for every user. Afterwards click on ''Next'' which will prompt you for your database credentials & information: *'''Databasetype: ''' Select ''MySQL'' from the dropdown. *'''Hostname: ''' this is the location of the database server, use <code>mysql.ulyssis.org</code>. *'''Username: ''' this is the name you gave during the creation of your mysql account, often this is the same as your username with ULYSSIS. *'''password: ''' the password hat you gave during the creation of your mysql account * You don't change the last two fields When you're done click on “Next” twice since ftp is already configured. Here you can see the last few details. Afterwards the install will run by its own and that's it, you have succesfully installed Joomla. ==Setting up multiple instances of Joomla== If you want to have multiple instances of a Joomla site then you the create a new folder in your homedir from your shell account. You need a new virtual host, you can send us an [mailto:ulyssis@ulyssis.org email] and we will create one for you. After your new virtual host is ready, you need to do all the same steps as for a regular Joomla installation. Another option is to use the Joomla [https://docs.joomla.org/Multiple_Domains_and_Web_Sites_in_a_single_Joomla!_installation multisite] option. 1a69c23320dc748ab8c978fcf637585ff828edea 0 3 466 446 2017-04-09T11:48:51Z Tim 25 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2016]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Regular updates on a CMS]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Anti-spam policies]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Other == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ cb3fd9fd5994f90f2fc635e2c2bb74e4acc8824a 467 466 2017-04-09T11:51:22Z Tim 25 /* Other */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2016]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] </div><div style="width:45%;float:left"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Regular updates on a CMS]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Anti-spam policies]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ bd994907eab0285dd7edb40b253ae027e1ced428 468 467 2017-04-09T11:53:15Z Tim 25 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2016]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] </div><div style="width:45%;float:left"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Regular updates on a CMS]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Anti-spam policies]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 3954e4776c21da21a9fbf6ef9056188b7774b873 476 468 2017-09-04T19:37:37Z Yoa 30 /* Files */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] * [[Using Filezilla]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2016]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] </div><div style="width:45%;float:left"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Regular updates on a CMS]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Anti-spam policies]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 2b91878a2bda7725edec801ee37ac3877691d1c1 477 476 2017-09-04T19:38:02Z Yoa 30 oops wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2016]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] </div><div style="width:45%;float:left"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Regular updates on a CMS]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Anti-spam policies]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ b23368cde830a1d98408b519d09cba66d00e446b 491 477 2017-09-14T18:39:49Z Yoa 30 /* Security & anti-spam */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2016]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] </div><div style="width:45%;float:left"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Regular updates on a CMS]] * [[CMS Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Anti-spam policies]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 26bc0405430134eba008e04f469fec9785f669b5 492 491 2017-09-14T18:40:52Z Yoa 30 /* Security & anti-spam */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2016]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] </div><div style="width:45%;float:left"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Regular updates on a CMS]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Anti-spam policies]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ ed362ca8dcefa1a9c96a66ae724c60f4cd08a00f 0 73 470 447 2017-05-09T14:38:22Z Travolter 31 /* User-wide installation */ wikitext text/x-wiki We often get the question at our LaTeX workshop how to properly install the kulemt package. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading "kulemt-tds.zip" from ftp://ftp.esat.kuleuven.be/latex/kulemt/. == One-time use == Most people will only use this package once, for their master thesis. In this case, you can just put the necessary files in the same folder as your LaTeX project. The easiest way to accomplish this, is to unzip the downloaded file and in the unzipped folder, navigate to the directory "tex/latex/kulemt". Here, copy the following files to the same directory as your LaTeX project: kulemt.cfg, kulemt.cls, kulemtx.sty, logokul.eps and logokuleng.eps. == User-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package in a central location where LaTeX can find it autonomously. When using TeXLive, as we recommend, this involves a bit more work. First, you should find where to install the packages for your user. This is called the TEXMFHOME. The default location of this folder is: * For Windows: the folder "texmf" in your %USERPROFILE% (C:\Users\YourUsername for Windows Vista and up). * For Linux: "~/texmf" * For OS X/macOS: "~/Library/texmf" It is possible that this folder needs to be created first. From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location (note: the directory itself, not only its contents). If this does not work, or if you want to check the directory first, please refer to the section [[#Finding the TEXMFHOME]] at the bottom of this document. For a more technical overview, you can follow the general guidelines provided by the department: ftp://ftp.esat.kuleuven.be/latex/kulemt/README. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English}, % in case of a Dutch master udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> == Finding the TEXMFHOME == In case the default location for the TEXMFHOME as stated above does not work, you can find the correct directory through command-line. In Linux and macOS, look for an app called "Terminal". In Windows, search for "cmd" using the start menu. The program has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf If you have found this folder, copy the entire "tex" directory from the extracted kulemt-tds.zip to this location, as stated before. Create the folder if needed. == Troubleshooting == The kulemt package requires the memoir package. Make sure you have this package. We recommend installing the texlive-full package on Ubuntu. When you use the installer from [ftp://ftp.ulyssis.org/LaTeX-Workshop/installers/ our FTP server] for Windows or OS X/macOS, you will automatically have the entire LaTeX suite. 96bb2fe2dc91ef3df30a8041e7b429dbd1b2d2b8 471 470 2017-05-09T14:39:07Z Travolter 31 /* User-wide installation */ wikitext text/x-wiki We often get the question at our LaTeX workshop how to properly install the kulemt package. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading "kulemt-tds.zip" from ftp://ftp.esat.kuleuven.be/latex/kulemt/. == One-time use == Most people will only use this package once, for their master thesis. In this case, you can just put the necessary files in the same folder as your LaTeX project. The easiest way to accomplish this, is to unzip the downloaded file and in the unzipped folder, navigate to the directory "tex/latex/kulemt". Here, copy the following files to the same directory as your LaTeX project: kulemt.cfg, kulemt.cls, kulemtx.sty, logokul.eps and logokuleng.eps. == User-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package in a central location where LaTeX can find it autonomously when using TeXLive, as we recommend. This involves a bit more work. First, you should find where to install the packages for your user. This is called the TEXMFHOME. The default location of this folder is: * For Windows: the folder "texmf" in your %USERPROFILE% (C:\Users\YourUsername for Windows Vista and up). * For Linux: "~/texmf" * For OS X/macOS: "~/Library/texmf" It is possible that this folder needs to be created first. From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location (note: the directory itself, not only its contents). If this does not work, or if you want to check the directory first, please refer to the section [[#Finding the TEXMFHOME]] at the bottom of this document. For a more technical overview, you can follow the general guidelines provided by the department: ftp://ftp.esat.kuleuven.be/latex/kulemt/README. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English}, % in case of a Dutch master udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> == Finding the TEXMFHOME == In case the default location for the TEXMFHOME as stated above does not work, you can find the correct directory through command-line. In Linux and macOS, look for an app called "Terminal". In Windows, search for "cmd" using the start menu. The program has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf If you have found this folder, copy the entire "tex" directory from the extracted kulemt-tds.zip to this location, as stated before. Create the folder if needed. == Troubleshooting == The kulemt package requires the memoir package. Make sure you have this package. We recommend installing the texlive-full package on Ubuntu. When you use the installer from [ftp://ftp.ulyssis.org/LaTeX-Workshop/installers/ our FTP server] for Windows or OS X/macOS, you will automatically have the entire LaTeX suite. 7eef4e54c9c6278d6b4c9112b43846d8dd153735 472 471 2017-05-09T14:45:26Z Travolter 31 /* User-wide installation */ wikitext text/x-wiki We often get the question at our LaTeX workshop how to properly install the kulemt package. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading "kulemt-tds.zip" from ftp://ftp.esat.kuleuven.be/latex/kulemt/. == One-time use == Most people will only use this package once, for their master thesis. In this case, you can just put the necessary files in the same folder as your LaTeX project. The easiest way to accomplish this, is to unzip the downloaded file and in the unzipped folder, navigate to the directory "tex/latex/kulemt". Here, copy the following files to the same directory as your LaTeX project: kulemt.cfg, kulemt.cls, kulemtx.sty, logokul.eps and logokuleng.eps. == User-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package in a central location where LaTeX can find it autonomously. When using TeXLive, as we recommend, this involves a bit more work. First, you should find where to install the packages for your user. This is called the TEXMFHOME. The default location of this folder is: * For Windows: the folder "texmf" in your %USERPROFILE% (C:\Users\YourUsername for Windows Vista and up). * For Linux: "~/texmf" * For OS X/macOS: "~/Library/texmf" It is possible that this folder needs to be created first. From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location (note: the directory itself, not only its contents). If this does not work, or if you want to check the directory first, please refer to the section [[#Finding the TEXMFHOME]] at the bottom of this document. For a more technical overview, you can follow the general guidelines provided by the department: ftp://ftp.esat.kuleuven.be/latex/kulemt/README. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English}, % in case of a Dutch master udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> == Finding the TEXMFHOME == In case the default location for the TEXMFHOME as stated above does not work, you can find the correct directory through command-line. In Linux and macOS, look for an app called "Terminal". In Windows, search for "cmd" using the start menu. The program has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf If you have found this folder, copy the entire "tex" directory from the extracted kulemt-tds.zip to this location, as stated before. Create the folder if needed. == Troubleshooting == The kulemt package requires the memoir package. Make sure you have this package. We recommend installing the texlive-full package on Ubuntu. When you use the installer from [ftp://ftp.ulyssis.org/LaTeX-Workshop/installers/ our FTP server] for Windows or OS X/macOS, you will automatically have the entire LaTeX suite. 96bb2fe2dc91ef3df30a8041e7b429dbd1b2d2b8 0 37 473 367 2017-08-09T20:34:21Z Lars 26 /* FastCGI */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</pre> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' Do not place sensitive files inside the web accessible folder.Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.</div> It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than were it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> Or, for Python 3: <pre>virtualenv ~/.venv --python=python3</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [http://flask.pocoo.org/docs/0.10/deploying/fastcgi/ Flask documentation for FastCGI] dcaf334b155be8f8037669c8955732a4e2941e4a 0 10 474 424 2017-08-27T13:03:59Z Bert 8 wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. You can follow the above procedure every time a certificate needs to be replaced. We are however looking into automating this process in the future. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. 4b96a91c2449e8558dda1cb1770bf3661931c1e7 0 43 475 396 2017-09-03T13:51:39Z Bert 8 wikitext text/x-wiki You may want to receive e-mail from ulyssis on another email provider. It is very easy to set this up. = Change the forwarders for your @ulyssis email address = # Go to ucc.ulyssis.org and log in with your username and password. # On the right side, click on '''Mail'''. # Under '''Address forward''' you can change the forward address of your ULYSSIS mail by clicking on '''edit'''. # Choose '''forward''' and enter the email address you want to forward your ULYSSIS mail to and save the changes. # If you forward to Gmail, Hotmail. or use Thunderbird, we recommend looking at [[Using a forwarder as an alias]] so you can send mails under the forwarding address instead of just your own. = Change the forwarders for other domains = # Go to ucc.ulyssis.org and log in with your username and password. # On the right side, click on '''Mail'''. # Under '''Virtual Domains''', click on the domain you want to change. # You can change a forwarder by clicking on '''edit''' or on '''Add alias''' and add the forwarders you want. # Save your changes = Use your mailbox and forwarders at the same time = An alternative way to set the forwarders, that will also allow you to use your mailbox and the webinterface, is to use a .forward file. On each line of this file, you can specify to wich addresses you want to forward the email. If one of the addresses is the same as your @ulyssis address, then the mail will also be placed in your ULYSSIS mailbox. In the following example, your @ulyssis email address is <code>user@ulyssis.org</code>. Example .forward file: user@ulyssis.org example@gmail.com example2@skynet.be This will place the email in your ULYSSIS mailbox so that you can access it from the webinterface or your local mailclient. It will also forward the mail to <code>example@gmail.com</code> and <code>example2@skynet.be</code>. To use this, place a .forward file with the prefered email addresses in your homedir, see [[Accessing your files]], and set your forwarder to 'Inbox' in https://ucc.ulyssis.org/mail 61b98a7a1291b03078166ffa2ed929b3e7e33746 0 96 478 2017-09-04T20:46:13Z Yoa 30 Created page with "==Introduction== Content Management Systems, or CMS's, are easy tools to set up a website without requiring much programming or configuration. However, as is common in a lot o..." wikitext text/x-wiki ==Introduction== Content Management Systems, or CMS's, are easy tools to set up a website without requiring much programming or configuration. However, as is common in a lot of popular and wide-spread software, bugs or errors in the code occur. These errors can be exploited by hackers to gain access to websites or databases connected to those CMS's. Whenever a new update for a CMS, or other popular software (MediaWiki, PhpBB) is released, those hackers will try to implement them as fast as possible in order to hack the most websites. This is why it's critical to update a CMS, plugins/themes, or any related software as soon as the update comes out. To help you facilitate this, we have created a tool to help you keep the most popular software up-to-date. Currently this feature is only active if you have an Org or Kring account. ==Supported Software== * Drupal, Drupal Modules, Drupal Themes * Joomla (Joomla Plugins are not supported yet) * MediaWiki (MediaWiki Extensions and Themes are not supported yet) * PhpBB, PhpBB Plugins, PhpBB Styles * WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the CMS Version Checker performs two big steps: * Retrieve all outdated software and respective locations from a database * Mail accounts using outdated software * Scan relevant files, detect supported software, and store in database ===Retrieval=== Information about any outdated, supported piece of software (see above), is stored in a local SQLite database. During the first step, all entries added more than a week ago (this to allow users the time to update independently) are retrieved from the database. If the software is not present anymore at the given location, the entry is removed. If the version in the database is equal to the version at the location, the responsible user has not updated the software and a mail will be sent. If the version is not equal, and the software is completely up-to-date, the entry is removed from the database. Otherwise, if the software is updated but not completely up-to-date, the timer for this entry will be reset, giving the acount owner an extra week to update the software completely. ===Mailing=== Any outdated software for a particular user will be collected and mailed in the same e-mail, to the personal account e-mail address and the @ulyssis.org e-mail address. The mail will contain the name, location, current version, and latest version of all outdated software. In addition, a comprehensive status report, containing all outdated, invalid and detected software, will also be mailed to the ULYSSIS members. ===Scanning=== During the last step, new software installations will be detected. For every active Org and Kring, the apache document roots are retrieved, and those directories are searched recursively to find signature files from specific software, as listed above. Those files do not contain personal information. If outdated software is found, and there is no entry in the database yet, the software location and version (among other information) is stored in the SQLite database. ==Stored Data== The following data is stored in the SQLite database: * The file location * The responsible Org or Kring * The personal account e-mail address * The detected software version * The type and name of the software * The update URL for the software * The date the entry was added ==Ignored Paths== The CMS Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org 8227eb5f18f8438be8731649d7f0cf321c5fd566 479 478 2017-09-04T20:54:09Z Bert 8 /* Introduction */ wikitext text/x-wiki ==Introduction== Content Management Systems, or CMS's, are easy tools to set up a website without requiring much programming or configuration. However, as is common in a lot of popular and wide-spread software, bugs or errors in the code occur. These errors can be exploited by hackers to gain access to websites or databases connected to those CMS's. Whenever a new update for a CMS, or other popular software (MediaWiki, PhpBB) is released, those hackers will try to implement them as fast as possible in order to hack the most websites. This is why it's critical to update a CMS, plugins/themes, or any related software as soon as the update comes out. To help you facilitate this, we have created a tool to help you keep the most popular software up-to-date. Currently this feature is only active if you have an organisation or student union (kring/facultair overlegorgaan) account. ==Supported Software== * Drupal, Drupal Modules, Drupal Themes * Joomla (Joomla Plugins are not supported yet) * MediaWiki (MediaWiki Extensions and Themes are not supported yet) * PhpBB, PhpBB Plugins, PhpBB Styles * WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the CMS Version Checker performs two big steps: * Retrieve all outdated software and respective locations from a database * Mail accounts using outdated software * Scan relevant files, detect supported software, and store in database ===Retrieval=== Information about any outdated, supported piece of software (see above), is stored in a local SQLite database. During the first step, all entries added more than a week ago (this to allow users the time to update independently) are retrieved from the database. If the software is not present anymore at the given location, the entry is removed. If the version in the database is equal to the version at the location, the responsible user has not updated the software and a mail will be sent. If the version is not equal, and the software is completely up-to-date, the entry is removed from the database. Otherwise, if the software is updated but not completely up-to-date, the timer for this entry will be reset, giving the acount owner an extra week to update the software completely. ===Mailing=== Any outdated software for a particular user will be collected and mailed in the same e-mail, to the personal account e-mail address and the @ulyssis.org e-mail address. The mail will contain the name, location, current version, and latest version of all outdated software. In addition, a comprehensive status report, containing all outdated, invalid and detected software, will also be mailed to the ULYSSIS members. ===Scanning=== During the last step, new software installations will be detected. For every active Org and Kring, the apache document roots are retrieved, and those directories are searched recursively to find signature files from specific software, as listed above. Those files do not contain personal information. If outdated software is found, and there is no entry in the database yet, the software location and version (among other information) is stored in the SQLite database. ==Stored Data== The following data is stored in the SQLite database: * The file location * The responsible Org or Kring * The personal account e-mail address * The detected software version * The type and name of the software * The update URL for the software * The date the entry was added ==Ignored Paths== The CMS Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org bf678466257865a73b372f29c61d7f8f12d5212e 480 479 2017-09-04T21:18:03Z Yoa 30 /* Operation */ wikitext text/x-wiki ==Introduction== Content Management Systems, or CMS's, are easy tools to set up a website without requiring much programming or configuration. However, as is common in a lot of popular and wide-spread software, bugs or errors in the code occur. These errors can be exploited by hackers to gain access to websites or databases connected to those CMS's. Whenever a new update for a CMS, or other popular software (MediaWiki, PhpBB) is released, those hackers will try to implement them as fast as possible in order to hack the most websites. This is why it's critical to update a CMS, plugins/themes, or any related software as soon as the update comes out. To help you facilitate this, we have created a tool to help you keep the most popular software up-to-date. Currently this feature is only active if you have an organisation or student union (kring/facultair overlegorgaan) account. ==Supported Software== * Drupal, Drupal Modules, Drupal Themes * Joomla (Joomla Plugins are not supported yet) * MediaWiki (MediaWiki Extensions and Themes are not supported yet) * PhpBB, PhpBB Plugins, PhpBB Styles * WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the CMS Version Checker performs two big steps: * Retrieve all outdated software and respective locations from a database, and check their version * Mail accounts using outdated software * Scan relevant files, detect supported software, and store in database ===Version checking=== Information about any outdated, supported piece of software (see above), is stored in a local SQLite database. During the first step, all entries added more than a week ago (this to allow users the time to update independently) are retrieved from the database. If the software is not present anymore at the given location, the entry is removed. If the version in the database is equal to the version at the location, the responsible user has not updated the software and a mail will be sent. If the version is not equal, and the software is completely up-to-date, the entry is removed from the database. Otherwise, if the software is updated but not completely up-to-date, the timer for this entry will be reset, giving the acount owner an extra week to update the software completely. ===Mailing=== Any outdated software for a particular user will be collected and mailed in the same e-mail, to the personal account e-mail address and the @ulyssis.org e-mail address. The mail will contain the name, location, current version, and latest version of all outdated software. In addition, a comprehensive status report, containing all outdated, invalid and detected software, will also be mailed to the ULYSSIS members. ===Scanning=== During the last step, new software installations will be detected. For every active Org and Kring, the apache document roots are retrieved, and those directories are searched recursively to find signature files from specific software, as listed above. Those files do not contain personal information. If outdated software is found, and there is no entry in the database yet, the software location and version (among other information) is stored in the SQLite database. ==Stored Data== The following data is stored in the SQLite database: * The file location * The responsible Org or Kring * The personal account e-mail address * The detected software version * The type and name of the software * The update URL for the software * The date the entry was added ==Ignored Paths== The CMS Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org e3ec76d8c91fc3d4d43b32d5b2cc359a14f872cf 481 480 2017-09-04T22:04:08Z Bert 8 /* Operation */ wikitext text/x-wiki ==Introduction== Content Management Systems, or CMS's, are easy tools to set up a website without requiring much programming or configuration. However, as is common in a lot of popular and wide-spread software, bugs or errors in the code occur. These errors can be exploited by hackers to gain access to websites or databases connected to those CMS's. Whenever a new update for a CMS, or other popular software (MediaWiki, PhpBB) is released, those hackers will try to implement them as fast as possible in order to hack the most websites. This is why it's critical to update a CMS, plugins/themes, or any related software as soon as the update comes out. To help you facilitate this, we have created a tool to help you keep the most popular software up-to-date. Currently this feature is only active if you have an organisation or student union (kring/facultair overlegorgaan) account. ==Supported Software== * Drupal, Drupal Modules, Drupal Themes * Joomla (Joomla Plugins are not supported yet) * MediaWiki (MediaWiki Extensions and Themes are not supported yet) * PhpBB, PhpBB Plugins, PhpBB Styles * WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the CMS Version Checker performs three steps: * Retrieve all outdated software and respective locations from a database, and check their version * Mail accounts using outdated software * Scan relevant files, detect supported software, and store in database ===Version checking=== Information about any outdated, supported piece of software (see above), is stored in a local SQLite database. During the first step, all entries added more than a week ago (this to allow users the time to update independently) are retrieved from the database. If the software is not present anymore at the given location, the entry is removed. If the version in the database is equal to the version at the location, the responsible user has not updated the software and a mail will be sent. If the version is not equal, and the software is completely up-to-date, the entry is removed from the database. Otherwise, if the software is updated but not completely up-to-date, the timer for this entry will be reset, giving the acount owner an extra week to update the software completely. ===Mailing=== Any outdated software for a particular user will be collected and mailed in the same e-mail, to the personal account e-mail address and the @ulyssis.org e-mail address. The mail will contain the name, location, current version, and latest version of all outdated software. In addition, a comprehensive status report, containing all outdated, invalid and detected software, will also be mailed to the ULYSSIS members. ===Scanning=== During the last step, new software installations will be detected. For every active Org and Kring, the apache document roots are retrieved, and those directories are searched recursively to find signature files from specific software, as listed above. Those files do not contain personal information. If outdated software is found, and there is no entry in the database yet, the software location and version (among other information) is stored in the SQLite database. ==Stored Data== The following data is stored in the SQLite database: * The file location * The responsible Org or Kring * The personal account e-mail address * The detected software version * The type and name of the software * The update URL for the software * The date the entry was added ==Ignored Paths== The CMS Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org b7d5fa84b78bdcc562a7257fd27856f8b1f0e62c 482 481 2017-09-04T22:21:21Z Bert 8 /* Scanning */ wikitext text/x-wiki ==Introduction== Content Management Systems, or CMS's, are easy tools to set up a website without requiring much programming or configuration. However, as is common in a lot of popular and wide-spread software, bugs or errors in the code occur. These errors can be exploited by hackers to gain access to websites or databases connected to those CMS's. Whenever a new update for a CMS, or other popular software (MediaWiki, PhpBB) is released, those hackers will try to implement them as fast as possible in order to hack the most websites. This is why it's critical to update a CMS, plugins/themes, or any related software as soon as the update comes out. To help you facilitate this, we have created a tool to help you keep the most popular software up-to-date. Currently this feature is only active if you have an organisation or student union (kring/facultair overlegorgaan) account. ==Supported Software== * Drupal, Drupal Modules, Drupal Themes * Joomla (Joomla Plugins are not supported yet) * MediaWiki (MediaWiki Extensions and Themes are not supported yet) * PhpBB, PhpBB Plugins, PhpBB Styles * WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the CMS Version Checker performs three steps: * Retrieve all outdated software and respective locations from a database, and check their version * Mail accounts using outdated software * Scan relevant files, detect supported software, and store in database ===Version checking=== Information about any outdated, supported piece of software (see above), is stored in a local SQLite database. During the first step, all entries added more than a week ago (this to allow users the time to update independently) are retrieved from the database. If the software is not present anymore at the given location, the entry is removed. If the version in the database is equal to the version at the location, the responsible user has not updated the software and a mail will be sent. If the version is not equal, and the software is completely up-to-date, the entry is removed from the database. Otherwise, if the software is updated but not completely up-to-date, the timer for this entry will be reset, giving the acount owner an extra week to update the software completely. ===Mailing=== Any outdated software for a particular user will be collected and mailed in the same e-mail, to the personal account e-mail address and the @ulyssis.org e-mail address. The mail will contain the name, location, current version, and latest version of all outdated software. In addition, a comprehensive status report, containing all outdated, invalid and detected software, will also be mailed to the ULYSSIS members. ===Scanning=== During the last step, new software installations will be detected. For every active organisation and student union (kring/facultair overlegorgaan) account, the apache document roots are retrieved, and those directories are searched recursively to find signature files from specific software, as listed above. Those files do not contain personal information. If outdated software is found, and there is no entry in the database yet, the software location and version (among other information) is stored in the SQLite database. ==Stored Data== The following data is stored in the SQLite database: * The file location * The responsible Org or Kring * The personal account e-mail address * The detected software version * The type and name of the software * The update URL for the software * The date the entry was added ==Ignored Paths== The CMS Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org f26677e95b6041576f742c74456177482060ba16 483 482 2017-09-04T22:22:40Z Bert 8 /* Stored Data */ wikitext text/x-wiki ==Introduction== Content Management Systems, or CMS's, are easy tools to set up a website without requiring much programming or configuration. However, as is common in a lot of popular and wide-spread software, bugs or errors in the code occur. These errors can be exploited by hackers to gain access to websites or databases connected to those CMS's. Whenever a new update for a CMS, or other popular software (MediaWiki, PhpBB) is released, those hackers will try to implement them as fast as possible in order to hack the most websites. This is why it's critical to update a CMS, plugins/themes, or any related software as soon as the update comes out. To help you facilitate this, we have created a tool to help you keep the most popular software up-to-date. Currently this feature is only active if you have an organisation or student union (kring/facultair overlegorgaan) account. ==Supported Software== * Drupal, Drupal Modules, Drupal Themes * Joomla (Joomla Plugins are not supported yet) * MediaWiki (MediaWiki Extensions and Themes are not supported yet) * PhpBB, PhpBB Plugins, PhpBB Styles * WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the CMS Version Checker performs three steps: * Retrieve all outdated software and respective locations from a database, and check their version * Mail accounts using outdated software * Scan relevant files, detect supported software, and store in database ===Version checking=== Information about any outdated, supported piece of software (see above), is stored in a local SQLite database. During the first step, all entries added more than a week ago (this to allow users the time to update independently) are retrieved from the database. If the software is not present anymore at the given location, the entry is removed. If the version in the database is equal to the version at the location, the responsible user has not updated the software and a mail will be sent. If the version is not equal, and the software is completely up-to-date, the entry is removed from the database. Otherwise, if the software is updated but not completely up-to-date, the timer for this entry will be reset, giving the acount owner an extra week to update the software completely. ===Mailing=== Any outdated software for a particular user will be collected and mailed in the same e-mail, to the personal account e-mail address and the @ulyssis.org e-mail address. The mail will contain the name, location, current version, and latest version of all outdated software. In addition, a comprehensive status report, containing all outdated, invalid and detected software, will also be mailed to the ULYSSIS members. ===Scanning=== During the last step, new software installations will be detected. For every active organisation and student union (kring/facultair overlegorgaan) account, the apache document roots are retrieved, and those directories are searched recursively to find signature files from specific software, as listed above. Those files do not contain personal information. If outdated software is found, and there is no entry in the database yet, the software location and version (among other information) is stored in the SQLite database. ==Stored Data== The following data is stored in the SQLite database: * The file location * The responsible organisation or student union (kring/facultair overlegorgaan) * The personal account e-mail address * The detected software version * The type and name of the software * The update URL for the software * The date the entry was added ==Ignored Paths== The CMS Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org b5f27833dc339bac2de8667fb1c931c9c2474250 484 483 2017-09-04T22:23:03Z Bert 8 /* Stored Data */ wikitext text/x-wiki ==Introduction== Content Management Systems, or CMS's, are easy tools to set up a website without requiring much programming or configuration. However, as is common in a lot of popular and wide-spread software, bugs or errors in the code occur. These errors can be exploited by hackers to gain access to websites or databases connected to those CMS's. Whenever a new update for a CMS, or other popular software (MediaWiki, PhpBB) is released, those hackers will try to implement them as fast as possible in order to hack the most websites. This is why it's critical to update a CMS, plugins/themes, or any related software as soon as the update comes out. To help you facilitate this, we have created a tool to help you keep the most popular software up-to-date. Currently this feature is only active if you have an organisation or student union (kring/facultair overlegorgaan) account. ==Supported Software== * Drupal, Drupal Modules, Drupal Themes * Joomla (Joomla Plugins are not supported yet) * MediaWiki (MediaWiki Extensions and Themes are not supported yet) * PhpBB, PhpBB Plugins, PhpBB Styles * WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the CMS Version Checker performs three steps: * Retrieve all outdated software and respective locations from a database, and check their version * Mail accounts using outdated software * Scan relevant files, detect supported software, and store in database ===Version checking=== Information about any outdated, supported piece of software (see above), is stored in a local SQLite database. During the first step, all entries added more than a week ago (this to allow users the time to update independently) are retrieved from the database. If the software is not present anymore at the given location, the entry is removed. If the version in the database is equal to the version at the location, the responsible user has not updated the software and a mail will be sent. If the version is not equal, and the software is completely up-to-date, the entry is removed from the database. Otherwise, if the software is updated but not completely up-to-date, the timer for this entry will be reset, giving the acount owner an extra week to update the software completely. ===Mailing=== Any outdated software for a particular user will be collected and mailed in the same e-mail, to the personal account e-mail address and the @ulyssis.org e-mail address. The mail will contain the name, location, current version, and latest version of all outdated software. In addition, a comprehensive status report, containing all outdated, invalid and detected software, will also be mailed to the ULYSSIS members. ===Scanning=== During the last step, new software installations will be detected. For every active organisation and student union (kring/facultair overlegorgaan) account, the apache document roots are retrieved, and those directories are searched recursively to find signature files from specific software, as listed above. Those files do not contain personal information. If outdated software is found, and there is no entry in the database yet, the software location and version (among other information) is stored in the SQLite database. ==Stored Data== The following data is stored in the SQLite database: * The location of the CMS, plugin/extension or theme * The responsible organisation or student union (kring/facultair overlegorgaan) * The personal account e-mail address * The detected software version * The type and name of the software * The update URL for the software * The date the entry was added ==Ignored Paths== The CMS Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org 514d01eb37ad210c7e1aacc57b95c54fd7d2d511 485 484 2017-09-04T22:23:56Z Bert 8 /* Ignored Paths */ wikitext text/x-wiki ==Introduction== Content Management Systems, or CMS's, are easy tools to set up a website without requiring much programming or configuration. However, as is common in a lot of popular and wide-spread software, bugs or errors in the code occur. These errors can be exploited by hackers to gain access to websites or databases connected to those CMS's. Whenever a new update for a CMS, or other popular software (MediaWiki, PhpBB) is released, those hackers will try to implement them as fast as possible in order to hack the most websites. This is why it's critical to update a CMS, plugins/themes, or any related software as soon as the update comes out. To help you facilitate this, we have created a tool to help you keep the most popular software up-to-date. Currently this feature is only active if you have an organisation or student union (kring/facultair overlegorgaan) account. ==Supported Software== * Drupal, Drupal Modules, Drupal Themes * Joomla (Joomla Plugins are not supported yet) * MediaWiki (MediaWiki Extensions and Themes are not supported yet) * PhpBB, PhpBB Plugins, PhpBB Styles * WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the CMS Version Checker performs three steps: * Retrieve all outdated software and respective locations from a database, and check their version * Mail accounts using outdated software * Scan relevant files, detect supported software, and store in database ===Version checking=== Information about any outdated, supported piece of software (see above), is stored in a local SQLite database. During the first step, all entries added more than a week ago (this to allow users the time to update independently) are retrieved from the database. If the software is not present anymore at the given location, the entry is removed. If the version in the database is equal to the version at the location, the responsible user has not updated the software and a mail will be sent. If the version is not equal, and the software is completely up-to-date, the entry is removed from the database. Otherwise, if the software is updated but not completely up-to-date, the timer for this entry will be reset, giving the acount owner an extra week to update the software completely. ===Mailing=== Any outdated software for a particular user will be collected and mailed in the same e-mail, to the personal account e-mail address and the @ulyssis.org e-mail address. The mail will contain the name, location, current version, and latest version of all outdated software. In addition, a comprehensive status report, containing all outdated, invalid and detected software, will also be mailed to the ULYSSIS members. ===Scanning=== During the last step, new software installations will be detected. For every active organisation and student union (kring/facultair overlegorgaan) account, the apache document roots are retrieved, and those directories are searched recursively to find signature files from specific software, as listed above. Those files do not contain personal information. If outdated software is found, and there is no entry in the database yet, the software location and version (among other information) is stored in the SQLite database. ==Stored Data== The following data is stored in the SQLite database: * The location of the CMS, plugin/extension or theme * The responsible organisation or student union (kring/facultair overlegorgaan) * The personal account e-mail address * The detected software version * The type and name of the software * The update URL for the software * The date the entry was added ==Ignored Paths== The CMS Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org 041babed405613684ea373614e1158dfbbc1af45 486 485 2017-09-04T22:24:49Z Bert 8 /* Ignored Paths */ wikitext text/x-wiki ==Introduction== Content Management Systems, or CMS's, are easy tools to set up a website without requiring much programming or configuration. However, as is common in a lot of popular and wide-spread software, bugs or errors in the code occur. These errors can be exploited by hackers to gain access to websites or databases connected to those CMS's. Whenever a new update for a CMS, or other popular software (MediaWiki, PhpBB) is released, those hackers will try to implement them as fast as possible in order to hack the most websites. This is why it's critical to update a CMS, plugins/themes, or any related software as soon as the update comes out. To help you facilitate this, we have created a tool to help you keep the most popular software up-to-date. Currently this feature is only active if you have an organisation or student union (kring/facultair overlegorgaan) account. ==Supported Software== * Drupal, Drupal Modules, Drupal Themes * Joomla (Joomla Plugins are not supported yet) * MediaWiki (MediaWiki Extensions and Themes are not supported yet) * PhpBB, PhpBB Plugins, PhpBB Styles * WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the CMS Version Checker performs three steps: * Retrieve all outdated software and respective locations from a database, and check their version * Mail accounts using outdated software * Scan relevant files, detect supported software, and store in database ===Version checking=== Information about any outdated, supported piece of software (see above), is stored in a local SQLite database. During the first step, all entries added more than a week ago (this to allow users the time to update independently) are retrieved from the database. If the software is not present anymore at the given location, the entry is removed. If the version in the database is equal to the version at the location, the responsible user has not updated the software and a mail will be sent. If the version is not equal, and the software is completely up-to-date, the entry is removed from the database. Otherwise, if the software is updated but not completely up-to-date, the timer for this entry will be reset, giving the acount owner an extra week to update the software completely. ===Mailing=== Any outdated software for a particular user will be collected and mailed in the same e-mail, to the personal account e-mail address and the @ulyssis.org e-mail address. The mail will contain the name, location, current version, and latest version of all outdated software. In addition, a comprehensive status report, containing all outdated, invalid and detected software, will also be mailed to the ULYSSIS members. ===Scanning=== During the last step, new software installations will be detected. For every active organisation and student union (kring/facultair overlegorgaan) account, the apache document roots are retrieved, and those directories are searched recursively to find signature files from specific software, as listed above. Those files do not contain personal information. If outdated software is found, and there is no entry in the database yet, the software location and version (among other information) is stored in the SQLite database. ==Stored Data== The following data is stored in the SQLite database: * The location of the CMS, plugin/extension or theme * The responsible organisation or student union (kring/facultair overlegorgaan) * The personal account e-mail address * The detected software version * The type and name of the software * The update URL for the software * The date the entry was added ==Ignored Paths== The CMS Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. 23cb5ec31ba82374beb43bd8fc3ce0e07f56a1c1 487 486 2017-09-07T19:12:16Z Yoa 30 wikitext text/x-wiki ==Introduction== Content Management Systems, or CMS's, are easy tools to set up a website without requiring much programming or configuration. However, as is common in a lot of popular and wide-spread software, bugs or errors in the code occur. These errors can be exploited by hackers to gain access to websites or databases connected to those CMS's. Whenever a new update for a CMS, or other popular software (MediaWiki, PhpBB) is released, those hackers will try to implement them as fast as possible in order to hack the most websites. This is why it's critical to update a CMS, plugins/themes, or any related software as soon as the update comes out. To help you facilitate this, we have created a tool to help you keep the most popular software up-to-date. Currently this feature is only active if you have an organisation or student union (kring/facultair overlegorgaan) account. ==I received an e-mail!== If you receive an e-mail from the CMS Version Checker, it's best you update the software mentioned in the e-mail as soon as possible. Make sure to download the latest public version, not just any newer version. It's also best to check if any other software you run is up-to-date: not all software is checked by the tool. (As seen below) ==Supported Software== * Drupal, Drupal Modules, Drupal Themes * Joomla (Joomla Plugins are not supported yet) * MediaWiki (MediaWiki Extensions and Themes are not supported yet) * PhpBB, PhpBB Plugins, PhpBB Styles * WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the CMS Version Checker performs the following steps: * Retrieve all outdated software and respective locations from a database, and check their version * Mail accounts using outdated software * Scan relevant files, detect supported software, and store in database ==Stored Data== The following data is stored in the SQLite database: * The location of the CMS, plugin/extension or theme * The responsible organisation or student union (kring/facultair overlegorgaan) * The personal account e-mail address * The detected software version * The type and name of the software * The update URL for the software * The date the entry was added ==Ignored Paths== The CMS Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. 708ba51d90e723cebf82f7a9f7017f30d81a1785 488 487 2017-09-07T20:17:19Z Bert 8 /* Stored Data */ wikitext text/x-wiki ==Introduction== Content Management Systems, or CMS's, are easy tools to set up a website without requiring much programming or configuration. However, as is common in a lot of popular and wide-spread software, bugs or errors in the code occur. These errors can be exploited by hackers to gain access to websites or databases connected to those CMS's. Whenever a new update for a CMS, or other popular software (MediaWiki, PhpBB) is released, those hackers will try to implement them as fast as possible in order to hack the most websites. This is why it's critical to update a CMS, plugins/themes, or any related software as soon as the update comes out. To help you facilitate this, we have created a tool to help you keep the most popular software up-to-date. Currently this feature is only active if you have an organisation or student union (kring/facultair overlegorgaan) account. ==I received an e-mail!== If you receive an e-mail from the CMS Version Checker, it's best you update the software mentioned in the e-mail as soon as possible. Make sure to download the latest public version, not just any newer version. It's also best to check if any other software you run is up-to-date: not all software is checked by the tool. (As seen below) ==Supported Software== * Drupal, Drupal Modules, Drupal Themes * Joomla (Joomla Plugins are not supported yet) * MediaWiki (MediaWiki Extensions and Themes are not supported yet) * PhpBB, PhpBB Plugins, PhpBB Styles * WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the CMS Version Checker performs the following steps: * Retrieve all outdated software and respective locations from a database, and check their version * Mail accounts using outdated software * Scan relevant files, detect supported software, and store in database ==Stored Data== The following data is stored in the database: * The location of the CMS, plugin/extension or theme * The responsible organisation or student union (kring/facultair overlegorgaan) * The personal account e-mail address * The detected software version * The type and name of the software * The update URL for the software * The date the entry was added ==Ignored Paths== The CMS Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. 805a1395d0f4d372512dee308e698a7585ad4323 493 488 2017-09-14T18:41:07Z Yoa 30 Yoa moved page [[CMS Version Checker]] to [[Software Version Checker]] wikitext text/x-wiki ==Introduction== Content Management Systems, or CMS's, are easy tools to set up a website without requiring much programming or configuration. However, as is common in a lot of popular and wide-spread software, bugs or errors in the code occur. These errors can be exploited by hackers to gain access to websites or databases connected to those CMS's. Whenever a new update for a CMS, or other popular software (MediaWiki, PhpBB) is released, those hackers will try to implement them as fast as possible in order to hack the most websites. This is why it's critical to update a CMS, plugins/themes, or any related software as soon as the update comes out. To help you facilitate this, we have created a tool to help you keep the most popular software up-to-date. Currently this feature is only active if you have an organisation or student union (kring/facultair overlegorgaan) account. ==I received an e-mail!== If you receive an e-mail from the CMS Version Checker, it's best you update the software mentioned in the e-mail as soon as possible. Make sure to download the latest public version, not just any newer version. It's also best to check if any other software you run is up-to-date: not all software is checked by the tool. (As seen below) ==Supported Software== * Drupal, Drupal Modules, Drupal Themes * Joomla (Joomla Plugins are not supported yet) * MediaWiki (MediaWiki Extensions and Themes are not supported yet) * PhpBB, PhpBB Plugins, PhpBB Styles * WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the CMS Version Checker performs the following steps: * Retrieve all outdated software and respective locations from a database, and check their version * Mail accounts using outdated software * Scan relevant files, detect supported software, and store in database ==Stored Data== The following data is stored in the database: * The location of the CMS, plugin/extension or theme * The responsible organisation or student union (kring/facultair overlegorgaan) * The personal account e-mail address * The detected software version * The type and name of the software * The update URL for the software * The date the entry was added ==Ignored Paths== The CMS Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. 805a1395d0f4d372512dee308e698a7585ad4323 495 493 2017-09-14T18:41:36Z Yoa 30 /* I received an e-mail! */ wikitext text/x-wiki ==Introduction== Content Management Systems, or CMS's, are easy tools to set up a website without requiring much programming or configuration. However, as is common in a lot of popular and wide-spread software, bugs or errors in the code occur. These errors can be exploited by hackers to gain access to websites or databases connected to those CMS's. Whenever a new update for a CMS, or other popular software (MediaWiki, PhpBB) is released, those hackers will try to implement them as fast as possible in order to hack the most websites. This is why it's critical to update a CMS, plugins/themes, or any related software as soon as the update comes out. To help you facilitate this, we have created a tool to help you keep the most popular software up-to-date. Currently this feature is only active if you have an organisation or student union (kring/facultair overlegorgaan) account. ==I received an e-mail!== If you receive an e-mail from the Version Checker, it's best you update the software mentioned in the e-mail as soon as possible. Make sure to download the latest public version, not just any newer version. It's also best to check if any other software you run is up-to-date: not all software is checked by the tool. (As seen below) ==Supported Software== * Drupal, Drupal Modules, Drupal Themes * Joomla (Joomla Plugins are not supported yet) * MediaWiki (MediaWiki Extensions and Themes are not supported yet) * PhpBB, PhpBB Plugins, PhpBB Styles * WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the CMS Version Checker performs the following steps: * Retrieve all outdated software and respective locations from a database, and check their version * Mail accounts using outdated software * Scan relevant files, detect supported software, and store in database ==Stored Data== The following data is stored in the database: * The location of the CMS, plugin/extension or theme * The responsible organisation or student union (kring/facultair overlegorgaan) * The personal account e-mail address * The detected software version * The type and name of the software * The update URL for the software * The date the entry was added ==Ignored Paths== The CMS Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. f4c3fa7a95d4fb150fe4e00dfe22a2b548c60f4c 496 495 2017-09-14T18:41:46Z Yoa 30 /* Ignored Paths */ wikitext text/x-wiki ==Introduction== Content Management Systems, or CMS's, are easy tools to set up a website without requiring much programming or configuration. However, as is common in a lot of popular and wide-spread software, bugs or errors in the code occur. These errors can be exploited by hackers to gain access to websites or databases connected to those CMS's. Whenever a new update for a CMS, or other popular software (MediaWiki, PhpBB) is released, those hackers will try to implement them as fast as possible in order to hack the most websites. This is why it's critical to update a CMS, plugins/themes, or any related software as soon as the update comes out. To help you facilitate this, we have created a tool to help you keep the most popular software up-to-date. Currently this feature is only active if you have an organisation or student union (kring/facultair overlegorgaan) account. ==I received an e-mail!== If you receive an e-mail from the Version Checker, it's best you update the software mentioned in the e-mail as soon as possible. Make sure to download the latest public version, not just any newer version. It's also best to check if any other software you run is up-to-date: not all software is checked by the tool. (As seen below) ==Supported Software== * Drupal, Drupal Modules, Drupal Themes * Joomla (Joomla Plugins are not supported yet) * MediaWiki (MediaWiki Extensions and Themes are not supported yet) * PhpBB, PhpBB Plugins, PhpBB Styles * WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the CMS Version Checker performs the following steps: * Retrieve all outdated software and respective locations from a database, and check their version * Mail accounts using outdated software * Scan relevant files, detect supported software, and store in database ==Stored Data== The following data is stored in the database: * The location of the CMS, plugin/extension or theme * The responsible organisation or student union (kring/facultair overlegorgaan) * The personal account e-mail address * The detected software version * The type and name of the software * The update URL for the software * The date the entry was added ==Ignored Paths== The Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. 69cd7be29456f2d8c2410e9643d187ec20bbe576 497 496 2017-09-14T18:41:53Z Yoa 30 /* Operation */ wikitext text/x-wiki ==Introduction== Content Management Systems, or CMS's, are easy tools to set up a website without requiring much programming or configuration. However, as is common in a lot of popular and wide-spread software, bugs or errors in the code occur. These errors can be exploited by hackers to gain access to websites or databases connected to those CMS's. Whenever a new update for a CMS, or other popular software (MediaWiki, PhpBB) is released, those hackers will try to implement them as fast as possible in order to hack the most websites. This is why it's critical to update a CMS, plugins/themes, or any related software as soon as the update comes out. To help you facilitate this, we have created a tool to help you keep the most popular software up-to-date. Currently this feature is only active if you have an organisation or student union (kring/facultair overlegorgaan) account. ==I received an e-mail!== If you receive an e-mail from the Version Checker, it's best you update the software mentioned in the e-mail as soon as possible. Make sure to download the latest public version, not just any newer version. It's also best to check if any other software you run is up-to-date: not all software is checked by the tool. (As seen below) ==Supported Software== * Drupal, Drupal Modules, Drupal Themes * Joomla (Joomla Plugins are not supported yet) * MediaWiki (MediaWiki Extensions and Themes are not supported yet) * PhpBB, PhpBB Plugins, PhpBB Styles * WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the Version Checker performs the following steps: * Retrieve all outdated software and respective locations from a database, and check their version * Mail accounts using outdated software * Scan relevant files, detect supported software, and store in database ==Stored Data== The following data is stored in the database: * The location of the CMS, plugin/extension or theme * The responsible organisation or student union (kring/facultair overlegorgaan) * The personal account e-mail address * The detected software version * The type and name of the software * The update URL for the software * The date the entry was added ==Ignored Paths== The Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. 3d34982fe6eb35549698cd83c9d7d158db9948b7 0 13 489 226 2017-09-10T04:18:58Z Bert 8 /* Guest users */ wikitext text/x-wiki If you want to use [http://git-scm.com/ git] for version control to work privately on personal projects, or collaborate with others on projects, you can use GitLab for central repositories, and for tracking bugs. = Accessing GitLab = You can access our GitLab server at https://gitlab.ulyssis.org. You can log in with your standard ULYSSIS username and password. = Getting started with Git = If you want to get acquainted with git, these are good free resources: * [https://try.github.io Try Git]: an interactive introduction to git * [http://git-scm.com/book Pro Git]: a book that you can read for free online * [http://git-scm.com/docs The official Git reference documentation] = Guest users = Sadly, we do not provide automated guest user support for GitLab yet, as we do for Subversion. If not everyone who works on your project has their own ULYSSIS account, you can request a Gitlab guest account via email. You simply send an email with the guest account's username (which will be prefixed with an underscore), full name, KU Leuven uid (m/s/r/u number) and email address to ulyssis@ulyssis.org and we will create it. 01df18a2ed1d6cb3e4cad8d273b438d6ba944f8e 490 489 2017-09-10T04:20:02Z Bert 8 /* Guest users */ wikitext text/x-wiki If you want to use [http://git-scm.com/ git] for version control to work privately on personal projects, or collaborate with others on projects, you can use GitLab for central repositories, and for tracking bugs. = Accessing GitLab = You can access our GitLab server at https://gitlab.ulyssis.org. You can log in with your standard ULYSSIS username and password. = Getting started with Git = If you want to get acquainted with git, these are good free resources: * [https://try.github.io Try Git]: an interactive introduction to git * [http://git-scm.com/book Pro Git]: a book that you can read for free online * [http://git-scm.com/docs The official Git reference documentation] = Guest users = Sadly, we do not provide automated guest user support for GitLab yet, as we do for Subversion. If not everyone who works on your project has their own ULYSSIS account, you can request a Gitlab guest account via email. You simply send an email with the guest account's username (which will be prefixed with an underscore), full name, KU Leuven uid (m/s/r/u number) and email address to ulyssis@ulyssis.org and we will create it. Do keep in mind you bear full responsibility for all guests created for your account. 4b57ef559d3e858325942e8d422cdef317f8c3d9 0 97 494 2017-09-14T18:41:07Z Yoa 30 Yoa moved page [[CMS Version Checker]] to [[Software Version Checker]] wikitext text/x-wiki #REDIRECT [[Software Version Checker]] 0b636cae5d3afba117d9b28ab235b134cc5b3835 0 98 498 2017-09-18T14:07:52Z Yoa 30 Created page with "==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and cr..." wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First unzip the zip file in your <code><mediawiki root>/extensions/</code> directory. Then, add the following lines to your <code><mediawiki root>/LocalSettings.php</code>: <code> wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; </code> If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. [[File:Login.jpg]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account) 513fa1cd1f6421e154311825699949200ded35c6 500 498 2017-09-18T14:09:01Z Yoa 30 wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First unzip the zip file in your <code><mediawiki root>/extensions/</code> directory. Then, add the following lines to your <code><mediawiki root>/LocalSettings.php</code>: <code> wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; </code> If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account) eaf8d198bcede499b610afbbfaf9904c5c727dcd 502 500 2017-09-18T14:10:52Z Yoa 30 wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First unzip the zip file in your <code><mediawiki root>/extensions/</code> directory. Then, add the following lines to your <code><mediawiki root>/LocalSettings.php</code>: <code> wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; </code> If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account) You should select [[File:CreateAccount.png]] c15d83d944e0cc4c53a1f9fdf8c8e22662c19ccc 503 502 2017-09-18T14:11:09Z Yoa 30 wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First unzip the zip file in your <code><mediawiki root>/extensions/</code> directory. Then, add the following lines to your <code><mediawiki root>/LocalSettings.php</code>: <code> wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; </code> If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account) You should select [[File:CreateAccount.png]] 07f64e85a3dfe2ba1f0da19f32aff131a006ff71 504 503 2017-09-18T14:11:45Z Yoa 30 wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First unzip the zip file in your <code><mediawiki root>/extensions/</code> directory. Then, add the following lines to your <code><mediawiki root>/LocalSettings.php</code>: <code> wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; </code> If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account) You should select [[File:CreateAccount.png]] 59d9c77e038a84a848d0bce973910a38ca3dd61a 505 504 2017-09-18T14:12:06Z Yoa 30 wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First unzip the zip file in your <code><mediawiki root>/extensions/</code> directory. Then, add the following lines to your <code><mediawiki root>/LocalSettings.php</code>: <code> wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; </code> If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account) You should select [[File:CreateAccount.png]] e92b5ac74160f8af285e08f901b99db690c76c0f 6 100 501 2017-09-18T14:10:08Z Yoa 30 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 98 506 505 2017-09-18T14:12:43Z Yoa 30 wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First unzip the zip file in your <code><mediawiki root>/extensions/</code> directory. Then, add the following lines to your <code><mediawiki root>/LocalSettings.php</code>: <code> wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; </code> If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account) You should select "Use a temporary random password and email it to the specified email address". [[File:CreateAccount.png]] 06fa46fcdb1a3fa0310f36b067dadafd5145ab7a 507 506 2017-09-18T14:13:00Z Yoa 30 wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First unzip the zip file in your <code><mediawiki root>/extensions/</code> directory. Then, add the following lines to your <code><mediawiki root>/LocalSettings.php</code>: <code> wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; </code> If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account) You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 4f35a2d7670e4028cee28b64c401ac237153a99e 508 507 2017-09-18T14:17:56Z Yoa 30 /* Creating accounts */ wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First unzip the zip file in your <code><mediawiki root>/extensions/</code> directory. Then, add the following lines to your <code><mediawiki root>/LocalSettings.php</code>: <code> wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; </code> If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 233c0d5dac8df3a55c86998748d31ea36940be96 509 508 2017-09-18T14:21:42Z Bert 8 wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First unzip the zip file in your <code><mediawiki root>/extensions/</code> directory. Then, add the following lines to your <code><mediawiki root>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 824ee631216982ca96e1ecbefb31bff8a2e0254e 510 509 2017-09-18T14:21:52Z Bert 8 /* Installation */ wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First unzip the zip file in your <code><mediawiki root>/extensions/</code> directory. Then, add the following lines to your <code><mediawiki root>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 4468dfc82bf4619e3cb26a5508976a1b7801a930 511 510 2017-09-18T14:22:10Z Bert 8 wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First unzip the zip file in your <code><mediawiki root>/extensions/</code> directory. Then, add the following lines to your <code><mediawiki root>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 676b8da0a8af83957acdf918392e673e5eb49a74 512 511 2017-09-18T14:23:08Z Bert 8 wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First unzip the zip file in your <code><mediawiki root>/extensions/</code> directory. Then, add the following lines to your <code><mediawiki root>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the plugin. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 4f3486961c23b40b757e0a54bd3ee1a4128f3fc9 514 512 2017-09-25T22:18:23Z Yoa 30 /* Installation */ wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First unzip the zip file in your <code><mediawiki root>/extensions/</code> directory. Then, add the following lines to your <code><mediawiki root>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 6fdf29b38f933e6b2c0186e1947619c351c6de08 530 514 2017-11-08T20:31:17Z Yoa 30 wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Then, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 7e5be7d174e2a72e55c8da86e0f649be128653d3 531 530 2017-11-08T20:32:00Z Yoa 30 Yoa moved page [[Securing MediaWiki using Shibboleth]] to [[Securing MediaWiki using Centrale KU Leuven Login]]: domme mensen weten niet wat shibboleth is wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Then, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 7e5be7d174e2a72e55c8da86e0f649be128653d3 536 531 2017-11-23T22:35:20Z Yoa 30 wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest]. Make sure to click the `MediaWikiShibboleth.zip` download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] b6c3e7a70cb21d6c209bc18e57dd37fc5cce421c 537 536 2017-11-23T22:35:46Z Yoa 30 wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 3dda677e092443c8350bdbf623e675adc52188b8 538 537 2017-11-23T22:37:16Z Yoa 30 wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 57fc64fc122a6e7d4478a3ef582fe3c6f07da99b 0 78 513 417 2017-09-19T19:32:41Z Vincenttc 21 wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. # Set up agenda sync on KU Loket ## Visit [http://kuloket.be/ KU Loket] ## Go to the '''Education & Students''' (Onderwijs & studenten) tab [[File:KULoket-Agenda-Step1.png|thumb|200px]] ## Click '''Agenda sync''' ## Click '''Configure agenda''' (Agenda instellen) [[File:KULoket-Agenda-Step2.png|thumb|200px]] ## Change the switch '''Show schedule in my agenda''' (Toon uurrooster in mijn agenda) to '''On'''. [[File:KULoket-Agenda-Step3.png|thumb|200px]] You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (Agenda) # On the top right (below the menu bar), click the '''Share''' (Delen) button. A side-panel appears. # Enter a non-KU Leuven email address in the '''Share with''' (Delen met) textfield. After filling the email address, press the enter key. # Make sure '''Full details''' (Volledige informatie) is selected in the dropdown next to your email address # Click the '''Send''' (Verzenden) button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> 0eede3605936463f1a5a3250ec374f7c775fcd01 0 30 515 122 2017-09-27T05:39:40Z Lars 26 wikitext text/x-wiki 3 weeks before your account expires you will start receiving emails reminding you to renew your account. These will continue until your account expires. To renew your account you visit https://ucc.ulyssis.org/accounts and, while making sure you are '''not''' logged into a ULYSSIS Account, login using the Central KU Leuven Login and select your account (the renewal option will only be available if the account is in the renewal period of 3 weeks or has expired already). * Select your account option, you are free to upgrade your personal account to a higher tier now * Verify your personal information (in case of errors please contact ULYSSIS) * Accept the terms of use * Confirm your order * An email will be sent to your KU Leuven emailaddress to confirm your order and with a request for payment. * As soon as we have received and processed your payment your account will get renewed, you will receive a notification. * If you are running late with your payment and you wish to prevent your account from getting expired you can contact ULYSSIS with a screenshot or scan that confirms the payment, we will then temporarily renew your account and verify that the money arrives within the near future. e28bb0591b853cdcb5bc83e8a9632080f09b4f7c 0 73 516 472 2017-10-08T12:42:58Z Tim 25 wikitext text/x-wiki We often get the question at our LaTeX workshop how to properly install the kulemt package. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading "kulemt-tds.zip" from ftp://ftp.esat.kuleuven.be/latex/kulemt/. == One-time use == Most people will only use this package once, for their master thesis. In this case, you can just put the necessary files in the same folder as your LaTeX project. The easiest way to accomplish this, is to unzip the downloaded file and in the unzipped folder, navigate to the directory "tex/latex/kulemt". Here, copy the following files to the same directory as your LaTeX project: kulemt.cfg, kulemt.cls, kulemtx.sty, logokul.eps and logokuleng.eps. == User-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package in a central location where LaTeX can find it autonomously. When using TeXLive, as we recommend, this involves a bit more work. First, you should find where to install the packages for your user. This is called the TEXMFHOME. The default location of this folder is: * For Windows: the folder "texmf" in your %USERPROFILE% (C:\Users\YourUsername for Windows Vista and up). * For Linux: "~/texmf" * For OS X/macOS: "~/Library/texmf" It is possible that this folder needs to be created first. From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location (note: the directory itself, not only its contents). If this does not work, or if you want to check the directory first, please refer to the section [[#Finding the TEXMFHOME]] at the bottom of this document. For a more technical overview, you can follow the general guidelines provided by the department: ftp://ftp.esat.kuleuven.be/latex/kulemt/README.html. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English}, % in case of a Dutch master udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> == Finding the TEXMFHOME == In case the default location for the TEXMFHOME as stated above does not work, you can find the correct directory through command-line. In Linux and macOS, look for an app called "Terminal". In Windows, search for "cmd" using the start menu. The program has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf If you have found this folder, copy the entire "tex" directory from the extracted kulemt-tds.zip to this location, as stated before. Create the folder if needed. == Troubleshooting == The kulemt package requires the memoir package. Make sure you have this package. We recommend installing the texlive-full package on Ubuntu. When you use the installer from [ftp://ftp.ulyssis.org/LaTeX-Workshop/installers/ our FTP server] for Windows or OS X/macOS, you will automatically have the entire LaTeX suite. 08ddf52246194b78419a134f0e698d7576fc0a85 0 45 517 198 2017-10-16T12:22:19Z Bert 8 wikitext text/x-wiki You can always reset your password. In order to reset your password, visit [https://ucc.ulyssis.org/ucc/passwd/reset UCC]. Please keep in mind you need to be logged out of UCC to be able to reset your password. * Fill in your username and click on 'reset password' * Then you will have to sign in using your KULeuven credentials to make sure it is really you * Choose another password * Click on reset password * Try to log in at UCC with your new password Be wise and pick a [https://xkcd.com/936/ strong and easy to remember password]. 7b6529ae82559a01aa62f2897d05ffd2f18d4b64 0 96 518 497 2017-10-23T10:14:14Z Yoa 30 /* Stored Data */ wikitext text/x-wiki ==Introduction== Content Management Systems, or CMS's, are easy tools to set up a website without requiring much programming or configuration. However, as is common in a lot of popular and wide-spread software, bugs or errors in the code occur. These errors can be exploited by hackers to gain access to websites or databases connected to those CMS's. Whenever a new update for a CMS, or other popular software (MediaWiki, PhpBB) is released, those hackers will try to implement them as fast as possible in order to hack the most websites. This is why it's critical to update a CMS, plugins/themes, or any related software as soon as the update comes out. To help you facilitate this, we have created a tool to help you keep the most popular software up-to-date. Currently this feature is only active if you have an organisation or student union (kring/facultair overlegorgaan) account. ==I received an e-mail!== If you receive an e-mail from the Version Checker, it's best you update the software mentioned in the e-mail as soon as possible. Make sure to download the latest public version, not just any newer version. It's also best to check if any other software you run is up-to-date: not all software is checked by the tool. (As seen below) ==Supported Software== * Drupal, Drupal Modules, Drupal Themes * Joomla (Joomla Plugins are not supported yet) * MediaWiki (MediaWiki Extensions and Themes are not supported yet) * PhpBB, PhpBB Plugins, PhpBB Styles * WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the Version Checker performs the following steps: * Retrieve all outdated software and respective locations from a database, and check their version * Mail accounts using outdated software * Scan relevant files, detect supported software, and store in database ==Stored Data== The following data is stored in the database: * The location of the CMS, plugin/extension or theme * The responsible organisation or student union (kring/facultair overlegorgaan) * The detected software version * The type and name of the software * The update URL for the software * The date the entry was added ==Ignored Paths== The Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. 96ddf6f5cbd8a26b252b73086ee26349eeab9769 519 518 2017-10-23T10:18:06Z Yoa 30 wikitext text/x-wiki ==Introduction== Content Management Systems, or CMS's, are easy tools to set up a website without requiring much programming or configuration. However, as is common in a lot of popular and wide-spread software, bugs or errors in the code occur. These errors can be exploited by hackers to gain access to websites or databases connected to those CMS's. Whenever a new update for a CMS, or other popular software (MediaWiki, PhpBB) is released, those hackers will try to implement them as fast as possible in order to hack the most websites. This is why it's critical to update a CMS, plugins/themes, or any related software as soon as the update comes out. To help you facilitate this, we have created a tool to help you keep the most popular software up-to-date. Currently this feature is only active if you have an organisation or student union (kring/facultair overlegorgaan) account. ==I received an e-mail!== If you receive an e-mail from the Version Checker, it's best you update the software mentioned in the e-mail as soon as possible. Make sure to download the latest public version, not just any newer version. It's also best to check if any other software you run is up-to-date: not all software is checked by the tool. (As seen below) ==Supported Software== * Drupal, Drupal Modules, Drupal Themes * Joomla (Joomla Plugins are not supported yet) * MediaWiki (MediaWiki Extensions and Themes are not supported yet) * PhpBB, PhpBB Plugins, PhpBB Styles * WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the Version Checker performs the following steps: * Retrieve all outdated software and respective locations from a database, and check their version * Mail accounts using outdated software * Scan relevant files, detect supported software, and store in database ==Stored Data== The following data is stored in the database: * The location of the CMS, plugin/extension or theme * The responsible organisation or student union (kring/facultair overlegorgaan) * The detected software version * The type and name of the software * The update URL for the software * The date the entry was added ==Ignored Paths== The Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. ==Ignored Organisations/Student Unions== In addition to the ignored paths feature, the Version Checker can also ignore specific Organisations or Student Unions entirely. This feature is possible on request, but only after extensive deliberation with ulyssis. Enabling this feature also carries possible consequences: no more mails about outdated software, ever (unless enabled on request), no support if/when your account gets hacked (the account will be expired immediately)... 2d7c737eec33263d2a5bbae3c75f40fada5c41e4 520 519 2017-10-23T10:18:28Z Yoa 30 /* Ignored Organisations/Student Unions */ wikitext text/x-wiki ==Introduction== Content Management Systems, or CMS's, are easy tools to set up a website without requiring much programming or configuration. However, as is common in a lot of popular and wide-spread software, bugs or errors in the code occur. These errors can be exploited by hackers to gain access to websites or databases connected to those CMS's. Whenever a new update for a CMS, or other popular software (MediaWiki, PhpBB) is released, those hackers will try to implement them as fast as possible in order to hack the most websites. This is why it's critical to update a CMS, plugins/themes, or any related software as soon as the update comes out. To help you facilitate this, we have created a tool to help you keep the most popular software up-to-date. Currently this feature is only active if you have an organisation or student union (kring/facultair overlegorgaan) account. ==I received an e-mail!== If you receive an e-mail from the Version Checker, it's best you update the software mentioned in the e-mail as soon as possible. Make sure to download the latest public version, not just any newer version. It's also best to check if any other software you run is up-to-date: not all software is checked by the tool. (As seen below) ==Supported Software== * Drupal, Drupal Modules, Drupal Themes * Joomla (Joomla Plugins are not supported yet) * MediaWiki (MediaWiki Extensions and Themes are not supported yet) * PhpBB, PhpBB Plugins, PhpBB Styles * WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the Version Checker performs the following steps: * Retrieve all outdated software and respective locations from a database, and check their version * Mail accounts using outdated software * Scan relevant files, detect supported software, and store in database ==Stored Data== The following data is stored in the database: * The location of the CMS, plugin/extension or theme * The responsible organisation or student union (kring/facultair overlegorgaan) * The detected software version * The type and name of the software * The update URL for the software * The date the entry was added ==Ignored Paths== The Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. ==Ignored Organisations/Student Unions== In addition to the ignored paths feature, the Version Checker can also ignore specific Organisations or Student Unions entirely. This feature is possible on request, but only after extensive deliberation with ULYSSIS. Enabling this feature also carries possible consequences: no more mails about outdated software, ever (unless enabled on request), no support if/when your account gets hacked (the account will be expired immediately)... 57fa0dba76a955d3f75efa1d47530a7dcbc9520d 0 20 521 249 2017-11-06T01:45:07Z Kevin 33 Beetje degelijke tekst maken ipv google translate wikitext text/x-wiki ==Installing wordpress on our servers is definitely easy== First you will need to download Wordpress from their website, https://wordpress.org. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. The files that you've extracted will need to be moved to your www-directory on your shell account. You can do this by copying them there using Filezilla or any other FTP client. After you've copied those files to your www-directory, you'll have to go to your account on *your username here*.ulyssis.be. You will then receive a notification telling you your <code>wp-config.php</code> has to be created. The easiest way to do this is by following the wizard, so you can click on "Create a configuration file". Go through to the wizard until it prompts you for your database credentials: *'''Database Name:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll have to create it here. The default database is: "username_username". *'''Username:''' The name you used during the creation of your database account. *'''Password:''' The password you used during the creation of your database account. *'''Database Host:''' This is <code>mysql.ulyssis.org</code> * You don't need to change the last field. After that you can proceed in the wizard where you can fill in some last few details. By then the wizard will do the rest and, congratulations, you have installed Wordpress. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site then you the create a new folder in your homedir from your shell account. You need a new virtual host, send us an email and we will create one for you. After your new virtual host has been configured, you need to do al the same steps as for a regular wordpress installation. You could also use the Wordpress [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about the multisite option [https://wordpress.org/support/forum/multisite here]. 4edbafd5b46fccda5a14205a0e206fc253943364 522 521 2017-11-06T01:46:20Z Kevin 33 /* Installing wordpress on our servers is definitely easy */ wikitext text/x-wiki ==How to install Wordpress== First you will need to download Wordpress from their website, https://wordpress.org. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. The files that you've extracted will need to be moved to your www-directory on your shell account. You can do this by copying them there using Filezilla or any other FTP client. After you've copied those files to your www-directory, you'll have to go to your account on *your username here*.ulyssis.be. You will then receive a notification telling you your <code>wp-config.php</code> has to be created. The easiest way to do this is by following the wizard, so you can click on "Create a configuration file". Go through to the wizard until it prompts you for your database credentials: *'''Database Name:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll have to create it here. The default database is: "username_username". *'''Username:''' The name you used during the creation of your database account. *'''Password:''' The password you used during the creation of your database account. *'''Database Host:''' This is <code>mysql.ulyssis.org</code> * You don't need to change the last field. After that you can proceed in the wizard where you can fill in some last few details. By then the wizard will do the rest and, congratulations, you have installed Wordpress. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site then you the create a new folder in your homedir from your shell account. You need a new virtual host, send us an email and we will create one for you. After your new virtual host has been configured, you need to do al the same steps as for a regular wordpress installation. You could also use the Wordpress [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about the multisite option [https://wordpress.org/support/forum/multisite here]. 0563daa475e2fca68008b3d07f1bb25f43701e71 523 522 2017-11-06T02:04:02Z Kevin 33 wat is degelijk engels¿? wikitext text/x-wiki ==How to install Wordpress== First you will need to download Wordpress from their website, https://wordpress.org. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. The files that you've extracted will need to be moved to your www-directory on your shell account. You can do this by copying them there using Filezilla or any other FTP client. After you've copied those files to your www-directory, you'll have to go to your account on *your username here*.ulyssis.be. You will then receive a notification telling you your <code>wp-config.php</code> has to be created. The easiest way to do this is by following the wizard, so you can click on "Create a configuration file". Go through to the wizard until it prompts you for your database credentials: *'''Database Name:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll have to create it here. The default database is: "username_username". *'''Username:''' The name you used during the creation of your database account. *'''Password:''' The password you used during the creation of your database account. *'''Database Host:''' This is <code>mysql.ulyssis.org</code> * You don't need to change the last field. After that you can proceed in the wizard where you can fill in some last few details. By then the wizard will do the rest and, congratulations, you have installed Wordpress. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you will need to create a new folder in your www-directory on your shell account. Then you'll need a virtual host for this folder, so you'll have to send us an email asking for this. After your new virtual host has been configured, you will need to do the same steps that you would need to do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about it [https://wordpress.org/support/forum/multisite here]. 0bc62a2d1d5c5fe73e67ee4fab6cc0297b7f4cdb 524 523 2017-11-07T20:13:09Z Kevin 33 /* How to install Wordpress */ wikitext text/x-wiki ==How to install Wordpress== First you will need to download Wordpress from their website, https://wordpress.org. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. The files that you've extracted will need to be moved to your www-directory on your shell account. You can do this by copying them there using Filezilla or any other FTP client. After you've copied those files to your www-directory, you'll have to go to your account on *your username here*.ulyssis.be. You will then receive a notification telling you your <code>wp-config.php</code> has to be created. The easiest way to do this is by following the wizard, so you can click on "Create a configuration file". Go through to the wizard until it prompts you for your database configuration: *'''Database Name:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll have to create it here. The default database is: "username_username". *'''Username:''' The name you used during the creation of your database account. *'''Password:''' The password you used during the creation of your database account. *'''Database Host:''' This is <code>mysql.ulyssis.org</code> * You don't need to change the last field. After that you can proceed in the wizard where you can fill in some last few details. By then the wizard will do the rest and, congratulations, you have installed Wordpress. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you will need to create a new folder in your www-directory on your shell account. Then you'll need a virtual host for this folder, so you'll have to send us an email asking for this. After your new virtual host has been configured, you will need to do the same steps that you would need to do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about it [https://wordpress.org/support/forum/multisite here]. 61ea4f620851422e152a4a4d96049b8cbc080edb 525 524 2017-11-08T20:12:01Z Kevin 33 /* How to install Wordpress */ wikitext text/x-wiki ==How to install Wordpress for your account== First you will need to download Wordpress from their website, https://wordpress.org. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. The files that you've extracted will need to be moved to your www-directory on your shell account. You can do this by copying them there using Filezilla or any other FTP client. After you've copied those files to your www-directory, you'll have to go to your account on *your username here*.ulyssis.be. You will then receive a notification telling you your <code>wp-config.php</code> has to be created. The easiest way to do this is by following the wizard, so you can click on "Create a configuration file". Go through to the wizard until it prompts you for your database configuration: *'''Database Name:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll have to create it here. The default database is: "username_username". *'''Username:''' The name you used during the creation of your database account. *'''Password:''' The password you used during the creation of your database account. *'''Database Host:''' This is <code>mysql.ulyssis.org</code> * You don't need to change the last field. After that you can proceed in the wizard where you can fill in some last few details. By then the wizard will do the rest and, congratulations, you have installed Wordpress. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you will need to create a new folder in your www-directory on your shell account. Then you'll need a virtual host for this folder, so you'll have to send us an email asking for this. After your new virtual host has been configured, you will need to do the same steps that you would need to do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about it [https://wordpress.org/support/forum/multisite here]. 0e5828c9714ddff72a68838efa533abdf288b950 533 525 2017-11-08T20:49:31Z Kevin 33 /* How to install Wordpress for your account */ wikitext text/x-wiki ==How to install Wordpress for your account== First you will need to download Wordpress from their website, https://wordpress.org. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. The files that you've extracted will need to be moved to your www-directory on your shell account. You can do this by copying them there using Filezilla or any other FTP client. After you've copied those files to your www-directory, you'll have to go to your account on *your username here*.ulyssis.be. You will then receive a notification telling you your <code>wp-config.php</code> has to be created. The easiest way to do this is by following the wizard, so you can click on "Create a configuration file". Go through to the wizard until it prompts you for your database configuration: *'''Database Name:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll have to create it here. The default database is: "username_username". *'''Username:''' The name you used during the creation of your database account. *'''Password:''' The password you used during the creation of your database account. *'''Database Host:''' This is <code>mysql.ulyssis.org</code> or <code>postgresql.ulyssis.org</code>. It depends on whether you want to use a MySQL or PostgreSQL database. * You don't need to change the last field. After that you can proceed in the wizard where you can fill in some last few details. By then the wizard will do the rest and, congratulations, you have installed Wordpress. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you will need to create a new folder in your www-directory on your shell account. Then you'll need a virtual host for this folder, so you'll have to send us an email asking for this. After your new virtual host has been configured, you will need to do the same steps that you would need to do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about it [https://wordpress.org/support/forum/multisite here]. c64dd47c64d596a7b7302cdb6a93909e8f928219 0 50 526 250 2017-11-08T20:20:37Z Kevin 33 fix vuil engels wikitext text/x-wiki ==How to install Drupal for your account== First you will need to install Drupal from their website, http://drupal.org. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. The files that you've extracted will need to be moved to your www-directory on your shell account. You can do this by copying them there using Filezilla or any other FTP client. After you've copied those files to your www-directory, you'll have to go to your account on *your username here*.ulyssis.be. Click on the Drupal directory and the installer will start loading. First it will ask you to choose a language and after that a profile. If you do not know what profile to choose, you should choose the standard one. If the installer doesn't skip the ''Verify requiremen$ page, then you should just follow the steps described there. Finally the installer will ask you to set your database configuration: *'''Database name:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll$ *'''Database username:''' The name you used during the creation of your database account. *'''Database password:''' The password you used during the creation of your database account. *'''Database host:''' This is <code>mysql.ulyssis.org</code>. You will need to click on "Advanced op$ option. After that you can proceed in the wizard where you can fill in some last few details. By then the wizard will do the rest except for asking some basic questions about the site and, congratulations, you have installed Drupal. ==Setting up multiple instances of Drupal== If you want to have multiple instances of a Drupal site there are two options. The multiple instances can either share drupal code or be fully seperate. For fully seperate installs you can simply create a (sub)folder to store another copy of the drupal code in. You can then access it either from your default domain or have us attach another domain to it for you, more info about that on [[Adding domain names]] If you wish for multiple websites to share the same codebase it is easiest to use multiple domains. More information about how to set this up in your drupal is available in the drupal documentation: https://www.drupal.org/documentation/install/multi-site. As soon as you have made your preperations you can contact us about hooking up the domain name, more info about that on [[Adding domain names]] 91130f518a1340a7d32105cab8924b9a14a26012 527 526 2017-11-08T20:22:02Z Kevin 33 /* How to install Drupal for your account */ wikitext text/x-wiki ==How to install Drupal for your account== First you will need to install Drupal from their website, http://drupal.org. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. The files that you've extracted will need to be moved to your www-directory on your shell account. You can do this by copying them there using Filezilla or any other FTP client. After you've copied those files to your www-directory, you'll have to go to your account on *your username here*.ulyssis.be. Click on the Drupal directory and the installer will start loading. First it will ask you to choose a language and after that a profile. If you do not know what profile to choose, you should choose the standard one. If the installer doesn't skip the ''Verify requirements"" page, then you should just follow the steps described there. Finally the installer will ask you to set your database configuration: *'''Database name:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll have to create it here. The default database is: "username_username". *'''Database username:''' The name you used during the creation of your database account. *'''Database password:''' The password you used during the creation of your database account. *'''Database host:''' This is <code>mysql.ulyssis.org</code>. You will need to click on ''Advanced options'' to set this option. After that you can proceed in the wizard where you can fill in some last few details. By then the wizard will do the rest except for asking some basic questions about the site and, congratulations, you have installed Drupal. ==Setting up multiple instances of Drupal== If you want to have multiple instances of a Drupal site there are two options. The multiple instances can either share drupal code or be fully seperate. For fully seperate installs you can simply create a (sub)folder to store another copy of the drupal code in. You can then access it either from your default domain or have us attach another domain to it for you, more info about that on [[Adding domain names]] If you wish for multiple websites to share the same codebase it is easiest to use multiple domains. More information about how to set this up in your drupal is available in the drupal documentation: https://www.drupal.org/documentation/install/multi-site. As soon as you have made your preperations you can contact us about hooking up the domain name, more info about that on [[Adding domain names]] 74ecd17ec03b5edfa2f15b8af41e03da073e4a17 528 527 2017-11-08T20:22:20Z Kevin 33 /* How to install Drupal for your account */ wikitext text/x-wiki ==How to install Drupal for your account== First you will need to install Drupal from their website, http://drupal.org. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. The files that you've extracted will need to be moved to your www-directory on your shell account. You can do this by copying them there using Filezilla or any other FTP client. After you've copied those files to your www-directory, you'll have to go to your account on *your username here*.ulyssis.be. Click on the Drupal directory and the installer will start loading. First it will ask you to choose a language and after that a profile. If you do not know what profile to choose, you should choose the standard one. If the installer doesn't skip the ''Verify requirements'' page, then you should just follow the steps described there. Finally the installer will ask you to set your database configuration: *'''Database name:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll have to create it here. The default database is: "username_username". *'''Database username:''' The name you used during the creation of your database account. *'''Database password:''' The password you used during the creation of your database account. *'''Database host:''' This is <code>mysql.ulyssis.org</code>. You will need to click on ''Advanced options'' to set this option. After that you can proceed in the wizard where you can fill in some last few details. By then the wizard will do the rest except for asking some basic questions about the site and, congratulations, you have installed Drupal. ==Setting up multiple instances of Drupal== If you want to have multiple instances of a Drupal site there are two options. The multiple instances can either share drupal code or be fully seperate. For fully seperate installs you can simply create a (sub)folder to store another copy of the drupal code in. You can then access it either from your default domain or have us attach another domain to it for you, more info about that on [[Adding domain names]] If you wish for multiple websites to share the same codebase it is easiest to use multiple domains. More information about how to set this up in your drupal is available in the drupal documentation: https://www.drupal.org/documentation/install/multi-site. As soon as you have made your preperations you can contact us about hooking up the domain name, more info about that on [[Adding domain names]] 64ad71215db6c1c0aa642d805c0667af54f8afc1 529 528 2017-11-08T20:22:31Z Kevin 33 /* How to install Drupal for your account */ wikitext text/x-wiki ==How to install Drupal for your account== First you will need to install Drupal from their website, http://drupal.org. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. The files that you've extracted will need to be moved to your www-directory on your shell account. You can do this by copying them there using Filezilla or any other FTP client. After you've copied those files to your www-directory, you'll have to go to your account on *your username here*.ulyssis.be. Click on the Drupal directory and the installer will start loading. First it will ask you to choose a language and after that a profile. If you do not know what profile to choose, you should choose the standard one. If the installer doesn't skip the ''Verify requirements'' page, then you should just follow the steps described there. Finally the installer will ask you to set your database configuration: *'''Database name:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll have to create it here. The default database is: "username_username". *'''Database username:''' The name you used during the creation of your database account. *'''Database password:''' The password you used during the creation of your database account. *'''Database host:''' This is <code>mysql.ulyssis.org</code>. You will need to click on ''Advanced options'' to set this option. After that you can proceed in the wizard where you can fill in some last few details. By then the wizard will do the rest except for asking some basic questions about the site and, congratulations, you have installed Drupal. ==Setting up multiple instances of Drupal== If you want to have multiple instances of a Drupal site there are two options. The multiple instances can either share drupal code or be fully seperate. For fully seperate installs you can simply create a (sub)folder to store another copy of the drupal code in. You can then access it either from your default domain or have us attach another domain to it for you, more info about that on [[Adding domain names]] If you wish for multiple websites to share the same codebase it is easiest to use multiple domains. More information about how to set this up in your drupal is available in the drupal documentation: https://www.drupal.org/documentation/install/multi-site. As soon as you have made your preperations you can contact us about hooking up the domain name, more info about that on [[Adding domain names]] 8a27c0c9b17376fe35b7d594c1a01d9a122bf7b9 0 101 532 2017-11-08T20:32:00Z Yoa 30 Yoa moved page [[Securing MediaWiki using Shibboleth]] to [[Securing MediaWiki using Centrale KU Leuven Login]]: domme mensen weten niet wat shibboleth is wikitext text/x-wiki #REDIRECT [[Securing MediaWiki using Centrale KU Leuven Login]] 23622964a83be74ec305b56602a221c361b53e67 0 33 534 221 2017-11-20T17:45:34Z Yoa 30 /* How to request */ wikitext text/x-wiki Shibboleth is the software powering the Central KU Leuven Login. It's a piece of software used by many universities to supply identification and access management. ULYSSIS works together with ICTS to supply limited access to Shibboleth. We are however only able to supply Shibboleth to those approved by ICTS. In practice all faculty unions will be granted access if they can prove they have the technical ability to use Shibboleth in a safe and privacy friendly way. For other organisations it can be more difficult to get access, therefore it is best to write an extensive explenation of what you plan to do with Shibboleth, why your organisation requires it, what your organisation does, and other relevant information. We will then contact ICTS with your request. == How to request == To request Shibboleth access, you first need to make sure the domain you wish to use Shibboleth on has valid SSL certificates. Lately ICTS has been pushing that all traffic to the website is already over HTTPS before Shibboleth is issued. For more info you can check [[Getting SSL]] If you have SSL set up you need to send an email to request Shibboleth to ulyssis@ulyssis.org. The email must contain the following info: * What domain you wish to use Shibboleth on (this must be a single domain, so keep subdomains and www in mind) * What you will be using Shibboleth for and in general what your application will do. This explenation is required by ICTS. If you fail to convince them they will not grant your domain access. * What attributes you wish to use and what you will do with them (and whether you will store them). You can find the list of attributes on https://admin.kuleuven.be/icts/services/aai/attributes * Explicitly state you grant ULYSSIS permission to edit the .htaccess file to be able to export the required Shibboleth Metadata * If you are not a recognised faculty union you will need to include an extra motivation why you require Shibboleth (as noted above) If your application is complete and correct we will file a formal request. We will of course notify you of ICTS' response. == Deploying Shibboleth == After you have been granted access you can soon start using Shibboleth. The first step is to add the following lines to your .htaccess ShibDisable Off AuthType Shibboleth require shibboleth ShibRequireSession off We disable certain features of Shibboleth here because it will otherwise interfere with any other HTTP-auth options you might be using. Now that you have added this information to .htaccess you are able to serve requests to Shibboleth.sso, if your request is well-formed the sso will handle communication with the IdP (identity provider) of the KU Leuven. A login link follows the following syntax: https://[YOUR_HOSTNAME]/Shibboleth.sso/WAYF/kuleuven?target=[URLENCODED_RETURN_URL] And logout links: https://[YOUR_HOSTNAME]/Shibboleth.sso/Logout?return=[URLENCODED_DISPLAY_URL] It is important to note that on logout the user will stay on the KU Leuven's IdP-page and your link will only be displayed. The user will NOT be redirected (even though this is the normale behaviour according to the Shibboleth documentation). As soon as a user is logged in, his or hers attributes will be available to your application. Attributes are certain properties that an account may have and that supply further information about them. Some examples are: first name, last name, mail, student id. All of these will be available as HTTP headers. But keep in mind that apache might prefix those with REDIRECT_ multiple times (for example when mod_rewrite is used). For an overview of all attributes you can check out http://shib.kuleuven.be/secure/allAttributes More general information on the KU Leuvens implementation can be found on http://shib.kuleuven.be/ . But be aware of the fact that some of the documentation is very outdated (Most notably information about shib 1.3) 314547c1b84dfbf728de90fb714ad3d0cfd1b916 0 19 535 195 2017-11-21T23:20:50Z Operand 34 /* SMTP */ smtp.kuleuven.be werkt niet meer, dus vervangen door smtps.kuleuven.be wikitext text/x-wiki Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mail regularly, because all important information will be sent to this address. You can check your e-mail using the webmail or an email client of your own. ==Webmail== You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to enter the website. ==POP and IMAP access== You can access your ulyssis mail by POP or IMAP protocol. The configuration parameters are: * '''server''': <tt>mail.ulyssis.org</tt> * '''username''': ''your ULYSSIS username'' * '''password''': ''your ULYSSIS password'' * '''security''': SSL ==SMTP== ULYSSIS doesn't offer SMTP. Instead, you can use KULeuven's SMTP server: * '''server''': <tt>smtps.kuleuven.be</tt> * '''port''': 443 * '''username''': ''your student id'' * '''password''': ''your KULeuven password'' * '''security''': SSL 20d0dc1bfe860b8d88c6577e0ed73e05583289ba 0 6 539 71 2017-12-23T12:17:44Z Lars 26 /* Accessing MySQL from outside of our network */ wikitext text/x-wiki ==Creating a MySQL user== To use MySQL on your ULYSSIS account you first need to create a MySQL user on [https://ucc.ulyssis.org UCC]. In the MySQL section of the panel you will be suggested to click a link to create a user. Then fill in a password for the database user. It is highly recommended that this password differs from the password you use for your account. Then you just click ''Create user'' and you are ready to go. ==Creating a MySQL database== After creating a MySQL user, you can simple press ''Add database'' in [https://ucc.ulyssis.org UCC] and enter the name for your new database. It will automatically be prefixed by your username. ==Using MySQL for your website or application== Host: mysql.ulyssis.org Username: your account's username Password: the password you chose when you made the MySQL user Database: the database name you chose, prefixed by your username For example, if my username is foobar, I made a database called website and I were to create a PHP website I would use something like: <syntaxhighlight lang="php">$db = new mysqli('mysql.ulyssis.org', 'foobar', 'correct horse battery staple', 'foobar_website');</syntaxhighlight> or <syntaxhighlight lang="php">$db = new PDO('mysql:host=mysql.ulyssis.org;dbname=foobar_website', 'foobar', 'correct horse battery staple');</syntaxhighlight> ==Managing MySQL with PHPMyAdmin== Using your username and password you can easily manage your MySQL databases, tables and records on https://phpmyadmin.ulyssis.org ==Accessing MySQL from outside of our network== To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH-tunnel. In many mysql management tools this is already supported. On Linux, Mac OSX and other Unix-like Operating Systems it is also easily possible to use the following command to create a tunnel to a local port (in this case 3300) ssh -f username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N While this command is running, you can connect to the MySQL server with host 'localhost' and port '3300'. To terminate the port forwarding, press ctrl-C in the terminal. f9c4a8b5e4c701eefbe876f878baf1267b00cbe0 0 3 540 492 2018-01-21T02:13:11Z Bert 8 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2016]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] * [[Claiming a port]] </div><div style="width:45%;float:left"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Regular updates on a CMS]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Anti-spam policies]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 80918ae7cda24f98bea88d0c600cc7f6297e0929 549 540 2018-02-16T06:30:09Z Lars 26 /* Security & anti-spam */ Remove page with misinformation wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2016]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] * [[Claiming a port]] </div><div style="width:45%;float:left"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Anti-spam policies]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 1d2e6a9a6292df61369010db4e767b49d9f44e22 0 102 541 2018-01-21T02:35:16Z Bert 8 Created page with "= Short answer = You can't, no use in trying. = Long answer = We do not permit aribitrary access to ports from our firewall and users are not supposed to try claiming ports...." wikitext text/x-wiki = Short answer = You can't, no use in trying. = Long answer = We do not permit aribitrary access to ports from our firewall and users are not supposed to try claiming ports. We offer classic webhosting, version control, and basic shell access. You are free to run applications, within bounds of what is reasonable, legal and ethical, on our shellservers. But they cannot claim arbitrary ports and you won't be able to access those ports anyway. Besides the fact that this is not a service we wish to offer, it's also very hard to do this in an orderly and secure way. We would have to assign users specific ports, and check those are used correctly, furthermore proxies would be necessary for production, as no one wants their visitors to be forced to enter port numbers. Beyond that, there are tons more practical issues that would have to be solved. In most cases, you are better off using FastCGI or CGI. We support both of these protocols, and have documentation and examples for our users on [[Using (Fast)CGI for non-PHP websites]]. If this is not what you are looking for, then we are afraid you will have to look at other services, such as VPSes, by commercial providers. ad6c62426541d9945a204ab30c47134584a41a7d 544 541 2018-01-21T02:39:37Z Bert 8 wikitext text/x-wiki == Short answer == You can't, no use in trying. == Long answer == We do not permit aribitrary access to ports from our firewall and users are not supposed to try claiming ports. We offer classic webhosting, version control, and basic shell access. You are free to run applications, within bounds of what is reasonable, legal and ethical, on our shellservers. But they cannot claim arbitrary ports and you won't be able to access those ports anyway. Besides the fact that this is not a service we wish to offer, it's also very hard to do this in an orderly and secure way. We would have to assign users specific ports, and check those are used correctly, furthermore proxies would be necessary for production, as no one wants their visitors to be forced to enter port numbers. Beyond that, there are tons more practical issues that would have to be solved. In most cases, you are better off using FastCGI or CGI. We support both of these protocols, and have documentation and examples for our users on [[Using (Fast)CGI for non-PHP websites]]. If this is not what you are looking for, then we are afraid you will have to look at other services, such as VPSes, by commercial providers. 0746d63ff3542fdc216d885f010c2043eead8ad1 0 103 542 2018-01-21T02:39:03Z Bert 8 Created page with "= I want to use a programming language, library or tool that is not installed =" wikitext text/x-wiki = I want to use a programming language, library or tool that is not installed = 3830def193f409705861c5d64af772d4823c1390 543 542 2018-01-21T02:39:28Z Bert 8 wikitext text/x-wiki == I want to use a programming language, library or tool that is not installed == cac1340a75ac58273472e21161d292a40bca5eba 545 543 2018-01-21T02:58:17Z Bert 8 wikitext text/x-wiki While most webhosting providers give you access to a few or even just one programming language and a set amount of libraries, ULYSSIS prefers to offer more flexibility. We hope to give our users the chance to experiment with different languages, libraries and tools. There are of course also limits to what is realistic for us to install. More on that below. == Using a programming language, library or tool that is not installed == If the package that you would like us to install is available in the software repository of our current operating system, then that is usually not a problem. We currently use Ubuntu on all our servers, specifically, we upgrade to the latest LTS every summer vacation following the release of a new one. You can verify which version we are running by executing "cat /etc/lsb-release" on one of our shellservers. After you have verified what version we are running, you can refer to [[https://packages.ubuntu.com/]] to check whether your package is available in that version of Ubuntu. If it is, then you can contact us by email on ulyssis@ulyssis.org which package or packages you would like to have installed, and what you will be using it for. You will most likely get a positive response. If your package is not in the repository, you will have to go for a [[Installing packages#Manual installation|Manual installation]] == Using a newer/different version == == Manual installation == ac76a5249e4075399e53819dde4932d5aad7e5fc 546 545 2018-01-21T02:58:31Z Bert 8 wikitext text/x-wiki While most webhosting providers give you access to a few or even just one programming language and a set amount of libraries, ULYSSIS prefers to offer more flexibility. We hope to give our users the chance to experiment with different languages, libraries and tools. There are of course also limits to what is realistic for us to install. More on that below. == Using a programming language, library or tool that is not installed == If the package that you would like us to install is available in the software repository of our current operating system, then that is usually not a problem. We currently use Ubuntu on all our servers, specifically, we upgrade to the latest LTS every summer vacation following the release of a new one. You can verify which version we are running by executing "cat /etc/lsb-release" on one of our shellservers. After you have verified what version we are running, you can refer to https://packages.ubuntu.com/ to check whether your package is available in that version of Ubuntu. If it is, then you can contact us by email on ulyssis@ulyssis.org which package or packages you would like to have installed, and what you will be using it for. You will most likely get a positive response. If your package is not in the repository, you will have to go for a [[Installing packages#Manual installation|Manual installation]] == Using a newer/different version == == Manual installation == 14ea8dd5518b39b4e68f9886d8b8811059654aaf 547 546 2018-01-21T03:09:47Z Bert 8 wikitext text/x-wiki While most webhosting providers give you access to a few or even just one programming language and a set amount of libraries, ULYSSIS prefers to offer more flexibility. We hope to give our users the chance to experiment with different languages, libraries and tools. There are of course also limits to what is realistic for us to install. More on that below. == Using a programming language, library or tool that is not installed == If the package that you would like us to install is available in the software repository of our current operating system, then that is usually not a problem. We currently use Ubuntu on all our servers, specifically, we upgrade to the latest LTS every summer vacation following the release of a new one. You can verify which version we are running by executing "cat /etc/lsb-release" on one of our shellservers. After you have verified what version we are running, you can refer to https://packages.ubuntu.com/ to check whether your package is available in that version of Ubuntu. If it is, then you can contact us by email on ulyssis@ulyssis.org which package or packages you would like to have installed, and what you will be using it for. You will most likely get a positive response. If your package is not in the repository, you will have to go for a [[Installing packages#Manual installation|Manual installation]]. == Using a newer/different version == As you can read in the section concerning the installation of new packages, we only offer the version available in the repository of the version of Ubuntu that we are running. In most cases, this means you will have to wait for a version upgrade with the next LTS release, or go for a [[Installing packages#Manual installation|Manual installation]]. However, there are some exceptions. Sometimes multiple version will be available in the repository, such as with Python 2 and 3, or Perl 5 and 6. In such cases, you can refer to the section above for instructions on how to request an installation. == Manual installation == If you want to install a piece of software that is not available in the repository or you wish to install another version, you can always install it manually onto your account. It is important to keep in mind that ULYSSIS will not support manually installed software, and that you are fully responsible for the security of this software. You are free to ask us questions, but we will most probably not help you. If you do require a manual installation of specific software, we expect you to be capable of maintaining it as well. The way you install your software rewall differs depending on the software. You could be using tools such as pip, gem or npm to install to a directory in your home folder, you could be using a virtual environment, or you could be compiling your own binary. We suggest you look at the documentation of the software you're using very thoroughly, and make sure you are comfortable with what you are doing and aware of your responsibilities. After installing your software locally onto your account, you will probably want to add an alias in your dotfiles (for example .profile or .bashrc) to make using your manually installed version easier. In case you are using your piece of software for a web service, you will want to make sure you edit your fastcgi script or any other involved scripts to use your binary by changing the path or hardcoding the location. c4941ee0879e1bca3b7638e05ff1f2102e34c8e9 548 547 2018-01-21T14:19:51Z Bert 8 wikitext text/x-wiki While most webhosting providers give you access to a few or even just one programming language and a set amount of libraries, ULYSSIS prefers to offer more flexibility. We hope to give our users the chance to experiment with different languages, libraries and tools. There are of course also limits to what is realistic for us to install. More on that below. == Using a programming language, library or tool that is not installed == If the package that you would like us to install is available in the software repository of our current operating system, then that is usually not a problem. We currently use Ubuntu on all our servers, specifically, we upgrade to the latest LTS every summer vacation following the release of a new one. You can verify which version we are running by executing "cat /etc/lsb-release" on one of our shellservers. After you have verified what version we are running, you can refer to https://packages.ubuntu.com/ to check whether your package is available in that version of Ubuntu. If it is, then you can contact us by email on ulyssis@ulyssis.org which package or packages you would like to have installed, and what you will be using it for. You will most likely get a positive response. If your package is not in the repository, you will have to go for a [[Installing packages#Manual installation|Manual installation]]. == Using a newer/different version == As you can read in the section concerning the installation of new packages, we only offer the version available in the repository of the version of Ubuntu that we are running. In most cases, this means you will have to wait for a version upgrade with the next LTS release, or go for a [[Installing packages#Manual installation|Manual installation]]. However, there are some exceptions. Sometimes multiple version will be available in the repository, such as with Python 2 and 3, or Perl 5 and 6. In such cases, you can refer to the section above for instructions on how to request an installation. == Manual installation == If you want to install a piece of software that is not available in the repository or you wish to install another version, you can always install it manually onto your account. It is important to keep in mind that ULYSSIS will not support manually installed software, and that you are fully responsible for the security of this software. You are free to ask us questions, but we will most probably not help you. If you do require a manual installation of specific software, we expect you to be capable of maintaining it as well. The way you install your software differs depending on the software. You could be using tools such as pip, gem or npm to install to a directory in your home folder, you could be using a virtual environment, or you could be compiling your own binary. We suggest you look at the documentation of the software you're using very thoroughly, and make sure you are comfortable with what you are doing and aware of your responsibilities. After installing your software locally onto your account, you will probably want to add an alias in your dotfiles (for example .profile or .bashrc) to make using your manually installed version easier. In case you are using your piece of software for a web service, you will want to make sure you edit your fastcgi script or any other involved scripts to use your binary by changing the path or hardcoding the location. 56d5ec90463e742603a3ffaa7f825c8d4ee7875f 0 10 550 474 2018-02-24T20:52:34Z Bert 8 /* Let's Encrypt */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. For the first installation of a certificate, you will have to generate a new key as well as a certificate. For renewals, please '''always''' reuse the old key, so we only have to replace your certificate every few months. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, please create a folder ''letsencrypt'' in your home folder. Then add a folder per domain or group of domains, then add the relevant files. Please keep in mind that it is always good practice to have your key be only readable by you. So mind your permissions. Once you have placed your files in the correct folder. You can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. d6c8b677a7a18957e652994d116d90f19f0ec509 551 550 2018-02-24T20:55:54Z Bert 8 /* Let's Encrypt */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. For the first installation of a certificate, you will have to generate a new key as well as a certificate. For renewals, please '''always''' reuse the old key, so we only have to replace your certificate every few months. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, please create a folder ''letsencrypt'' in your home folder. Then add a folder per domain or group of domains, then add the relevant files. Please keep in mind that it is always good practice to have your key be only readable by you. So mind your permissions. Always remove irrevelant files, we do not wish to search for the right certificate. Once you have placed your files in the correct folder. You can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. ff8b7d63a9d09c09b4a5a1a1df270707a5ab3e70 552 551 2018-02-24T20:56:38Z Bert 8 /* Let's Encrypt */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. For the first installation of a certificate, you will have to generate a new key as well as a certificate. For renewals, please '''always''' reuse the old key, so we only have to replace your certificate every few months. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, please create a folder ''letsencrypt'' in your home folder. Then add a folder per domain or group of domains, then add the relevant files to the right domain folder. Please keep in mind that it is always good practice to have your key be only readable by you. So mind your permissions. Always remove irrevelant files, we do not wish to search for the right certificate. Once you have placed your files in the correct folder. You can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. c68793a848bd122fc97fd85c0737341456089486 553 552 2018-02-24T21:13:03Z Bert 8 /* Let's Encrypt */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. For the first installation of a certificate, you will have to generate a new key as well as a certificate. For renewals, please '''always''' reuse the old key, so we only have to replace your certificate and not the key every few months. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder ''letsencrypt'' in your home folder. Then add a folder per domain or group of domains, then add the relevant files to the right domain folder. Please keep in mind that it is always good practice to have your key be only readable by you. So mind your permissions. Always remove irrevelant files, we won't search for the right certificate. Your structure should look something like this: letsencrypt/ ├── interestingdomain.be │   ├── interestingdomain.chain │   ├── interestingdomain.crt │   └── interestingdomain.key └── otherdomain.com ├── otherdomain.chain ├── otherdomain.crt └── otherdomain.key Once you have placed your files in the correct folder. You can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. d597d7c12805e38f271d492150a2bc6c8ee99b3d 554 553 2018-02-24T21:18:27Z Bert 8 /* Let's Encrypt */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. For the first installation of a certificate, you will have to generate a new key as well as a certificate. For renewals, please '''always''' reuse the old key, so we only have to replace your certificate and not the key every few months. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder ''letsencrypt'' in your home folder. Then add a folder per domain or group of domains, then add the relevant files to the right domain folder. Please keep in mind that it is always good practice to have your key be only readable by you. So mind your permissions. Always remove irrevelant files, we won't search for the right certificate. Your structure should look something like this: letsencrypt/ ├── interestingdomain.be │   ├── interestingdomain.chain │   ├── interestingdomain.crt │   └── interestingdomain.key └── otherdomain.com ├── otherdomain.chain ├── otherdomain.crt └── otherdomain.key Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. d52b99c09e94563e9c3cf53dbb457e67035f8a08 555 554 2018-02-24T21:20:55Z Bert 8 /* Let's Encrypt */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. For the first installation of a certificate, you will have to generate a new key as well as a certificate. For renewals, please '''always''' reuse the old key, so we only have to replace your certificate and not the key every few months. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder ''letsencrypt'' in your home folder. Then add a folder per domain or group of domains, then add the relevant files to the right domain folder. Please keep in mind that it is always good practice to have your key be only readable by you, so check your permissions. Always remove irrevelant files, we won't search for the right certificate. Your structure should look something like this: letsencrypt/ ├── interestingdomain.be │   ├── interestingdomain.chain │   ├── interestingdomain.crt │   └── interestingdomain.key └── otherdomain.com ├── otherdomain.chain ├── otherdomain.crt └── otherdomain.key Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. 1436c476d4e39e6db433254299d2c42f948f4773 0 10 556 555 2018-02-24T21:22:41Z Bert 8 /* Let's Encrypt */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. For the first installation of a certificate, you will have to generate a new key as well as a certificate. For renewals, please '''always''' reuse the old key, so we only have to replace your certificate and not the key every few months. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder ''letsencrypt'' in your home folder. Then add a folder per domain or group of domains, then add the relevant files to the right domain folder. Please keep in mind that it is always good practice to have your key be only readable by you, so check your permissions. Always remove irrevelant files, we won't search for the right certificate. Your structure should look something like this: letsencrypt/ ├── interestingdomain.be │   ├── interestingdomain.chain │   ├── interestingdomain.crt │   └── interestingdomain.key └── otherdomain.com ├── otherdomain.chain ├── otherdomain.crt └── otherdomain.key Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. bbd146e2e9eb1152887b81b8bf9963b5a76db49b 580 556 2018-03-13T13:37:46Z Principis 32 /* Let's Encrypt */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. For the first installation of a certificate, you will have to generate a new key as well as a certificate. For renewals, please '''always''' reuse the old key, so we only have to replace your certificate and not the key every few months. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder ''letsencrypt'' in your home folder. Then add a folder per domain or group of domains, then add the relevant files to the right domain folder. Please keep in mind that it is always good practice to have your key be only readable by you, so check your permissions. Always remove irrevelant files, we won't search for the right certificate. Your structure should look something like this: letsencrypt/ ├── interestingdomain.be │   ├── interestingdomain.be.chain │   ├── interestingdomain.be.crt │   └── interestingdomain.be.key └── otherdomain.com ├── otherdomain.be.chain ├── otherdomain.be.crt └── otherdomain.be.key Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. ad75687f35dd96244a8d105e87d71666025305f0 581 580 2018-03-13T13:39:58Z Principis 32 /* Let's Encrypt */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. For the first installation of a certificate, you will have to generate a new key as well as a certificate. For renewals, please '''always''' reuse the old key, so we only have to replace your certificate and not the key every few months. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder ''letsencrypt'' in your home folder. Then add a folder per domain or group of domains, then add the relevant files to the right domain folder. Please keep in mind that it is always good practice to have your key be only readable by you, so check your permissions. Always remove irrevelant files, we won't search for the right certificate. Your structure should look something like this: letsencrypt/ ├── interestingdomain.be │   ├── interestingdomain.be.chain │   ├── interestingdomain.be.crt │   └── interestingdomain.be.key └── otherdomain.com ├── otherdomain.com.chain ├── otherdomain.com.crt └── otherdomain.com.key Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. 49ca36f73a4045cf37f10174371f7819e1212261 582 581 2018-03-14T20:02:26Z Principis 32 /* Let's Encrypt */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. For the first installation of a certificate, you will have to generate a new key as well as a certificate. For renewals, please '''always''' reuse the old key, so we only have to replace your certificate and not the key every few months. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder ''letsencrypt'' in your home folder. Then add a folder per domain or group of domains, then add the relevant files to the right domain folder. Please keep in mind that it is always good practice to have your key be only readable by you, so check your permissions. Always remove irrevelant files, we won't search for the right certificate. Rename your files like this: chain.pem -> interestingdomain.be.chain cert.pem -> interestingdomain.crt privkey.pem -> interestingdomain.key Your structure should look something like this: letsencrypt/ ├── interestingdomain.be │   ├── interestingdomain.be.chain │   ├── interestingdomain.be.crt │   └── interestingdomain.be.key └── otherdomain.com ├── otherdomain.com.chain ├── otherdomain.com.crt └── otherdomain.com.key Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. 627f601496aa39f69ef003f0bbf0ed2b1cc550ba 583 582 2018-03-14T20:05:51Z Principis 32 /* Let's Encrypt */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. For the first installation of a certificate, you will have to generate a new key as well as a certificate. For renewals, please '''always''' reuse the old key, so we only have to replace your certificate and not the key every few months. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder ''letsencrypt'' in your home folder. Then add a folder per domain or group of domains, then add the relevant files to the right domain folder. Please keep in mind that it is always good practice to have your key be only readable by you, so check your permissions. Always remove irrevelant files, we won't search for the right certificate. Rename your files like this: chain.pem -> interestingdomain.be.chain cert.pem -> interestingdomain.be.crt privkey.pem -> interestingdomain.be.key Your structure should look something like this: letsencrypt/ ├── interestingdomain.be │   ├── interestingdomain.be.chain │   ├── interestingdomain.be.crt │   └── interestingdomain.be.key └── otherdomain.com ├── otherdomain.com.chain ├── otherdomain.com.crt └── otherdomain.com.key Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. 7b449760273fac19d6638538ed83a9865ddd223a 602 583 2018-05-22T19:15:41Z Lars 26 /* Let's Encrypt */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. For the first installation of a certificate, you will have to generate a new key as well as a certificate. For renewals, please '''always''' reuse the old key, so we only have to replace your certificate and not the key every few months. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder ''letsencrypt'' in your home folder. Then add a folder per domain or group of domains, then add the relevant files to the right domain folder. Please keep in mind that it is always good practice to have your key be only readable by you, so check your permissions. Always remove irrevelant files, we won't search for the right certificate. Rename your files like this: chain.pem -> interestingdomain.be.chain cert.pem -> interestingdomain.be.crt privkey.pem -> interestingdomain.be.key Your structure should look something like this: letsencrypt/ ├── interestingdomain.be │   ├── interestingdomain.be.chain │   ├── interestingdomain.be.crt │   └── interestingdomain.be.key └── otherdomain.com ├── otherdomain.com.chain ├── otherdomain.com.crt └── otherdomain.com.key Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. You can check if your certificate will likely be okay with a command-line tool on our shellservers: <kbd>ulyssis-certificate check interestingdomain.be</kbd>. If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. de0ee45d9beab520bd9adf022101a26599a95d82 603 602 2018-05-22T19:18:15Z Lars 26 wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. For the first installation of a certificate, you will have to generate a new key as well as a certificate. For renewals, please '''always''' reuse the old key, so we only have to replace your certificate and not the key every few months. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder ''letsencrypt'' in your home folder. Then add a folder per domain or group of domains, then add the relevant files to the right domain folder. Please keep in mind that it is always good practice to have your key be only readable by you, so check your permissions. Always remove irrevelant files, we won't search for the right certificate. Rename your files like this: chain.pem -> interestingdomain.be.chain cert.pem -> interestingdomain.be.crt privkey.pem -> interestingdomain.be.key Your structure should look something like this: letsencrypt/ ├── interestingdomain.be │   ├── interestingdomain.be.chain │   ├── interestingdomain.be.crt │   └── interestingdomain.be.key └── otherdomain.com ├── otherdomain.com.chain ├── otherdomain.com.crt └── otherdomain.com.key Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ===Check certificate for common mistakes=== You can check if your certificate will likely be okay with a command-line tool on our shellservers: <kbd>ulyssis-certificate check interestingdomain.be</kbd>. If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. a994fb3eaf7e3c3e3c521b8586f4defc663715a8 0 3 557 549 2018-03-09T22:28:13Z Yoa 30 /* Security & anti-spam */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2016]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] * [[Claiming a port]] </div><div style="width:45%;float:left"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Anti-spam policies]] * [[Securing MediaWiki using Centrale KU Leuven Login]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 0e5d4b9d64234b5d6c1e3121c9c21d68785dc70c 585 557 2018-03-29T10:33:12Z Vincenttc 21 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, be free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2016]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] * [[Claiming a port]] </div><div style="width:45%;float:left"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 4cf420a12dac697db7a9c9ee963c79ec3c2253c9 0 98 558 538 2018-03-10T18:12:06Z Yoa 30 wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] df88ccda3865279179886242b267e9b01fe5d0a9 559 558 2018-03-10T18:12:32Z Yoa 30 /* Installation */ wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] cb54be21ae477a5176bd5aeaed9807f3d053ef2e 560 559 2018-03-10T18:32:52Z Yoa 30 /* Configuration */ wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === If you do not want guest visitors to visit any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctorate students, teaching assistants etc. will not be able to log in. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": [], "MWSAllowedStudies": [] }, to "config": { "MWSStudentsOnly": true, "MWSAllowedKULids": [], "MWSAllowedStudies": [] }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "[]", no KUL id checking will be performed. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": [], "MWSAllowedStudies": [] }, to "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": ["kul id 1", "kul id 2"...], "MWSAllowedStudies": [] }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 7282f9c4b9d7aade432c7478971b5a04915e8113 561 560 2018-03-10T20:43:18Z Yoa 30 /* MWSStudentsOnly */ wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === If you do not want guest visitors to visit any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctorate students, teaching assistants etc. will not be able to log in. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": [], "MWSAllowedDegrees": [] }, to "config": { "MWSStudentsOnly": true, "MWSAllowedKULids": [], "MWSAllowedDegrees": [] }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "[]", no KUL id checking will be performed. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": [], "MWSAllowedStudies": [] }, to "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": ["kul id 1", "kul id 2"...], "MWSAllowedStudies": [] }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 6dcbd44df2fde02e84bfc07ec07e652c6267aeb0 562 561 2018-03-10T20:43:23Z Yoa 30 /* MWSAllowedKULids */ wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === If you do not want guest visitors to visit any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctorate students, teaching assistants etc. will not be able to log in. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": [], "MWSAllowedDegrees": [] }, to "config": { "MWSStudentsOnly": true, "MWSAllowedKULids": [], "MWSAllowedDegrees": [] }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "[]", no KUL id checking will be performed. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": [], "MWSAllowedDegrees": [] }, to "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": ["kul id 1", "kul id 2"...], "MWSAllowedDegrees": [] }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 899f6f33ac6dc7b893cf332a0e9ff268237fc1b1 563 562 2018-03-10T20:45:19Z Yoa 30 /* Configuration */ wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === If you do not want guest visitors to visit any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctorate students, teaching assistants etc. will not be able to log in. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": [], "MWSAllowedDegrees": [] }, to "config": { "MWSStudentsOnly": true, "MWSAllowedKULids": [], "MWSAllowedDegrees": [] }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "[]", no KUL id checking will be performed. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": [], "MWSAllowedDegrees": [] }, to "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": ["r0653730", "KUL id 2", "KUL id 3"...], "MWSAllowedDegrees": [] }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is 51016742. If this option is set to "[]", no degree number checking will be performed. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": [], "MWSAllowedDegrees": [] }, to "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": [], "MWSAllowedDegrees": [51016742, degree number 2, degree number 3...] }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] f3c7b091a1014f116648c618fd89751ca2333045 564 563 2018-03-10T20:54:24Z Yoa 30 /* Configuration */ wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === If you do not want guest visitors to visit any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctorate students, teaching assistants etc. will not be able to log in. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": [], "MWSAllowedDegrees": [] }, to "config": { "MWSStudentsOnly": true, "MWSAllowedKULids": [], "MWSAllowedDegrees": [] }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "[]", no KUL id checking will be performed. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": [], "MWSAllowedDegrees": [] }, to "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": ["r0653730", "KUL id 2", "KUL id 3"...], "MWSAllowedDegrees": [] }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "[]", no degree number checking will be performed. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": [], "MWSAllowedDegrees": [] }, to "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": [], "MWSAllowedDegrees": ["51016742", "degree number 2", "degree number 3"...] }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] e6cb6fe832b1e1d7e554b99f659f9c2a7b87834f 565 564 2018-03-10T20:59:41Z Yoa 30 /* Configuration */ wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === If you do not want guest visitors to visit any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctorate students, teaching assistants etc. will not be able to log in. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, to "config": { "MWSStudentsOnly": true, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, to "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "r0653730, KUL id 2, KUL id 3", "MWSAllowedDegrees": "" }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "[]", no degree number checking will be performed. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, to "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "51016742, degree number 2, degree number 3" }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 04b9cf7f865af5d7f1d4900fbf9e1ce5331eeee8 566 565 2018-03-10T21:08:43Z Yoa 30 /* Restricting access to logged-in users only */ wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to visit any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctorate students, teaching assistants etc. will not be able to log in. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, to "config": { "MWSStudentsOnly": true, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, to "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "r0653730, KUL id 2, KUL id 3", "MWSAllowedDegrees": "" }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "[]", no degree number checking will be performed. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, to "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "51016742, degree number 2, degree number 3" }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 906d293d0409377902365f21a02ecc59aded82de 567 566 2018-03-10T21:09:13Z Yoa 30 /* Restricting access to logged-in users only */ wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctorate students, teaching assistants etc. will not be able to log in. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, to "config": { "MWSStudentsOnly": true, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, to "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "r0653730, KUL id 2, KUL id 3", "MWSAllowedDegrees": "" }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "[]", no degree number checking will be performed. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, to "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "51016742, degree number 2, degree number 3" }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] c4bc573305918fb004ee1ad3f9c87bf0356f47dc 568 567 2018-03-10T21:15:27Z Yoa 30 /* MWSAllowedKULids */ wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctorate students, teaching assistants etc. will not be able to log in. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, to "config": { "MWSStudentsOnly": true, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, to "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "r0653730, r0300342, KUL id 3", "MWSAllowedDegrees": "" }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "[]", no degree number checking will be performed. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, to "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "51016742, degree number 2, degree number 3" }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 92c5d70e1192b7fdb147acf10b90e1223ea11d41 569 568 2018-03-10T21:15:39Z Yoa 30 /* MWSAllowedDegrees */ wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctorate students, teaching assistants etc. will not be able to log in. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, to "config": { "MWSStudentsOnly": true, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, to "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "r0653730, r0300342, KUL id 3", "MWSAllowedDegrees": "" }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "[]", no degree number checking will be performed. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, to "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "51016742, 51016835, 51016753" }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 9e5956f17503ec17b2ab0851193715e137f3b114 570 569 2018-03-10T21:16:06Z Yoa 30 /* MWSAllowedDegrees */ wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctorate students, teaching assistants etc. will not be able to log in. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, to "config": { "MWSStudentsOnly": true, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, to "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "r0653730, r0300342, KUL id 3", "MWSAllowedDegrees": "" }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "[]", no degree number checking will be performed. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, to "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "51016742, 51016835, 51016753..." }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] c62da370d7f26860beb49cc4d3880baeba38862e 571 570 2018-03-10T21:16:25Z Yoa 30 /* MWSAllowedKULids */ wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctorate students, teaching assistants etc. will not be able to log in. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, to "config": { "MWSStudentsOnly": true, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, to "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "r0653730, r0300342, KUL id 3...", "MWSAllowedDegrees": "" }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "[]", no degree number checking will be performed. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, to "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "51016742, 51016835, 51016753..." }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 297c047d00d9dec80da2a92785f8c8737d0f752e 572 571 2018-03-10T21:27:24Z Yoa 30 /* MWSAllowedKULids */ wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctorate students, teaching assistants etc. will not be able to log in. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, to "config": { "MWSStudentsOnly": true, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, to "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "r0653730, r0300342, KUL id 3...", "MWSAllowedDegrees": "" }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "[]", no degree number checking will be performed. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, to "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "51016742, 51016835, 51016753..." }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] e845ced4b55e028d110ccd68330493ec21511ca1 573 572 2018-03-10T21:27:41Z Yoa 30 /* MWSAllowedDegrees */ wikitext text/x-wiki ==About== MediaWikiShibboleth is the name of a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctorate students, teaching assistants etc. will not be able to log in. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, to "config": { "MWSStudentsOnly": true, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, to "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "r0653730, r0300342, KUL id 3...", "MWSAllowedDegrees": "" }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "[]", no degree number checking will be performed. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, to "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "51016742, 51016835, 51016753..." }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. You can add as many degree numbers as you like, separated by a comma. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 65c6bcd3fe8fa75cf7102190d08233d2cd804807 574 573 2018-03-11T10:13:50Z Lars 26 /* About */ wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctorate students, teaching assistants etc. will not be able to log in. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, to "config": { "MWSStudentsOnly": true, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, to "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "r0653730, r0300342, KUL id 3...", "MWSAllowedDegrees": "" }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "[]", no degree number checking will be performed. Set this option by changing "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "" }, to "config": { "MWSStudentsOnly": false, "MWSAllowedKULids": "", "MWSAllowedDegrees": "51016742, 51016835, 51016753..." }, in <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code>. You can add as many degree numbers as you like, separated by a comma. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 88aa24ea8517b94a90c8bbccc42248787cb9d9fe 575 574 2018-03-11T12:20:49Z Yoa 30 /* Configuration */ wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctorate students, teaching assistants etc. will not be able to log in. Set this option by adding $wgMWSStudentsOnly = true; to <code><mediawiki installation folder>/LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "[]", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 9638fe33046574220e945549d22b050865444066 576 575 2018-03-13T02:20:57Z Bert 8 /* Prerequisites */ wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctorate students, teaching assistants etc. will not be able to log in. Set this option by adding $wgMWSStudentsOnly = true; to <code><mediawiki installation folder>/LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "[]", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] dd5b41c51b44a89b131e232225be059d276191af 577 576 2018-03-13T02:25:19Z Bert 8 /* MWSStudentsOnly */ wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for Shibboleth (Centrale KU Leuven) login. The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code><mediawiki installation folder>/LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "[]", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 1903a7aec62d2a87f24fc426b09ed3ce297b5ff6 578 577 2018-03-13T03:34:40Z Bert 8 wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for login through the Central KU Leuven Login (Shibboleth). The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Centrale KU Leuven) login enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code><mediawiki installation folder>/LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "[]", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 6f43dcf21fdd981b12bb589f19ad5bcb4fc4042c 579 578 2018-03-13T03:35:06Z Bert 8 /* Prerequisites */ wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for login through the Central KU Leuven Login (Shibboleth). The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Central KU Leuven Login) enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code><mediawiki installation folder>/LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "[]", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 356f97ca74f89beab6d8e472df9fe5adf71e3106 0 11 584 67 2018-03-15T17:21:07Z Bert 8 wikitext text/x-wiki By default, your website is accessible at the following URLs: * http://''username''.ulyssis.be * http://''username''.studentenweb.org Where ''username'' is your ULYSSIS user name. If you wish, you can also register another domain name. ULYSSIS isn't a domain name registrar, so you'll have to use an external registrar. For example, you can find a list of all registrars for .be at [http://dns.be dns.be]. If you have registered your own domain and you want to use it with your ULYSSIS account, you need to: # Point your domain name to the following ULYSSIS nameservers: ## ns.ulyssis.student.kuleuven.be ## ns3.ulyssis.student.kuleuven.be ## Optionally: ns2.ulyssis.student.kuleuven.be # Mail us at ulyssis@ulyssis.org, with the following details: ## Your ULYSSIS username ## The domain name you registered ## The directory that you want the domain to point at. This could be your <code>www</code> folder, but any other folder within your home directory is possible. ## Whether you want to receive e-mail at that domain name via ULYSSIS. Note that we need to request this with ICTS, so this will take a while. Please do keep in mind that, just like any change to an account, this can only be requested by the account holder. You can find more information about DNS at http://en.wikipedia.org/wiki/Domain_Name_System. b97abf5a419c7a9ff229bedc05e35d335221f97b 0 37 586 473 2018-04-28T22:18:16Z Bert 8 wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers of course. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</pre> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' Do not place sensitive files inside the web accessible folder.Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.</div> It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than were it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> Or, for Python 3: <pre>virtualenv ~/.venv --python=python3</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [http://flask.pocoo.org/docs/0.10/deploying/fastcgi/ Flask documentation for FastCGI] ad4a46565421f41c984ce2a396e6b4a76e3dbd24 587 586 2018-04-28T22:18:38Z Bert 8 wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</pre> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' Do not place sensitive files inside the web accessible folder.Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.</div> It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than were it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> Or, for Python 3: <pre>virtualenv ~/.venv --python=python3</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [http://flask.pocoo.org/docs/0.10/deploying/fastcgi/ Flask documentation for FastCGI] 93c94e0ef8052531635eaec0be85ba91d2f8e32d 588 587 2018-04-28T22:19:29Z Bert 8 /* FastCGI */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</pre> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' Do not place sensitive files inside the web accessible folder.Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.</div> It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than were it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> Or, for Python 3: <pre>virtualenv ~/.venv --python=python3</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [http://flask.pocoo.org/docs/0.10/deploying/fastcgi/ Flask documentation for FastCGI] 9076c4e8a44b741e58746b21b2d87c4acf0d218c 589 588 2018-04-28T22:29:16Z Bert 8 /* FastCGI */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</pre> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' Do not place sensitive files inside the web accessible folder.Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.</div> It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below) but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will only experience one slow request. This slow startup is obviously not a factor faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have fastcgi processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated and Apache is therefore reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [Managing_Cron_jobs cronjob] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than were it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> Or, for Python 3: <pre>virtualenv ~/.venv --python=python3</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [http://flask.pocoo.org/docs/0.10/deploying/fastcgi/ Flask documentation for FastCGI] 013f31fe7731d24fbe9babc686d12900341c38d7 590 589 2018-04-28T22:31:03Z Bert 8 /* Startup time and persistency */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</pre> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' Do not place sensitive files inside the web accessible folder.Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.</div> It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have fastcgi processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated and Apache is therefore reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [Managing_Cron_jobs cronjob] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than were it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> Or, for Python 3: <pre>virtualenv ~/.venv --python=python3</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [http://flask.pocoo.org/docs/0.10/deploying/fastcgi/ Flask documentation for FastCGI] bc4dcbb3e60565b263d65d774972fe53f2b01922 591 590 2018-04-28T22:31:21Z Bert 8 /* Startup time and persistency */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</pre> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' Do not place sensitive files inside the web accessible folder.Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.</div> It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have fastcgi processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated and Apache is therefore reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [Managing_Cron_jobs cronjob] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than were it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> Or, for Python 3: <pre>virtualenv ~/.venv --python=python3</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [http://flask.pocoo.org/docs/0.10/deploying/fastcgi/ Flask documentation for FastCGI] 1d4a9f8acb4c3f353297a03725f21cb9c18fd88b 592 591 2018-04-28T22:32:14Z Bert 8 /* Startup time and persistency */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</pre> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' Do not place sensitive files inside the web accessible folder.Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.</div> It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [Managing_Cron_jobs cronjob] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than were it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> Or, for Python 3: <pre>virtualenv ~/.venv --python=python3</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [http://flask.pocoo.org/docs/0.10/deploying/fastcgi/ Flask documentation for FastCGI] 6d6527c27109fda7ecddf23dd7c3561acee41e4e 593 592 2018-04-28T22:32:53Z Bert 8 /* Startup time and persistency */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</pre> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' Do not place sensitive files inside the web accessible folder.Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.</div> It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [[Managing_Cron_jobs cronjob]] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than were it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> Or, for Python 3: <pre>virtualenv ~/.venv --python=python3</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [http://flask.pocoo.org/docs/0.10/deploying/fastcgi/ Flask documentation for FastCGI] 0fadd759e10d7ecbe650df0bcce21b6d4f66e013 594 593 2018-04-28T22:33:02Z Bert 8 /* Startup time and persistency */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</pre> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' Do not place sensitive files inside the web accessible folder.Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.</div> It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [[Managing_Cron_jobs | cronjob]] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than were it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> Or, for Python 3: <pre>virtualenv ~/.venv --python=python3</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre>#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [http://flask.pocoo.org/docs/0.10/deploying/fastcgi/ Flask documentation for FastCGI] 1736988ec7aa1492a84f1d8a31eb6bfab9fba98c 0 19 595 535 2018-05-07T04:07:46Z Bert 8 wikitext text/x-wiki Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mail regularly, because all important information will be sent to this address. You can check your e-mail using the webmail or an email client of your own. ==Webmail== You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to enter the website. ==POP and IMAP access== You can access your ulyssis mail by POP or IMAP protocol. The configuration parameters are: * '''server''': <tt>mail.ulyssis.org</tt> * '''username''': ''your ULYSSIS username'' * '''password''': ''your ULYSSIS password'' * '''security''': SSL ==SMTP== ULYSSIS doesn't offer SMTP. Instead, you can use KULeuven's SMTP server: * '''server''': <tt>smtps.kuleuven.be</tt> * '''port''': 443 * '''username''': ''your student id'' * '''password''': ''your KULeuven password'' * '''security''': SSL == Advanced == Your emails are stored within your account under ~/Maildir. These files can of course be read with a command line email client such as alpine or mutt. Beyond that we also support sendmail style local delivery using .forward. More information is available in the official documentation of [[https://www.sendmail.org/~ca/email/doc8.9/op-sh-2.html#sh-2.8 Sendmail]] and [[Postfix http://www.postfix.org/local.8.html]]. You can also use procmail on our services. A very detailed explenation on procmail is available on the [[Arch Linux wiki https://wiki.archlinux.org/index.php/Procmail]] 3048a50d6b328c690c04d70cc000e0def11d6ff4 596 595 2018-05-07T04:08:17Z Bert 8 /* Advanced */ wikitext text/x-wiki Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mail regularly, because all important information will be sent to this address. You can check your e-mail using the webmail or an email client of your own. ==Webmail== You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to enter the website. ==POP and IMAP access== You can access your ulyssis mail by POP or IMAP protocol. The configuration parameters are: * '''server''': <tt>mail.ulyssis.org</tt> * '''username''': ''your ULYSSIS username'' * '''password''': ''your ULYSSIS password'' * '''security''': SSL ==SMTP== ULYSSIS doesn't offer SMTP. Instead, you can use KULeuven's SMTP server: * '''server''': <tt>smtps.kuleuven.be</tt> * '''port''': 443 * '''username''': ''your student id'' * '''password''': ''your KULeuven password'' * '''security''': SSL == Advanced == Your emails are stored within your account under ~/Maildir. These files can of course be read with a command line email client such as alpine or mutt. Beyond that we also support sendmail style local delivery using .forward. More information is available in the official documentation of [https://www.sendmail.org/~ca/email/doc8.9/op-sh-2.html#sh-2.8 Sendmail] and [http://www.postfix.org/local.8.html Postfix]. You can also use procmail on our services. A very detailed explenation on procmail is available on the [https://wiki.archlinux.org/index.php/Procmail Arch Linux wiki] b23686cf45b3c45a9156ae6ec85ad55300f52abf 597 596 2018-05-07T04:08:58Z Bert 8 /* Advanced */ wikitext text/x-wiki Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mail regularly, because all important information will be sent to this address. You can check your e-mail using the webmail or an email client of your own. ==Webmail== You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to enter the website. ==POP and IMAP access== You can access your ulyssis mail by POP or IMAP protocol. The configuration parameters are: * '''server''': <tt>mail.ulyssis.org</tt> * '''username''': ''your ULYSSIS username'' * '''password''': ''your ULYSSIS password'' * '''security''': SSL ==SMTP== ULYSSIS doesn't offer SMTP. Instead, you can use KULeuven's SMTP server: * '''server''': <tt>smtps.kuleuven.be</tt> * '''port''': 443 * '''username''': ''your student id'' * '''password''': ''your KULeuven password'' * '''security''': SSL == Advanced == Your emails are stored within your account under ~/Maildir. These files can of course be read with a command line email client such as alpine or mutt. We also support sendmail style local delivery using .forward. More information is available in the official documentation of [https://www.sendmail.org/~ca/email/doc8.9/op-sh-2.html#sh-2.8 Sendmail] and [http://www.postfix.org/local.8.html Postfix]. You can also use procmail on our services. A very detailed explenation on procmail is available on the [https://wiki.archlinux.org/index.php/Procmail Arch Linux wiki]. 52226efc30872aca4106232892547130e1c77145 598 597 2018-05-07T04:09:23Z Bert 8 /* Advanced */ wikitext text/x-wiki Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mail regularly, because all important information will be sent to this address. You can check your e-mail using the webmail or an email client of your own. ==Webmail== You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to enter the website. ==POP and IMAP access== You can access your ulyssis mail by POP or IMAP protocol. The configuration parameters are: * '''server''': <tt>mail.ulyssis.org</tt> * '''username''': ''your ULYSSIS username'' * '''password''': ''your ULYSSIS password'' * '''security''': SSL ==SMTP== ULYSSIS doesn't offer SMTP. Instead, you can use KULeuven's SMTP server: * '''server''': <tt>smtps.kuleuven.be</tt> * '''port''': 443 * '''username''': ''your student id'' * '''password''': ''your KULeuven password'' * '''security''': SSL == Advanced == Your emails are stored within your account under ~/Maildir. These files can of course be read with a command line email client such as alpine or mutt. We support sendmail style local delivery using .forward. More information is available in the official documentation of [https://www.sendmail.org/~ca/email/doc8.9/op-sh-2.html#sh-2.8 Sendmail] and [http://www.postfix.org/local.8.html Postfix]. You can also use procmail on our services. A very detailed explenation on procmail is available on the [https://wiki.archlinux.org/index.php/Procmail Arch Linux wiki]. 3448c421ebeac2a1ea1b7d2e8c12b3084628f430 599 598 2018-05-07T04:09:32Z Bert 8 /* Advanced */ wikitext text/x-wiki Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mail regularly, because all important information will be sent to this address. You can check your e-mail using the webmail or an email client of your own. ==Webmail== You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to enter the website. ==POP and IMAP access== You can access your ulyssis mail by POP or IMAP protocol. The configuration parameters are: * '''server''': <tt>mail.ulyssis.org</tt> * '''username''': ''your ULYSSIS username'' * '''password''': ''your ULYSSIS password'' * '''security''': SSL ==SMTP== ULYSSIS doesn't offer SMTP. Instead, you can use KULeuven's SMTP server: * '''server''': <tt>smtps.kuleuven.be</tt> * '''port''': 443 * '''username''': ''your student id'' * '''password''': ''your KULeuven password'' * '''security''': SSL == Advanced == Your emails are stored within your account under ~/Maildir. These files can of course be read with a command line email client such as alpine or mutt. We support sendmail style local delivery using .forward. More information is available in the official documentation of [https://www.sendmail.org/~ca/email/doc8.9/op-sh-2.html#sh-2.8 Sendmail] and [http://www.postfix.org/local.8.html Postfix]. You can also use procmail on our servers. A very detailed explenation on procmail is available on the [https://wiki.archlinux.org/index.php/Procmail Arch Linux wiki]. a3d1b13c5f1e3c010fb5a88c3e6f4ee7a99492c7 600 599 2018-05-07T04:09:45Z Bert 8 /* Advanced */ wikitext text/x-wiki Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mail regularly, because all important information will be sent to this address. You can check your e-mail using the webmail or an email client of your own. ==Webmail== You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to enter the website. ==POP and IMAP access== You can access your ulyssis mail by POP or IMAP protocol. The configuration parameters are: * '''server''': <tt>mail.ulyssis.org</tt> * '''username''': ''your ULYSSIS username'' * '''password''': ''your ULYSSIS password'' * '''security''': SSL ==SMTP== ULYSSIS doesn't offer SMTP. Instead, you can use KULeuven's SMTP server: * '''server''': <tt>smtps.kuleuven.be</tt> * '''port''': 443 * '''username''': ''your student id'' * '''password''': ''your KULeuven password'' * '''security''': SSL == Advanced == Your emails are stored within your account under ~/Maildir. These files can of course be read with a command line email client such as alpine or mutt. We support sendmail style local delivery using .forward. More information is available in the official documentation of [https://www.sendmail.org/~ca/email/doc8.9/op-sh-2.html#sh-2.8 Sendmail] and [http://www.postfix.org/local.8.html Postfix]. You can also use procmail on our servers. A very detailed explanation on procmail is available on the [https://wiki.archlinux.org/index.php/Procmail Arch Linux wiki]. 645e78fed14b9ac7004c2ecfd2a99333afad7ee7 601 600 2018-05-07T04:10:06Z Bert 8 /* Advanced */ wikitext text/x-wiki Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mail regularly, because all important information will be sent to this address. You can check your e-mail using the webmail or an email client of your own. ==Webmail== You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to enter the website. ==POP and IMAP access== You can access your ulyssis mail by POP or IMAP protocol. The configuration parameters are: * '''server''': <tt>mail.ulyssis.org</tt> * '''username''': ''your ULYSSIS username'' * '''password''': ''your ULYSSIS password'' * '''security''': SSL ==SMTP== ULYSSIS doesn't offer SMTP. Instead, you can use KULeuven's SMTP server: * '''server''': <tt>smtps.kuleuven.be</tt> * '''port''': 443 * '''username''': ''your student id'' * '''password''': ''your KULeuven password'' * '''security''': SSL == Advanced == Your emails are stored within your account under ~/Maildir. These files can of course be read with a command line email client such as alpine or mutt. We support sendmail style local delivery using .forward. More information is available in the official documentation of [https://www.sendmail.org/~ca/email/doc8.9/op-sh-2.html#sh-2.8 Sendmail] and [http://www.postfix.org/local.8.html Postfix]. You can also use procmail on our servers. A very detailed explanation on procmail is available on the [https://wiki.archlinux.org/index.php/Procmail ArchWiki]. cfb54f397a6325e547061b4b1044132c565c7b34 0 7 604 359 2018-05-28T12:30:21Z Tim 25 wikitext text/x-wiki ULYSSIS hosts its own IRC server. (IRC stands for Internet Relay Chat, [https://en.wikipedia.org/wiki/Internet_Relay_Chat IRC on wikipedia]) ==Contact us on IRC== IRC is a chat protocol. If you have a question, you can use IRC as a fast way to contact us. Details: Server: irc.ulyssis.org Port: 6668 (SSL) Channel: #ulyssis To use IRC you'll need an IRC client, we advise the terminal based [https://irssi.org/ irssi] for Linux and [https://hexchat.github.io/ hexchat] or [https://www.mirc.com/ mIRC] for Windows, but there are a lot of other free options. ==Using our web IRC client== If you won't regularly use our IRC or if you just want to check it out, you can use our web IRC client instead. You can find it at [https://webirc.ulyssis.org/ webirc.ulyssis.org]. ==Using irssi in a screen or tmux session== Our IRC server isn't very crowded and as you only see messages when you're connected, we advise you to run irssi in either a screen or a tmux session. Members can run screen or tmux on our shellservers, as they keep running 24/7 you can use them to keep track of your conversations. Screen and tmux are similar programs. Screen has been around for longer and is more tested, while tmux is more modern with new features and being easier to use for beginners. ===Connect to the shellserver=== Use the ssh command in your Linux or OS X terminal, or use PuTTY to connect on windows. Extensive information on how to do so can be found on [[Accessing shell servers over SSH]]. ===Start irssi in a screen=== *When on the shellserver, enter <code>screen</code> to start a screen session, or <code>tmux</code> to start a tmux session. *Enter <code>irssi</code> to start irssi *Connect to the IRC server: <code>/server -ssl irc.ulyssis.org 6668</code> *Connect to the public channel: <code>/join #ulyssis</code> ===Screen usage=== *To exit the screen: press Ctrl-A and press D ('detach') to return to the shellserver. *To reconnect: enter <code>screen -r</code> or <code>screen -DR</code> (the latter will create a new screen if it wasn't already made). ===Tmux usage=== *To exit the tmux session: press Ctrl-B and press D ('detach') to return to the shellserver. *To reconnect: enter <code>tmux attach</code> ===Help, I can't reconnect to my session!=== *Check if you are on the right shell server and didn't make a typing error. *If everything is correct, your screen may have been stopped by a crash or a reboot of our shellserver. You can check the [http://www.ulyssis.org/status status] section of our website for more information about possible downtimes. *Make sure you use the right program (<code>screen</code> if you started a screen session and <code>tmux</code> if you started a tmux session) 4a177639c9b1405cac93d1eef1a4aa150ad86250 605 604 2018-05-31T20:14:55Z Tim 25 /* Start irssi in a screen */ wikitext text/x-wiki ULYSSIS hosts its own IRC server. (IRC stands for Internet Relay Chat, [https://en.wikipedia.org/wiki/Internet_Relay_Chat IRC on wikipedia]) ==Contact us on IRC== IRC is a chat protocol. If you have a question, you can use IRC as a fast way to contact us. Details: Server: irc.ulyssis.org Port: 6668 (SSL) Channel: #ulyssis To use IRC you'll need an IRC client, we advise the terminal based [https://irssi.org/ irssi] for Linux and [https://hexchat.github.io/ hexchat] or [https://www.mirc.com/ mIRC] for Windows, but there are a lot of other free options. ==Using our web IRC client== If you won't regularly use our IRC or if you just want to check it out, you can use our web IRC client instead. You can find it at [https://webirc.ulyssis.org/ webirc.ulyssis.org]. ==Using irssi in a screen or tmux session== Our IRC server isn't very crowded and as you only see messages when you're connected, we advise you to run irssi in either a screen or a tmux session. Members can run screen or tmux on our shellservers, as they keep running 24/7 you can use them to keep track of your conversations. Screen and tmux are similar programs. Screen has been around for longer and is more tested, while tmux is more modern with new features and being easier to use for beginners. ===Connect to the shellserver=== Use the ssh command in your Linux or OS X terminal, or use PuTTY to connect on windows. Extensive information on how to do so can be found on [[Accessing shell servers over SSH]]. ===Start irssi in a screen=== *When on the shellserver, enter <code>screen -U</code> to start a screen session, or <code>tmux</code> to start a tmux session. *Enter <code>irssi</code> to start irssi *Connect to the IRC server: <code>/server -ssl irc.ulyssis.org 6668</code> *Connect to the public channel: <code>/join #ulyssis</code> ===Screen usage=== *To exit the screen: press Ctrl-A and press D ('detach') to return to the shellserver. *To reconnect: enter <code>screen -r</code> or <code>screen -DR</code> (the latter will create a new screen if it wasn't already made). ===Tmux usage=== *To exit the tmux session: press Ctrl-B and press D ('detach') to return to the shellserver. *To reconnect: enter <code>tmux attach</code> ===Help, I can't reconnect to my session!=== *Check if you are on the right shell server and didn't make a typing error. *If everything is correct, your screen may have been stopped by a crash or a reboot of our shellserver. You can check the [http://www.ulyssis.org/status status] section of our website for more information about possible downtimes. *Make sure you use the right program (<code>screen</code> if you started a screen session and <code>tmux</code> if you started a tmux session) 5503c0fac2373f5bdabe5c12242e962699e9c3e6 0 3 606 585 2018-06-22T17:11:09Z Simon 36 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2016]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] * [[Claiming a port]] </div><div style="width:45%;float:left"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ c708784f744c787b056d4e24ccb1ca90eb003b5c 620 606 2018-07-16T10:40:46Z Simon 36 /* Security & anti-spam */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2016]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] * [[Claiming a port]] </div><div style="width:45%;float:left"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 3bf8f243514f502a46f04efd967d2eb350a8c8a5 621 620 2018-07-16T10:43:48Z Simon 36 /* CMSs */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2016]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] * [[Claiming a port]] </div><div style="width:45%;float:left"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 5e9ff4685d98989a4ade902755f8f2dc84443511 622 621 2018-07-16T10:44:15Z Simon 36 /* Files */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] * [[Secure file permissions]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2016]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] * [[Claiming a port]] </div><div style="width:45%;float:left"> == Mail == * [[ULYSSIS mail]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ b1f68f5b82d4d9dc76545614c49817208e73e75d 639 622 2018-10-10T14:48:58Z Bert 8 /* Mail */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] * [[Secure file permissions]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2016]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] * [[Claiming a port]] </div><div style="width:45%;float:left"> == Mail == * [[Mailbox]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 87440d2e52b9b60fc1f1c4e52f236c6423309fbb 644 639 2018-10-10T21:06:55Z Bert 8 /* Mail */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] * [[Secure file permissions]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2016]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] * [[Claiming a port]] </div><div style="width:45%;float:left"> == Mail == * [[All about e-mail]] * [[Mailbox]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ e3bd4e18ac83bfb4e05a03b5fef3cdb3c9416967 645 644 2018-10-10T23:41:37Z Bert 8 /* Mail */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] * [[Secure file permissions]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2016]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] * [[Claiming a port]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 53e1b1a3127e46998cc857b53c6bfb82ef55d273 0 43 607 475 2018-06-23T01:48:01Z Bert 8 wikitext text/x-wiki You may want to receive e-mail from ulyssis on another email provider. It is very easy to set this up. == Change the forwarders for your @ulyssis email address == # Go to ucc.ulyssis.org and log in with your username and password. # On the right side, click on '''Mail'''. # Under '''Address forward''' you can change the forward address of your ULYSSIS mail by clicking on '''edit'''. # Choose '''forward''' and enter the email address you want to forward your ULYSSIS mail to and save the changes. # If you forward to Gmail, Hotmail. or use Thunderbird, we recommend looking at [[Using a forwarder as an alias]] so you can send mails under the forwarding address instead of just your own. == Change the forwarders for other domains == # Go to ucc.ulyssis.org and log in with your username and password. # On the right side, click on '''Mail'''. # Under '''Virtual Domains''', click on the domain you want to change. # You can change a forwarder by clicking on '''edit''' or on '''Add alias''' and add the forwarders you want. # Save your changes == Use your mailbox and forwarders at the same time == An alternative way to set the forwarders, that will also allow you to use your mailbox and the webinterface, is to use a .forward file. On each line of this file, you can specify to wich addresses you want to forward the email. If one of the addresses is the same as your @ulyssis address, then the mail will also be placed in your ULYSSIS mailbox. In the following example, your @ulyssis email address is <code>user@ulyssis.org</code>. Example .forward file: user@ulyssis.org example@gmail.com example2@skynet.be This will place the email in your ULYSSIS mailbox so that you can access it from the webinterface or your local mailclient. It will also forward the mail to <code>example@gmail.com</code> and <code>example2@skynet.be</code>. To use this, place a .forward file with the prefered email addresses in your homedir, see [[Accessing your files]], and set your forwarder to 'Inbox' in https://ucc.ulyssis.org/mail ced20325b9a3b79aa750368bf0b3607e26879f31 632 607 2018-08-04T17:17:29Z Lars 26 Add images for forwarder setup wikitext text/x-wiki You may want to receive e-mail from ulyssis on another email provider. It is very easy to set this up. == Change the forwarders for your @ulyssis email address == # Go to ucc.ulyssis.org and log in with your username and password. # On the right side, click on '''Mail'''. # Under '''Address forward''' you can change the forward address of your ULYSSIS mail by clicking on '''edit'''. # Choose '''forward''' and enter the email address you want to forward your ULYSSIS mail to and save the changes. # If you forward to Gmail, Hotmail. or use Thunderbird, we recommend looking at [[Using a forwarder as an alias]] so you can send mails under the forwarding address instead of just your own. == Change the forwarders for other domains == # Go to ucc.ulyssis.org and log in with your username and password. # On the right side, click on '''Mail'''. [[File:Forwarder Step1.png|700px]] # Under '''Virtual Domains''', click on the domain you want to change. [[File:Forwarder Step2.png|700px]] # You can change a forwarder by clicking on '''edit''' or on '''Add alias''' and add the forwarders you want. [[File:Forwarder Step3.png|700px]] # Save your changes == Use your mailbox and forwarders at the same time == An alternative way to set the forwarders, that will also allow you to use your mailbox and the webinterface, is to use a .forward file. On each line of this file, you can specify to wich addresses you want to forward the email. If one of the addresses is the same as your @ulyssis address, then the mail will also be placed in your ULYSSIS mailbox. In the following example, your @ulyssis email address is <code>user@ulyssis.org</code>. Example .forward file: user@ulyssis.org example@gmail.com example2@skynet.be This will place the email in your ULYSSIS mailbox so that you can access it from the webinterface or your local mailclient. It will also forward the mail to <code>example@gmail.com</code> and <code>example2@skynet.be</code>. To use this, place a .forward file with the prefered email addresses in your homedir, see [[Accessing your files]], and set your forwarder to 'Inbox' in https://ucc.ulyssis.org/mail 5cd82c7678e1a38aae17549c760eb585c7076473 636 632 2018-08-30T14:25:30Z Lars 26 /* Change the forwarders for your @ulyssis email address */ wikitext text/x-wiki You may want to receive e-mail from ulyssis on another email provider. It is very easy to set this up. == Change the forwarders for your @ulyssis.org email address == # Go to ucc.ulyssis.org and log in with your username and password. # On the right side, click on '''Mail'''. # Under '''Address forward''' you can change the forward address of your ULYSSIS mail by clicking on '''edit'''. # Choose '''forward''' and enter the email address you want to forward your ULYSSIS mail to and save the changes. # If you forward to Gmail, Hotmail. or use Thunderbird, we recommend looking at [[Using a forwarder as an alias]] so you can send mails under the forwarding address instead of just your own. == Change the forwarders for other domains == # Go to ucc.ulyssis.org and log in with your username and password. # On the right side, click on '''Mail'''. [[File:Forwarder Step1.png|700px]] # Under '''Virtual Domains''', click on the domain you want to change. [[File:Forwarder Step2.png|700px]] # You can change a forwarder by clicking on '''edit''' or on '''Add alias''' and add the forwarders you want. [[File:Forwarder Step3.png|700px]] # Save your changes == Use your mailbox and forwarders at the same time == An alternative way to set the forwarders, that will also allow you to use your mailbox and the webinterface, is to use a .forward file. On each line of this file, you can specify to wich addresses you want to forward the email. If one of the addresses is the same as your @ulyssis address, then the mail will also be placed in your ULYSSIS mailbox. In the following example, your @ulyssis email address is <code>user@ulyssis.org</code>. Example .forward file: user@ulyssis.org example@gmail.com example2@skynet.be This will place the email in your ULYSSIS mailbox so that you can access it from the webinterface or your local mailclient. It will also forward the mail to <code>example@gmail.com</code> and <code>example2@skynet.be</code>. To use this, place a .forward file with the prefered email addresses in your homedir, see [[Accessing your files]], and set your forwarder to 'Inbox' in https://ucc.ulyssis.org/mail 40f992884d268a0cab219b51467ae31325e7e0d3 0 53 608 422 2018-06-23T10:37:27Z Bert 8 wikitext text/x-wiki Because in our webserversetup PHP is installed as a common gateway interface (CGI) basic authentication will not work in its usual way. There is however a workaround. First add a .htaccess file with following code in it: <IfModule mod_rewrite.c> RewriteEngine on \n RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization},L] </IfModule> Next add the following line to your script right before the authentication: <syntaxhighlight lang="php">list($_SERVER['PHP_AUTH_USER'], $_SERVER['PHP_AUTH_PW']) = explode(':' , base64_decode(substr($_SERVER['HTTP_AUTHORIZATION'], 6)));</syntaxhighlight> Now your script should work with basic authentication. 1fde83d8017240ca738add5ea973443731b88a0c 609 608 2018-06-23T10:37:48Z Bert 8 wikitext text/x-wiki Because in our webserversetup PHP is installed as a FastCGI Proxy basic authentication will not work in its usual way. There is however a workaround. First add a .htaccess file with following code in it: <IfModule mod_rewrite.c> RewriteEngine on \n RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization},L] </IfModule> Next add the following line to your script right before the authentication: <syntaxhighlight lang="php">list($_SERVER['PHP_AUTH_USER'], $_SERVER['PHP_AUTH_PW']) = explode(':' , base64_decode(substr($_SERVER['HTTP_AUTHORIZATION'], 6)));</syntaxhighlight> Now your script should work with basic authentication. efceaa1595e6b1938ce4d7aea124b8a97c03c457 0 37 610 594 2018-06-23T10:38:53Z Bert 8 wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</pre> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' Do not place sensitive files inside the web accessible folder.Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.</div> It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [[Managing_Cron_jobs | cronjob]] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than were it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> Or, for Python 3: <pre>virtualenv ~/.venv --python=python3</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <pre><syntaxhighlight lang="php">#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </syntaxhighlight></pre> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [http://flask.pocoo.org/docs/0.10/deploying/fastcgi/ Flask documentation for FastCGI] bcbc92a4daac20088cfa7c375cad3ba83edfacbc 611 610 2018-06-23T10:39:27Z Bert 8 wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</pre> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' Do not place sensitive files inside the web accessible folder.Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.</div> It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [[Managing_Cron_jobs | cronjob]] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than were it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> Or, for Python 3: <pre>virtualenv ~/.venv --python=python3</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <syntaxhighlight lang="php"><pre>#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </pre></syntaxhighlight> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [http://flask.pocoo.org/docs/0.10/deploying/fastcgi/ Flask documentation for FastCGI] a004d366a007c3dab0cd1f445947b95e28e767b1 612 611 2018-06-23T10:39:55Z Bert 8 wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</pre> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' Do not place sensitive files inside the web accessible folder.Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.</div> It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [[Managing_Cron_jobs | cronjob]] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than were it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> Or, for Python 3: <pre>virtualenv ~/.venv --python=python3</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <syntaxhighlight lang="php">#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </syntaxhighlight> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [http://flask.pocoo.org/docs/0.10/deploying/fastcgi/ Flask documentation for FastCGI] d55d384d343085b543d8a02d4ef6b59f1254e45c 613 612 2018-06-23T10:40:15Z Bert 8 wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</pre> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' Do not place sensitive files inside the web accessible folder.Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.</div> It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [[Managing_Cron_jobs | cronjob]] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than were it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> Or, for Python 3: <pre>virtualenv ~/.venv --python=python3</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <syntaxhighlight lang="python">#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </syntaxhighlight> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [http://flask.pocoo.org/docs/0.10/deploying/fastcgi/ Flask documentation for FastCGI] 4a3c7ccc610dd04d39606bb68897a652b317da95 614 613 2018-06-23T10:44:33Z Bert 8 wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <syntaxhighlight lang="apache">Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</syntaxhighlight> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' Do not place sensitive files inside the web accessible folder.Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.</div> It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [[Managing_Cron_jobs | cronjob]] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than were it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> Or, for Python 3: <pre>virtualenv ~/.venv --python=python3</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <syntaxhighlight lang="python">#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </syntaxhighlight> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [http://flask.pocoo.org/docs/0.10/deploying/fastcgi/ Flask documentation for FastCGI] 6b89043ad8182b397c8c438ec7e0fbf701fdc216 0 33 615 534 2018-07-13T14:49:31Z Vincenttc 21 wikitext text/x-wiki Shibboleth is the software powering the Central KU Leuven Login. It's a piece of software used by many universities to supply identification and access management. ULYSSIS works together with ICTS to supply limited access to Shibboleth. We are however only able to supply Shibboleth to those approved by ICTS. In practice all faculty unions will be granted access if they can prove they have the technical ability to use Shibboleth in a safe and privacy friendly way. For other organisations it can be more difficult to get access, therefore it is best to write an extensive explenation of what you plan to do with Shibboleth, why your organisation requires it, what your organisation does, and other relevant information. We will then contact ICTS with your request. == How to request == To request Shibboleth access, you first need to make sure the domain you wish to use Shibboleth on has valid SSL certificates. Lately ICTS has been pushing that all traffic to the website is already over HTTPS before Shibboleth is issued. For more info you can check [[Getting SSL]] If you have SSL set up you need to send an email to request Shibboleth to ulyssis@ulyssis.org. The email must contain the following info: * What domain you wish to use Shibboleth on (this must be a single domain, so keep subdomains and www in mind) * What you will be using Shibboleth for and in general what your application will do. This explanation is required by ICTS. If you fail to convince them they will not grant your domain access. * What attributes you wish to use and what you will do with them (and whether you will store them). You can find the list of attributes on https://admin.kuleuven.be/icts/services/aai/attributes * Explicitly state you grant ULYSSIS permission to edit the .htaccess file to be able to export the required Shibboleth Metadata * If you are not a recognised faculty union you will need to include an extra motivation why you require Shibboleth (as noted above) If your application is complete and correct we will file a formal request. We will of course notify you of ICTS' response. == Deploying Shibboleth == After you have been granted access you can soon start using Shibboleth. The first step is to add the following lines to your .htaccess ShibDisable Off AuthType Shibboleth require shibboleth ShibRequireSession off We disable certain features of Shibboleth here because it will otherwise interfere with any other HTTP-auth options you might be using. Now that you have added this information to .htaccess you are able to serve requests to Shibboleth.sso, if your request is well-formed the sso will handle communication with the IdP (identity provider) of the KU Leuven. A login link follows the following syntax: https://[YOUR_HOSTNAME]/Shibboleth.sso/WAYF/kuleuven?target=[URLENCODED_RETURN_URL] And logout links: https://[YOUR_HOSTNAME]/Shibboleth.sso/Logout?return=[URLENCODED_DISPLAY_URL] It is important to note that on logout the user will stay on the KU Leuven's IdP-page and your link will only be displayed. The user will NOT be redirected (even though this is the normale behaviour according to the Shibboleth documentation). As soon as a user is logged in, his or hers attributes will be available to your application. Attributes are certain properties that an account may have and that supply further information about them. Some examples are: first name, last name, mail, student id. All of these will be available as HTTP headers. But keep in mind that apache might prefix those with REDIRECT_ multiple times (for example when mod_rewrite is used). For an overview of all attributes you can check out http://shib.kuleuven.be/secure/allAttributes More general information on the KU Leuvens implementation can be found on http://shib.kuleuven.be/ . But be aware of the fact that some of the documentation is very outdated (Most notably information about shib 1.3) 84dab635c97d7c7e4ad746ebcc8a11ed56cb171a 0 104 616 2018-07-16T09:21:58Z Lars 26 Created page with "PHP code is run with PHP-FPM as your ULYSSIS user. This means you can tighten up you website's security by denying other users the permission to read your PHP files. However,..." wikitext text/x-wiki PHP code is run with PHP-FPM as your ULYSSIS user. This means you can tighten up you website's security by denying other users the permission to read your PHP files. However, due to the way the Apache webserver works, it must be able to determine the existence of your PHP files. Non-PHP files in your www directory must remain readable by other users, because Apache reads these as it's own user. === Recommended security settings === * Homedirectory: <code>0701/drwx-----x</code> * www directory (and other directories from where websites are served): <code>0705/drwx---r-x</code> * Website files (css, images, html, ...): <code>0604/-rw----r--</code> * Configuration files containing secrets/passwords: <code>0600/-rw-------</code> * Other directories and files that are not part of a website: <code>0600/-rw-------</code> or <code>0700/-rwx------</code> === Securing database login info === Suppose you have a file called <code>config.php</code>, containing login information for your database. To secure this information, you can make it readable and writeable by only you, and nobody else using <code>chmod 600 config.php</code>. In FileZilla, you can do this by right-clicking on the config file, clicking on "File permissions...", and changing the permissions according to the following screenshots: [[File:config-php_dropdown.png]] [[File:config-php_attrs.png]] === Securing uploads directory === Also, if there are directories that you made writeable by others, e.g. an uploads folder, this is no longer necessary. If this directory is called <code>uploads</code>, you can remove write rights for others with <code>chmod go-w uploads</code>. In FileZilla, you can do this by right-clicking on the config file, clicking on "File permissions...", and changing the permissions according to the following screenshots: [[File:uploads_dropdown.png]] [[File:uploads_attrs.png]] 0f671bfa4b912ad18014236dcd366dd30275cc5f 617 616 2018-07-16T09:22:09Z Lars 26 wikitext text/x-wiki PHP code is run with PHP-FPM as your ULYSSIS user. This means you can tighten up you website's security by denying other users the permission to read your PHP files. However, due to the way the Apache webserver works, it must be able to determine the existence of your PHP files. Non-PHP files in your www directory must remain readable by other users, because Apache reads these as it's own user. === Recommended security settings === * Homedirectory: <code>0701/drwx-----x</code> * www directory (and other directories from where websites are served): <code>0705/drwx---r-x</code> * Website files (css, images, html, ...): <code>0604/-rw----r--</code> * Configuration files containing secrets/passwords: <code>0600/-rw-------</code> * Other directories and files that are not part of a website: <code>0600/-rw-------</code> or <code>0700/-rwx------</code> === Securing database login info === Suppose you have a file called <code>config.php</code>, containing login information for your database. To secure this information, you can make it readable and writeable by only you, and nobody else using <code>chmod 600 config.php</code>. In FileZilla, you can do this by right-clicking on the config file, clicking on "File permissions...", and changing the permissions according to the following screenshots: [[File:config-php_dropdown.png]] [[File:config-php_attrs.png]] === Securing uploads directory === Also, if there are directories that you made writeable by others, e.g. an uploads folder, this is no longer necessary. If this directory is called <code>uploads</code>, you can remove write rights for others with <code>chmod go-w uploads</code>. In FileZilla, you can do this by right-clicking on the config file, clicking on "File permissions...", and changing the permissions according to the following screenshots: [[File:uploads_dropdown.png]] [[File:uploads_attrs.png]] 786265f4e33b421a13355f3d02c98597c3d3d873 618 617 2018-07-16T09:22:41Z Lars 26 /* Recommended security settings */ wikitext text/x-wiki PHP code is run with PHP-FPM as your ULYSSIS user. This means you can tighten up you website's security by denying other users the permission to read your PHP files. However, due to the way the Apache webserver works, it must be able to determine the existence of your PHP files. Non-PHP files in your www directory must remain readable by other users, because Apache reads these as it's own user. === Recommended security settings === * Homedirectory: <code>0701/drwx-----x</code> * www directory (and other directories from where websites are served), including subdirectories: <code>0705/drwx---r-x</code> * Website files (css, images, html, ...): <code>0604/-rw----r--</code> * Configuration files containing secrets/passwords: <code>0600/-rw-------</code> * Other directories and files that are not part of a website: <code>0600/-rw-------</code> or <code>0700/-rwx------</code> === Securing database login info === Suppose you have a file called <code>config.php</code>, containing login information for your database. To secure this information, you can make it readable and writeable by only you, and nobody else using <code>chmod 600 config.php</code>. In FileZilla, you can do this by right-clicking on the config file, clicking on "File permissions...", and changing the permissions according to the following screenshots: [[File:config-php_dropdown.png]] [[File:config-php_attrs.png]] === Securing uploads directory === Also, if there are directories that you made writeable by others, e.g. an uploads folder, this is no longer necessary. If this directory is called <code>uploads</code>, you can remove write rights for others with <code>chmod go-w uploads</code>. In FileZilla, you can do this by right-clicking on the config file, clicking on "File permissions...", and changing the permissions according to the following screenshots: [[File:uploads_dropdown.png]] [[File:uploads_attrs.png]] 978a8be7aebc67bbc9bf0b639cf2f5c8828a6d75 619 618 2018-07-16T09:23:44Z Lars 26 wikitext text/x-wiki PHP code is run with PHP-FPM as your ULYSSIS user. This means you can tighten up you website's security by denying other users the permission to read your PHP files. However, due to the way the Apache webserver works, it must be able to determine the existence of your PHP files. Non-PHP files in your www directory must remain readable by other users, because Apache reads these as it's own user. === Recommended permissions === * Homedirectory: <code>0701/drwx-----x</code> * www directory (and other directories from where websites are served), including subdirectories: <code>0705/drwx---r-x</code> * Website files (css, images, html, ...): <code>0604/-rw----r--</code> * Configuration files containing secrets/passwords: <code>0600/-rw-------</code> * Other directories and files that are not part of a website: <code>0600/-rw-------</code> or <code>0700/-rwx------</code> === Securing database login info === Suppose you have a file called <code>config.php</code>, containing login information for your database. To secure this information, you can make it readable and writeable by only you, and nobody else using <code>chmod 600 config.php</code>. In FileZilla, you can do this by right-clicking on the config file, clicking on "File permissions...", and changing the permissions according to the following screenshots: [[File:config-php_dropdown.png]] [[File:config-php_attrs.png]] === Securing uploads directory === Also, if there are directories that you made writeable by others, e.g. an uploads folder, this is no longer necessary. If this directory is called <code>uploads</code>, you can remove write rights for others with <code>chmod go-w uploads</code>. In FileZilla, you can do this by right-clicking on the config file, clicking on "File permissions...", and changing the permissions according to the following screenshots: [[File:uploads_dropdown.png]] [[File:uploads_attrs.png]] 044777fb45ded38e8725fd7fb8880e674c0b8e8b 623 619 2018-07-19T08:00:10Z Vincenttc 21 wikitext text/x-wiki PHP code is run with PHP-FPM as your ULYSSIS user. This means you can tighten up you website's security by denying other users the permission to read your PHP files. However, due to the way the Apache webserver works, it must be able to determine the existence of your PHP files. Non-PHP files in your www directory must remain readable by other users, because Apache reads these as it's own user. === Recommended permissions === * Homedirectory: See [[#homedirectory | homedirectory]] * www directory (and other directories from where websites are served), including subdirectories: <code>0705/drwx---r-x</code> * Website files (css, images, html, ...): <code>0604/-rw----r--</code> * Configuration files containing secrets/passwords: <code>0600/-rw-------</code> * Other directories and files that are not part of a website: <code>0600/-rw-------</code> or <code>0700/-rwx------</code> === Securing database login info === Suppose you have a file called <code>config.php</code>, containing login information for your database. To secure this information, you can make it readable and writeable by only you, and nobody else using <code>chmod 600 config.php</code>. In FileZilla, you can do this by right-clicking on the config file, clicking on "File permissions...", and changing the permissions according to the following screenshots: [[File:config-php_dropdown.png]] [[File:config-php_attrs.png]] === Securing uploads directory === Also, if there are directories that you made writeable by others, e.g. an uploads folder, this is no longer necessary. If this directory is called <code>uploads</code>, you can remove write rights for others with <code>chmod go-w uploads</code>. In FileZilla, you can do this by right-clicking on the config file, clicking on "File permissions...", and changing the permissions according to the following screenshots: === Homedirectory permissions === In order to prevent other users entirely from accessing files in your homedirectory, the permissions on your homedirectory should only allow yourself and the www-data user access. This is by default configured properly for you from the 29th of July, 2018 onward. Note that you should still follow the guidelines as detailed above. If you have changed your permissions on your homedirectory and want to restore the defaults, you can execute <code>nfs4_setfacl -s /home/user/acl ~</code>. The file <code>/home/user/acl</code> contains the default permissions. [[File:uploads_dropdown.png]] [[File:uploads_attrs.png]] b98007fed7c35de9b655bd7bf2f3d55e253450ca 624 623 2018-07-19T08:00:23Z Vincenttc 21 wikitext text/x-wiki PHP code is run with PHP-FPM as your ULYSSIS user. This means you can tighten up you website's security by denying other users the permission to read your PHP files. However, due to the way the Apache webserver works, it must be able to determine the existence of your PHP files. Non-PHP files in your www directory must remain readable by other users, because Apache reads these as it's own user. === Recommended permissions === * Homedirectory: See [[#homedirectory_permissions | homedirectory]] * www directory (and other directories from where websites are served), including subdirectories: <code>0705/drwx---r-x</code> * Website files (css, images, html, ...): <code>0604/-rw----r--</code> * Configuration files containing secrets/passwords: <code>0600/-rw-------</code> * Other directories and files that are not part of a website: <code>0600/-rw-------</code> or <code>0700/-rwx------</code> === Securing database login info === Suppose you have a file called <code>config.php</code>, containing login information for your database. To secure this information, you can make it readable and writeable by only you, and nobody else using <code>chmod 600 config.php</code>. In FileZilla, you can do this by right-clicking on the config file, clicking on "File permissions...", and changing the permissions according to the following screenshots: [[File:config-php_dropdown.png]] [[File:config-php_attrs.png]] === Securing uploads directory === Also, if there are directories that you made writeable by others, e.g. an uploads folder, this is no longer necessary. If this directory is called <code>uploads</code>, you can remove write rights for others with <code>chmod go-w uploads</code>. In FileZilla, you can do this by right-clicking on the config file, clicking on "File permissions...", and changing the permissions according to the following screenshots: === Homedirectory permissions === In order to prevent other users entirely from accessing files in your homedirectory, the permissions on your homedirectory should only allow yourself and the www-data user access. This is by default configured properly for you from the 29th of July, 2018 onward. Note that you should still follow the guidelines as detailed above. If you have changed your permissions on your homedirectory and want to restore the defaults, you can execute <code>nfs4_setfacl -s /home/user/acl ~</code>. The file <code>/home/user/acl</code> contains the default permissions. [[File:uploads_dropdown.png]] [[File:uploads_attrs.png]] 770d9d605bf7205311b3a4ade508720a8a311603 625 624 2018-07-19T08:01:38Z Vincenttc 21 /* Recommended permissions */ wikitext text/x-wiki PHP code is run with PHP-FPM as your ULYSSIS user. This means you can tighten up you website's security by denying other users the permission to read your PHP files. However, due to the way the Apache webserver works, it must be able to determine the existence of your PHP files. Non-PHP files in your www directory must remain readable by other users, because Apache reads these as it's own user. === Recommended permissions === * Homedirectory: See [[#homedirectory permissions | homedirectory]] * www directory (and other directories from where websites are served), including subdirectories: <code>0705/drwx---r-x</code> * Website files (css, images, html, ...): <code>0604/-rw----r--</code> * Configuration files containing secrets/passwords: <code>0600/-rw-------</code> * Other directories and files that are not part of a website: <code>0600/-rw-------</code> or <code>0700/-rwx------</code> === Securing database login info === Suppose you have a file called <code>config.php</code>, containing login information for your database. To secure this information, you can make it readable and writeable by only you, and nobody else using <code>chmod 600 config.php</code>. In FileZilla, you can do this by right-clicking on the config file, clicking on "File permissions...", and changing the permissions according to the following screenshots: [[File:config-php_dropdown.png]] [[File:config-php_attrs.png]] === Securing uploads directory === Also, if there are directories that you made writeable by others, e.g. an uploads folder, this is no longer necessary. If this directory is called <code>uploads</code>, you can remove write rights for others with <code>chmod go-w uploads</code>. In FileZilla, you can do this by right-clicking on the config file, clicking on "File permissions...", and changing the permissions according to the following screenshots: === Homedirectory permissions === In order to prevent other users entirely from accessing files in your homedirectory, the permissions on your homedirectory should only allow yourself and the www-data user access. This is by default configured properly for you from the 29th of July, 2018 onward. Note that you should still follow the guidelines as detailed above. If you have changed your permissions on your homedirectory and want to restore the defaults, you can execute <code>nfs4_setfacl -s /home/user/acl ~</code>. The file <code>/home/user/acl</code> contains the default permissions. [[File:uploads_dropdown.png]] [[File:uploads_attrs.png]] dc954275c1ffc708247c43ea716fcd73ebe0085d 626 625 2018-07-19T08:01:56Z Vincenttc 21 /* Recommended permissions */ wikitext text/x-wiki PHP code is run with PHP-FPM as your ULYSSIS user. This means you can tighten up you website's security by denying other users the permission to read your PHP files. However, due to the way the Apache webserver works, it must be able to determine the existence of your PHP files. Non-PHP files in your www directory must remain readable by other users, because Apache reads these as it's own user. === Recommended permissions === * Homedirectory: See [[#Homedirectory permissions | homedirectory]] * www directory (and other directories from where websites are served), including subdirectories: <code>0705/drwx---r-x</code> * Website files (css, images, html, ...): <code>0604/-rw----r--</code> * Configuration files containing secrets/passwords: <code>0600/-rw-------</code> * Other directories and files that are not part of a website: <code>0600/-rw-------</code> or <code>0700/-rwx------</code> === Securing database login info === Suppose you have a file called <code>config.php</code>, containing login information for your database. To secure this information, you can make it readable and writeable by only you, and nobody else using <code>chmod 600 config.php</code>. In FileZilla, you can do this by right-clicking on the config file, clicking on "File permissions...", and changing the permissions according to the following screenshots: [[File:config-php_dropdown.png]] [[File:config-php_attrs.png]] === Securing uploads directory === Also, if there are directories that you made writeable by others, e.g. an uploads folder, this is no longer necessary. If this directory is called <code>uploads</code>, you can remove write rights for others with <code>chmod go-w uploads</code>. In FileZilla, you can do this by right-clicking on the config file, clicking on "File permissions...", and changing the permissions according to the following screenshots: === Homedirectory permissions === In order to prevent other users entirely from accessing files in your homedirectory, the permissions on your homedirectory should only allow yourself and the www-data user access. This is by default configured properly for you from the 29th of July, 2018 onward. Note that you should still follow the guidelines as detailed above. If you have changed your permissions on your homedirectory and want to restore the defaults, you can execute <code>nfs4_setfacl -s /home/user/acl ~</code>. The file <code>/home/user/acl</code> contains the default permissions. [[File:uploads_dropdown.png]] [[File:uploads_attrs.png]] 39826e064a2ff869c642e3cf23c96f03b00d234e 627 626 2018-07-19T08:02:28Z Vincenttc 21 /* Homedirectory permissions */ wikitext text/x-wiki PHP code is run with PHP-FPM as your ULYSSIS user. This means you can tighten up you website's security by denying other users the permission to read your PHP files. However, due to the way the Apache webserver works, it must be able to determine the existence of your PHP files. Non-PHP files in your www directory must remain readable by other users, because Apache reads these as it's own user. === Recommended permissions === * Homedirectory: See [[#Homedirectory permissions | homedirectory]] * www directory (and other directories from where websites are served), including subdirectories: <code>0705/drwx---r-x</code> * Website files (css, images, html, ...): <code>0604/-rw----r--</code> * Configuration files containing secrets/passwords: <code>0600/-rw-------</code> * Other directories and files that are not part of a website: <code>0600/-rw-------</code> or <code>0700/-rwx------</code> === Securing database login info === Suppose you have a file called <code>config.php</code>, containing login information for your database. To secure this information, you can make it readable and writeable by only you, and nobody else using <code>chmod 600 config.php</code>. In FileZilla, you can do this by right-clicking on the config file, clicking on "File permissions...", and changing the permissions according to the following screenshots: [[File:config-php_dropdown.png]] [[File:config-php_attrs.png]] === Securing uploads directory === Also, if there are directories that you made writeable by others, e.g. an uploads folder, this is no longer necessary. If this directory is called <code>uploads</code>, you can remove write rights for others with <code>chmod go-w uploads</code>. In FileZilla, you can do this by right-clicking on the config file, clicking on "File permissions...", and changing the permissions according to the following screenshots: [[File:uploads_dropdown.png]] [[File:uploads_attrs.png]] === Homedirectory permissions === In order to prevent other users entirely from accessing files in your homedirectory, the permissions on your homedirectory should only allow yourself and the www-data user access. This is by default configured properly for you from the 29th of July, 2018 onward. Note that you should still follow the guidelines as detailed above. If you have changed your permissions on your homedirectory and want to restore the defaults, you can execute <code>nfs4_setfacl -s /home/user/acl ~</code>. The file <code>/home/user/acl</code> contains the default permissions. 7491f3d9268ca02b90929d8f1a8c0233c5aebdc2 628 627 2018-07-26T19:25:51Z Vincenttc 21 /* Homedirectory permissions */ wikitext text/x-wiki PHP code is run with PHP-FPM as your ULYSSIS user. This means you can tighten up you website's security by denying other users the permission to read your PHP files. However, due to the way the Apache webserver works, it must be able to determine the existence of your PHP files. Non-PHP files in your www directory must remain readable by other users, because Apache reads these as it's own user. === Recommended permissions === * Homedirectory: See [[#Homedirectory permissions | homedirectory]] * www directory (and other directories from where websites are served), including subdirectories: <code>0705/drwx---r-x</code> * Website files (css, images, html, ...): <code>0604/-rw----r--</code> * Configuration files containing secrets/passwords: <code>0600/-rw-------</code> * Other directories and files that are not part of a website: <code>0600/-rw-------</code> or <code>0700/-rwx------</code> === Securing database login info === Suppose you have a file called <code>config.php</code>, containing login information for your database. To secure this information, you can make it readable and writeable by only you, and nobody else using <code>chmod 600 config.php</code>. In FileZilla, you can do this by right-clicking on the config file, clicking on "File permissions...", and changing the permissions according to the following screenshots: [[File:config-php_dropdown.png]] [[File:config-php_attrs.png]] === Securing uploads directory === Also, if there are directories that you made writeable by others, e.g. an uploads folder, this is no longer necessary. If this directory is called <code>uploads</code>, you can remove write rights for others with <code>chmod go-w uploads</code>. In FileZilla, you can do this by right-clicking on the config file, clicking on "File permissions...", and changing the permissions according to the following screenshots: [[File:uploads_dropdown.png]] [[File:uploads_attrs.png]] === Homedirectory permissions === In order to prevent other users entirely from accessing files in your homedirectory, the permissions on your homedirectory should only allow yourself and the www-data user access. This is by default configured properly for you from the 29th of July, 2018 onward. Note that you should still follow the guidelines as detailed above. If you have changed your permissions on your homedirectory and want to restore the defaults, you can execute <code>nfs4_setfacl -S /home/user/acl ~</code>. The file <code>/home/user/acl</code> contains the default permissions. 642be949b7d45240788a9438b2cdbbcd1737bfd2 6 105 629 2018-08-04T17:14:03Z Lars 26 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 106 630 2018-08-04T17:14:22Z Lars 26 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 107 631 2018-08-04T17:14:42Z Lars 26 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 108 633 2018-08-27T18:10:11Z Yoa 30 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 634 633 2018-08-27T18:15:13Z Yoa 30 Yoa uploaded a new version of [[File:MySQL Workbench SSH.png]] wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 6 635 539 2018-08-27T18:16:07Z Yoa 30 /* Accessing MySQL from outside of our network */ wikitext text/x-wiki ==Creating a MySQL user== To use MySQL on your ULYSSIS account you first need to create a MySQL user on [https://ucc.ulyssis.org UCC]. In the MySQL section of the panel you will be suggested to click a link to create a user. Then fill in a password for the database user. It is highly recommended that this password differs from the password you use for your account. Then you just click ''Create user'' and you are ready to go. ==Creating a MySQL database== After creating a MySQL user, you can simple press ''Add database'' in [https://ucc.ulyssis.org UCC] and enter the name for your new database. It will automatically be prefixed by your username. ==Using MySQL for your website or application== Host: mysql.ulyssis.org Username: your account's username Password: the password you chose when you made the MySQL user Database: the database name you chose, prefixed by your username For example, if my username is foobar, I made a database called website and I were to create a PHP website I would use something like: <syntaxhighlight lang="php">$db = new mysqli('mysql.ulyssis.org', 'foobar', 'correct horse battery staple', 'foobar_website');</syntaxhighlight> or <syntaxhighlight lang="php">$db = new PDO('mysql:host=mysql.ulyssis.org;dbname=foobar_website', 'foobar', 'correct horse battery staple');</syntaxhighlight> ==Managing MySQL with PHPMyAdmin== Using your username and password you can easily manage your MySQL databases, tables and records on https://phpmyadmin.ulyssis.org ==Accessing MySQL from outside of our network== To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH-tunnel. In many MySQL management tools this is already supported. === MySQL Workbench === While [https://www.mysql.com/products/workbench/ MySQL Workbench] might not fully support our MySQL database, all commonly used operations work perfectly. You can connect to our database using MySQL Workbench by creating a connection as follows ([username] should be replaced by your username, of course): [[File:MySQL_Workbench_SSH.png]] === Linux, Mac OSX === On Linux, Mac OSX and other Unix-like Operating Systems it is also easily possible to use the following command to create a tunnel to a local port (in this case 3300) ssh -f username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N While this command is running, you can connect to the MySQL server with host 'localhost' and port '3300'. To terminate the port forwarding, press ctrl-C in the terminal. 6589760f6602e0b0e25109a6ddb741321ec1aa1f 653 635 2018-11-05T11:41:33Z Andreas 20 /* Linux, Mac OSX */ wikitext text/x-wiki ==Creating a MySQL user== To use MySQL on your ULYSSIS account you first need to create a MySQL user on [https://ucc.ulyssis.org UCC]. In the MySQL section of the panel you will be suggested to click a link to create a user. Then fill in a password for the database user. It is highly recommended that this password differs from the password you use for your account. Then you just click ''Create user'' and you are ready to go. ==Creating a MySQL database== After creating a MySQL user, you can simple press ''Add database'' in [https://ucc.ulyssis.org UCC] and enter the name for your new database. It will automatically be prefixed by your username. ==Using MySQL for your website or application== Host: mysql.ulyssis.org Username: your account's username Password: the password you chose when you made the MySQL user Database: the database name you chose, prefixed by your username For example, if my username is foobar, I made a database called website and I were to create a PHP website I would use something like: <syntaxhighlight lang="php">$db = new mysqli('mysql.ulyssis.org', 'foobar', 'correct horse battery staple', 'foobar_website');</syntaxhighlight> or <syntaxhighlight lang="php">$db = new PDO('mysql:host=mysql.ulyssis.org;dbname=foobar_website', 'foobar', 'correct horse battery staple');</syntaxhighlight> ==Managing MySQL with PHPMyAdmin== Using your username and password you can easily manage your MySQL databases, tables and records on https://phpmyadmin.ulyssis.org ==Accessing MySQL from outside of our network== To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH-tunnel. In many MySQL management tools this is already supported. === MySQL Workbench === While [https://www.mysql.com/products/workbench/ MySQL Workbench] might not fully support our MySQL database, all commonly used operations work perfectly. You can connect to our database using MySQL Workbench by creating a connection as follows ([username] should be replaced by your username, of course): [[File:MySQL_Workbench_SSH.png]] === Linux, Mac OSX === On Linux, Mac OSX and other Unix-like Operating Systems it is also easily possible to use the following command to create a tunnel to a local port (in this case 3300) ssh username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N While this command is running, you can connect to the MySQL server with host 'localhost' and port '3300'. To terminate the port forwarding, press ctrl-C in the terminal. You can use "ssh -f username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N": the f-argument will put the command in the background. 079a23cbb0bd2d6b41706efa117222cc5fb78db3 0 20 637 533 2018-09-26T15:28:40Z Yoa 30 /* How to install Wordpress for your account */ wikitext text/x-wiki ==How to install Wordpress for your account== First you will need to download Wordpress from their website, https://wordpress.org. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. The files that you've extracted will need to be moved to your `www` directory on your shell account. You can do this by copying them there using Filezilla or any other FTP client. After you've copied those files to your `www` directory, you'll have to go to your account on *your username here*.ulyssis.be. You will then receive a notification telling you your <code>wp-config.php</code> has to be created. The easiest way to do this is by following the wizard, so you can click on "Create a configuration file". Go through to the wizard until it prompts you for your database configuration: *'''Database Name/Databasenaam:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll have to create it here. The default database is: "username_username". *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is <code>mysql.ulyssis.org</code> or <code>postgresql.ulyssis.org</code>. It depends on whether you want to use a MySQL or PostgreSQL database. * You don't need to change the last field. After that you can proceed in the wizard where you can fill in some last few details. By then the wizard will do the rest and, congratulations, you have installed Wordpress. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you will need to create a new folder in your www-directory on your shell account. Then you'll need a virtual host for this folder, so you'll have to send us an email asking for this. After your new virtual host has been configured, you will need to do the same steps that you would need to do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about it [https://wordpress.org/support/forum/multisite here]. 67da23b57e043c6db39f8d44714b568279511fc7 0 19 638 601 2018-10-10T14:48:38Z Bert 8 Bert moved page [[ULYSSIS mail]] to [[Mailbox]] without leaving a redirect wikitext text/x-wiki Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mail regularly, because all important information will be sent to this address. You can check your e-mail using the webmail or an email client of your own. ==Webmail== You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to enter the website. ==POP and IMAP access== You can access your ulyssis mail by POP or IMAP protocol. The configuration parameters are: * '''server''': <tt>mail.ulyssis.org</tt> * '''username''': ''your ULYSSIS username'' * '''password''': ''your ULYSSIS password'' * '''security''': SSL ==SMTP== ULYSSIS doesn't offer SMTP. Instead, you can use KULeuven's SMTP server: * '''server''': <tt>smtps.kuleuven.be</tt> * '''port''': 443 * '''username''': ''your student id'' * '''password''': ''your KULeuven password'' * '''security''': SSL == Advanced == Your emails are stored within your account under ~/Maildir. These files can of course be read with a command line email client such as alpine or mutt. We support sendmail style local delivery using .forward. More information is available in the official documentation of [https://www.sendmail.org/~ca/email/doc8.9/op-sh-2.html#sh-2.8 Sendmail] and [http://www.postfix.org/local.8.html Postfix]. You can also use procmail on our servers. A very detailed explanation on procmail is available on the [https://wiki.archlinux.org/index.php/Procmail ArchWiki]. cfb54f397a6325e547061b4b1044132c565c7b34 640 638 2018-10-10T14:49:33Z Bert 8 wikitext text/x-wiki Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mailbox regularly, because all important information will be sent to this address. You can check your e-mail using the webmail or an email client of your own. ==Webmail== You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to enter the website. ==POP and IMAP access== You can access your ulyssis mail by POP or IMAP protocol. The configuration parameters are: * '''server''': <tt>mail.ulyssis.org</tt> * '''username''': ''your ULYSSIS username'' * '''password''': ''your ULYSSIS password'' * '''security''': SSL ==SMTP== ULYSSIS doesn't offer SMTP. Instead, you can use KULeuven's SMTP server: * '''server''': <tt>smtps.kuleuven.be</tt> * '''port''': 443 * '''username''': ''your student id'' * '''password''': ''your KULeuven password'' * '''security''': SSL == Advanced == Your emails are stored within your account under ~/Maildir. These files can of course be read with a command line email client such as alpine or mutt. We support sendmail style local delivery using .forward. More information is available in the official documentation of [https://www.sendmail.org/~ca/email/doc8.9/op-sh-2.html#sh-2.8 Sendmail] and [http://www.postfix.org/local.8.html Postfix]. You can also use procmail on our servers. A very detailed explanation on procmail is available on the [https://wiki.archlinux.org/index.php/Procmail ArchWiki]. 7310b4db0d090642858bdf3b8ec187ccf0865056 641 640 2018-10-10T14:50:34Z Bert 8 wikitext text/x-wiki Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mailbox regularly, because all important information will be sent to this address. You can check your e-mail using the webmail or an email client of your own. It is also possible to configure your email address in UCC to automatically forward all correspondence to another address. ==Webmail== You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to enter the website. ==POP and IMAP access== You can access your ulyssis mail by POP or IMAP protocol. The configuration parameters are: * '''server''': <tt>mail.ulyssis.org</tt> * '''username''': ''your ULYSSIS username'' * '''password''': ''your ULYSSIS password'' * '''security''': SSL ==SMTP== ULYSSIS doesn't offer SMTP. Instead, you can use KULeuven's SMTP server: * '''server''': <tt>smtps.kuleuven.be</tt> * '''port''': 443 * '''username''': ''your student id'' * '''password''': ''your KULeuven password'' * '''security''': SSL == Advanced == Your emails are stored within your account under ~/Maildir. These files can of course be read with a command line email client such as alpine or mutt. We support sendmail style local delivery using .forward. More information is available in the official documentation of [https://www.sendmail.org/~ca/email/doc8.9/op-sh-2.html#sh-2.8 Sendmail] and [http://www.postfix.org/local.8.html Postfix]. You can also use procmail on our servers. A very detailed explanation on procmail is available on the [https://wiki.archlinux.org/index.php/Procmail ArchWiki]. 6fb527c1e5bf0ca505b046002ed5e50148743934 642 641 2018-10-10T14:51:14Z Bert 8 wikitext text/x-wiki Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mailbox regularly, because all important information will be sent to this address. You can check your e-mail using the webmail or an email client of your own. It is also possible to configure your email address in UCC to automatically [[forward Forwarders]] all correspondence to another address. ==Webmail== You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to enter the website. ==POP and IMAP access== You can access your ulyssis mail by POP or IMAP protocol. The configuration parameters are: * '''server''': <tt>mail.ulyssis.org</tt> * '''username''': ''your ULYSSIS username'' * '''password''': ''your ULYSSIS password'' * '''security''': SSL ==SMTP== ULYSSIS doesn't offer SMTP. Instead, you can use KULeuven's SMTP server: * '''server''': <tt>smtps.kuleuven.be</tt> * '''port''': 443 * '''username''': ''your student id'' * '''password''': ''your KULeuven password'' * '''security''': SSL == Advanced == Your emails are stored within your account under ~/Maildir. These files can of course be read with a command line email client such as alpine or mutt. We support sendmail style local delivery using .forward. More information is available in the official documentation of [https://www.sendmail.org/~ca/email/doc8.9/op-sh-2.html#sh-2.8 Sendmail] and [http://www.postfix.org/local.8.html Postfix]. You can also use procmail on our servers. A very detailed explanation on procmail is available on the [https://wiki.archlinux.org/index.php/Procmail ArchWiki]. bd34582f173b162f33653bbf13299404ccf17f8e 643 642 2018-10-10T15:37:38Z Bert 8 wikitext text/x-wiki Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mailbox regularly, because all important information will be sent to this address. You can check your e-mail using the webmail or an email client of your own. It is also possible to configure your email address in UCC to automatically [[Forwarders|forward]] all correspondence to another address. ==Webmail== You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to enter the website. ==POP and IMAP access== You can access your ulyssis mail by POP or IMAP protocol. The configuration parameters are: * '''server''': <tt>mail.ulyssis.org</tt> * '''username''': ''your ULYSSIS username'' * '''password''': ''your ULYSSIS password'' * '''security''': SSL ==SMTP== ULYSSIS doesn't offer SMTP. Instead, you can use KULeuven's SMTP server: * '''server''': <tt>smtps.kuleuven.be</tt> * '''port''': 443 * '''username''': ''your student id'' * '''password''': ''your KULeuven password'' * '''security''': SSL == Advanced == Your emails are stored within your account under ~/Maildir. These files can of course be read with a command line email client such as alpine or mutt. We support sendmail style local delivery using .forward. More information is available in the official documentation of [https://www.sendmail.org/~ca/email/doc8.9/op-sh-2.html#sh-2.8 Sendmail] and [http://www.postfix.org/local.8.html Postfix]. You can also use procmail on our servers. A very detailed explanation on procmail is available on the [https://wiki.archlinux.org/index.php/Procmail ArchWiki]. 24ee24113ab3768e36a02b41848a50ad57d0fda8 0 109 646 2018-10-11T00:08:57Z Bert 8 Created page with "By default, any ULYSSIS account comes with a single email address, specifically your username on our main domain, ulyssis.org: <code>''username''@ulyssis.org</code>. You can e..." wikitext text/x-wiki By default, any ULYSSIS account comes with a single email address, specifically your username on our main domain, ulyssis.org: <code>''username''@ulyssis.org</code>. You can either use this address as your only mailbox, or as a forwarder to another email address. You can find more information about your mailbox [[Mailbox|here]]. For any other addresses, you will need a domain (for example a .com or .be). It is possible to have a domain already connected to your ULYSSIS account as a regular website, but not activated for email. It is also possible to use a domain just for email and not for a website. More information about adding and activating domains can be found [[Adding_domain_names|here]]. Keep in mind ULYSSIS does not currently sell domains. If you have an email domain activated on your account, you will be able to add [[forwarders]] in our control panel [[https://ucc.ulyssis.org|UCC]]. You can create as many forwarders as you like, and have the addresses forward to a single address or several. Lots of organisations use forwarders as an easy way to contact a team of people responsible for a certain task, for example your PR team or the president of your organisation. Since forwarders relay emails to one or several addresses, you may want to reply using the forwarder address instead of your personal one. In that case you want to [[Using_a_forwarder_as_an_alias|add an alias]]. We offer instructions for our own webmail, the Thunderbird email client, Gmail and Hotmail/Outlook.com. Currently we do not offer mailboxes for your own domains, only the single mailbox that comes with your account by default. If you have any further questions about email, you can always contact our team at ulyssis@ulyssis.org c2b0a3f275bf5b92ee4306ca22c956d97d3fd756 647 646 2018-10-11T00:09:09Z Bert 8 wikitext text/x-wiki By default, any ULYSSIS account comes with a single email address, specifically your username on our main domain, ulyssis.org: <code>''username''@ulyssis.org</code>. You can either use this address as your only mailbox, or as a forwarder to another email address. You can find more information about your mailbox [[Mailbox|here]]. For any other addresses, you will need a domain (for example a .com or .be). It is possible to have a domain already connected to your ULYSSIS account as a regular website, but not activated for email. It is also possible to use a domain just for email and not for a website. More information about adding and activating domains can be found [[Adding_domain_names|here]]. Keep in mind ULYSSIS does not currently sell domains. If you have an email domain activated on your account, you will be able to add [[forwarders]] in our control panel [https://ucc.ulyssis.org|UCC]. You can create as many forwarders as you like, and have the addresses forward to a single address or several. Lots of organisations use forwarders as an easy way to contact a team of people responsible for a certain task, for example your PR team or the president of your organisation. Since forwarders relay emails to one or several addresses, you may want to reply using the forwarder address instead of your personal one. In that case you want to [[Using_a_forwarder_as_an_alias|add an alias]]. We offer instructions for our own webmail, the Thunderbird email client, Gmail and Hotmail/Outlook.com. Currently we do not offer mailboxes for your own domains, only the single mailbox that comes with your account by default. If you have any further questions about email, you can always contact our team at ulyssis@ulyssis.org 65a70b323d1486c446816697193ed2f7f3fc6deb 648 647 2018-10-11T00:09:54Z Bert 8 wikitext text/x-wiki By default, any ULYSSIS account comes with a single email address, specifically your username on our main domain, ulyssis.org: <code>''username''@ulyssis.org</code>. You can either use this address as your only mailbox, or as a forwarder to another email address. You can find more information about your mailbox [[Mailbox|here]]. For any other addresses, you will need a domain (for example a .com or .be). It is possible to have a domain already connected to your ULYSSIS account as a regular website, but not activated for email. It is also possible to use a domain just for email and not for a website. More information about adding and activating domains can be found [[Adding_domain_names|here]]. Keep in mind ULYSSIS does not currently sell domains. If you have an email domain activated on your account, you will be able to add [[forwarders]] in our control panel [https://ucc.ulyssis.org UCC]. You can create as many forwarders as you like, and have the addresses forward to a single address or several. Lots of organisations use forwarders as an easy way to contact a team of people responsible for a certain task, for example your PR team or the president of your organisation. Since forwarders relay emails to one or several addresses, you may want to reply using the forwarder address instead of your personal one. In that case you want to [[Using_a_forwarder_as_an_alias|add an alias]]. We offer instructions for our own webmail, the Thunderbird email client, Gmail and Hotmail/Outlook.com. Currently we do not offer mailboxes for your own domains, only the single mailbox that comes with your account by default. If you have any further questions about email, you can always contact our team at ulyssis@ulyssis.org 8efe252d8b3c6f05864d63b0e7ccebf9c9fd1c15 649 648 2018-10-11T00:11:00Z Bert 8 wikitext text/x-wiki By default, any ULYSSIS account comes with a single email address, specifically your username on our main domain, ulyssis.org: <code>''username''@ulyssis.org</code>. You can either use this address as your only mailbox, or as a forwarder to another email address. You can find more information about your mailbox [[Mailbox|here]]. For any other addresses, you will need a domain (for example a .com or .be). It is possible to have a domain already connected to your ULYSSIS account as a regular website, but not activated for email. It is also possible to use a domain just for email and not for a website. More information about adding and activating domains can be found [[Adding_domain_names|here]]. Keep in mind ULYSSIS does not currently sell domains, but you can buy them from lots of different companies. If you have an email domain activated on your account, you will be able to add [[forwarders]] in our control panel [https://ucc.ulyssis.org UCC]. You can create as many forwarders as you like, and have the addresses forward to a single address or several. Lots of organisations use forwarders as an easy way to contact a team of people responsible for a certain task, for example your PR team or the president of your organisation. Since forwarders relay emails to one or several addresses, you may want to reply using the forwarder address instead of your personal one. In that case you want to [[Using_a_forwarder_as_an_alias|add an alias]]. We offer instructions for our own webmail, the Thunderbird email client, Gmail and Hotmail/Outlook.com. Currently we do not offer mailboxes for your own domains, only the single mailbox that comes with your account by default. If you have any further questions about email, you can always contact our team at ulyssis@ulyssis.org ebbad3b5fd1bad90cab92d86b9ad6f39778489b0 650 649 2018-10-11T00:13:10Z Bert 8 wikitext text/x-wiki By default, any ULYSSIS account comes with a single email address, specifically your username on our main domain, ulyssis.org: <code>''username''@ulyssis.org</code>. You can either use this address as your only mailbox, or as a forwarder to another email address. You can find more information about your mailbox [[Mailbox|here]]. For any other addresses, you will need a domain (for example a .com or .be). It is possible to have a domain already connected to your ULYSSIS account as a regular website, but not activated for email. It is also possible to use a domain just for email and not for a website. More information about adding and activating domains can be found [[Adding_domain_names|here]]. Keep in mind ULYSSIS does not currently sell domains, but you can buy them from lots of different companies. If you have an email domain activated on your account, you will be able to add [[forwarders]] in our control panel [https://ucc.ulyssis.org UCC]. You can create as many forwarders as you like, and have the addresses forward to a single address or several. Lots of organisations use forwarders as an easy way to contact a team of people responsible for a certain task, for example your PR team or the president of your organisation. This way you can have an address such as preses@kringleuven.be forward to jan.peeters@gmail.com, but can easily change it every year. This way external contacts only have to use a single address and will always end up contacting the right people. Since forwarders relay emails to one or several addresses, you may want to reply using the forwarder address instead of your personal one. In that case you want to [[Using_a_forwarder_as_an_alias|add an alias]]. We offer instructions for our own webmail, the Thunderbird email client, Gmail and Hotmail/Outlook.com. Currently we do not offer mailboxes for your own domains, only the single mailbox that comes with your account by default. If you have any further questions about email, you can always contact our team at ulyssis@ulyssis.org 4dee85f08757c27779740705bb4e0f5d88eb163f 651 650 2018-10-11T00:13:47Z Bert 8 wikitext text/x-wiki By default, any ULYSSIS account comes with a single email address, specifically your username on our main domain, ulyssis.org: <code>''username''@ulyssis.org</code>. You can either use this address as your only mailbox, or as a forwarder to another email address. You can find more information about your mailbox [[Mailbox|here]]. For any other addresses, you will need a domain (for example a .com or .be). It is possible to have a domain already connected to your ULYSSIS account as a regular website, but not activated for email. It is also possible to use a domain just for email and not for a website. More information about adding and activating domains can be found [[Adding_domain_names|here]]. Keep in mind ULYSSIS does not currently sell domains, but you can buy them from lots of different companies. If you have an email domain activated on your account, you will be able to add [[forwarders]] in our control panel [https://ucc.ulyssis.org UCC]. You can create as many forwarders as you like, and have the addresses forward to a single address or several. Lots of organisations use forwarders as an easy way to contact a team of people responsible for a certain task, for example your PR team or the president of your organisation. This way you can have an address such as preses@kringleuven.be forward to jan.peeters@gmail.com, but can easily change it every year. This way external contacts only have to use a single address and will always end up contacting the right people. Since forwarders relay emails to one or several addresses, you may want to reply using the forwarder address instead of your personal one. In that case you want to [[Using_a_forwarder_as_an_alias|add an alias]]. We offer instructions for our own webmail, the Thunderbird email client, Gmail and Hotmail/Outlook.com. If instructions are missing for your email client or service, we can of course try and help you if you send us an email. Currently we do not offer mailboxes for your own domains, only the single mailbox that comes with your account by default. If you have any further questions about email, you can always contact our team at ulyssis@ulyssis.org 4d076774d71134aefde707a0729fcb60b294499c 0 12 652 426 2018-11-05T11:37:37Z Andreas 20 /* Accessing PostgreSQL from outside of our network */ wikitext text/x-wiki = Creating a database = You can create one or more PostgreSQL databases in [https://ucc.ulyssis.org UCC]. The first database you create will have the same name as your username. Subsequent databases will be prefixed with "''username''_". = Managing your database = * The easiest way to manage your database is using [https://phppgadmin.ulyssis.org phpPgAdmin]. * You can also access it via the [[Accessing shell servers over SSH|command line]] with: psql -h pgsql.ulyssis.org = Connecting to the database = You can connect to the database with the following details: * Host: <code>pgsql.ulyssis.org</code> * Login: your ULYSSIS username * Password: the PostgreSQL password you chose in UCC * Database: the database you created in UCC Note that some CMSs will assume that you use "localhost" as the host, and will hide the host option under advanced settings in the installation process. If you can't find anywhere to enter the hostname, look under advanced settings. == Connection string == If you are programming your application yourself, PostgreSQL often uses the following connection format: host=$host user=$username password=$password db=$dbname Where you replace the parts starting with <code>$</code> with the above connection details. == pg_connect == If you are using PHP's [http://www.php.net/manual/en/function.pg-connect.php pg_connect] to connect to the database, and your username is "foo", your password is "password" and your database name is "foo": <syntaxhighlight lang="php"> $connection = pg_connect("host=pgsql.ulyssis.org user=foo password=password db=foo"); </syntaxhighlight> == PDO == If you want to connect using [http://be2.php.net/manual/en/intro.pdo.php PDO], your username is "foo", your password is "password" and your database is "foo": <syntaxhighlight lang="php"> $pdo = new PDO('pgsql:host=pgsql.ulyssis.org;dbname=foo', 'foo', 'password'); </syntaxhighlight> =Accessing PostgreSQL from outside of our network= To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH-tunnel. On Linux, Mac OSX and other Unix-like Operating Systems it is easily possible to use the following command to create a tunnel to a local port (in this case 5400): ssh username@ssh2.ulyssis.org -L 5400:pgsql.ulyssis.org:5432 -N You can use "ssh -f username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N": the f-argument will put the command in the background. = PostGIS = If necessary for an application or website you wish to use on ULYSSIS, we can always enable PostGIS for the specific database you wish to use it on. Contact us at ulyssis@ulyssis.org and let us know you would like to get PostGIS enabled and on which specific database. ce49215c0d66c55ddbd7f08d8ebae505f51ded00 0 30 655 515 2018-11-07T01:14:59Z Bert 8 wikitext text/x-wiki Please keep in mind you have to be the owner of the account to be able to renew it. If you are not the owner you first have to look into [Transferring_your_account]. 3 weeks before your account expires you will start receiving emails reminding you to renew your account. These will continue until your account expires. To renew your account you visit https://ucc.ulyssis.org/accounts and, while making sure you are '''not''' logged into a ULYSSIS Account, login using the Central KU Leuven Login and select your account (the renewal option will only be available if the account is in the renewal period of 3 weeks or has expired already). * Select your account option, you are free to upgrade your personal account to a higher tier now * Verify your personal information (in case of errors please contact ULYSSIS) * Accept the terms of use * Confirm your order * An email will be sent to your KU Leuven emailaddress to confirm your order and with a request for payment. * As soon as we have received and processed your payment your account will get renewed, you will receive a notification. * If you are running late with your payment and you wish to prevent your account from getting expired you can contact ULYSSIS with a screenshot or scan that confirms the payment, we will then temporarily renew your account and verify that the money arrives within the near future. 86a982f721f00cb8d0af44290241ad020aeabfd3 656 655 2018-11-07T01:15:08Z Bert 8 wikitext text/x-wiki Please keep in mind you have to be the owner of the account to be able to renew it. If you are not the owner you first have to look into [[Transferring_your_account]]. 3 weeks before your account expires you will start receiving emails reminding you to renew your account. These will continue until your account expires. To renew your account you visit https://ucc.ulyssis.org/accounts and, while making sure you are '''not''' logged into a ULYSSIS Account, login using the Central KU Leuven Login and select your account (the renewal option will only be available if the account is in the renewal period of 3 weeks or has expired already). * Select your account option, you are free to upgrade your personal account to a higher tier now * Verify your personal information (in case of errors please contact ULYSSIS) * Accept the terms of use * Confirm your order * An email will be sent to your KU Leuven emailaddress to confirm your order and with a request for payment. * As soon as we have received and processed your payment your account will get renewed, you will receive a notification. * If you are running late with your payment and you wish to prevent your account from getting expired you can contact ULYSSIS with a screenshot or scan that confirms the payment, we will then temporarily renew your account and verify that the money arrives within the near future. ff60ece9037abfb401f5214951d3ac580483abfe 0 30 657 656 2018-11-07T01:15:27Z Bert 8 wikitext text/x-wiki Please keep in mind you have to be the owner of the account to be able to renew it. If you are not the owner you first have to look into [[Transferring your account]]. 3 weeks before your account expires you will start receiving emails reminding you to renew your account. These will continue until your account expires. To renew your account you visit https://ucc.ulyssis.org/accounts and, while making sure you are '''not''' logged into a ULYSSIS Account, login using the Central KU Leuven Login and select your account (the renewal option will only be available if the account is in the renewal period of 3 weeks or has expired already). * Select your account option, you are free to upgrade your personal account to a higher tier now * Verify your personal information (in case of errors please contact ULYSSIS) * Accept the terms of use * Confirm your order * An email will be sent to your KU Leuven emailaddress to confirm your order and with a request for payment. * As soon as we have received and processed your payment your account will get renewed, you will receive a notification. * If you are running late with your payment and you wish to prevent your account from getting expired you can contact ULYSSIS with a screenshot or scan that confirms the payment, we will then temporarily renew your account and verify that the money arrives within the near future. bf67c64d08983ccbb353c5d00e118e4505b1d3ba 687 657 2019-04-25T11:00:07Z Bert 8 wikitext text/x-wiki Please keep in mind you have to be the owner of the account to be able to renew it. If you are not the owner you first have to look into [[Transferring your account]]. 3 weeks before your account expires you will start receiving emails reminding you to renew your account. These will continue until your account expires. To renew your account you visit https://ucc.ulyssis.org/accounts and, while making sure you are '''not''' logged into a ULYSSIS Account, login using the Central KU Leuven Login and select your account (the renewal option will only be available if the account is in the renewal period of 40 days or has expired already). * Select your account option, you are free to upgrade your personal account to a higher tier now * Verify your personal information (in case of errors please contact ULYSSIS) * Accept the terms of use * Confirm your order * An email will be sent to your KU Leuven emailaddress to confirm your order and with a request for payment. * As soon as we have received and processed your payment your account will get renewed, you will receive a notification. * If you are running late with your payment and you wish to prevent your account from getting expired you can contact ULYSSIS with a screenshot or scan that confirms the payment, we will then temporarily renew your account and verify that the money arrives within the near future. 6a13db95689816b9e3b21927e760daf10671d604 699 687 2019-08-28T15:07:58Z Bert 8 wikitext text/x-wiki Please keep in mind you have to be the owner of the account to be able to renew it. If you are not the owner you first have to look into [[Transferring your account]]. 3 weeks before your account expires you will start receiving emails reminding you to renew your account. These will continue until your account expires. To renew your account you visit https://ucc.ulyssis.org/accounts and, while making sure you are '''not''' logged into a ULYSSIS Account, login using the Central KU Leuven Login and select your account (the renewal option will only be available if the account is in the renewal period of 40 days or has expired already). * Select your account option, you are free to upgrade your personal account to a higher tier now * Verify your personal information (in case of errors please contact ULYSSIS) * Accept the terms of use * Confirm your order * An email will be sent to your KU Leuven emailaddress to confirm your order and with a request for payment. * As soon as we have received and processed your payment your account will get renewed, you will receive a notification. * If you are running late with your payment and you wish to prevent your account from getting expired you can contact ULYSSIS with a screenshot or scan that confirms the payment, we will then temporarily renew your account and verify that the money arrives within the near future. [[Category:Account]] 7aa3137d5b5a2e6336622f576ddb6e889cef1b19 0 7 658 605 2018-11-23T23:23:32Z Tim 25 Update introduction, start with web irc, add znc wikitext text/x-wiki ULYSSIS hosts its own IRC server. IRC stands for Internet Relay Chat, [https://en.wikipedia.org/wiki/Internet_Relay_Chat IRC on wikipedia]. It is a chat protocol that mainly focuses on group chat, but also allows for private chat. If you have an urgent question, IRC is often the quickest way to contact us. But also if you don't have a question and just want to hang out in our chat, feel free to join! ==Using our web IRC client== If you won't regularly use our IRC or if you just want to check it out, you can use our web IRC client instead. You can find it at [https://webirc.ulyssis.org/ webirc.ulyssis.org]. ==IRC server details== Below are specific instructions for some clients, but if you are already familiar with IRC, here are the details you need to connect to our server. We highly recommend using SSL. Server: irc.ulyssis.org Port: 6668 (SSL) Channel: #ulyssis ==IRC clients== To use IRC, you'll need an IRC client. We advise the terminal based [https://irssi.org/ irssi] or [https://weechat.org/ weechat] for Linux and [https://hexchat.github.io/ hexchat] or [https://www.mirc.com/ mIRC] for Windows, but there are a lot of other free options. You can only receive messages over IRC while you're connected. Therefore, we advise you to run irssi or weechat in either a screen or a tmux session. With a ULYSSIS account, you can run screen or tmux on our shellservers, as they keep running 24/7 you can use them to keep track of your conversations. Screen and tmux are similar programs. Screen has been around for longer and is more tested, while tmux is more modern with new features and being easier to use for beginners. ==Using irssi on our shell servers== ===Connect to the shellserver=== Use the ssh command in your Linux or OS X terminal, or use PuTTY to connect on windows. Extensive information on how to do so can be found on [[Accessing shell servers over SSH]]. ===Start irssi in a screen=== *When on the shellserver, enter <code>screen -U</code> to start a screen session, or <code>tmux</code> to start a tmux session. *Enter <code>irssi</code> to start irssi *Connect to the IRC server: <code>/server -ssl irc.ulyssis.org 6668</code> *Connect to the public channel: <code>/join #ulyssis</code> ===Screen usage=== *To exit the screen: press Ctrl-A and press D ('detach') to return to the shellserver. *To reconnect: enter <code>screen -r</code> or <code>screen -DR</code> (the latter will create a new screen if it wasn't already made). ===Tmux usage=== *To exit the tmux session: press Ctrl-B and press D ('detach') to return to the shellserver. *To reconnect: enter <code>tmux attach</code> ===Help, I can't reconnect to my session!=== *Check if you are on the right shell server and didn't make a typing error. *If everything is correct, your screen may have been stopped by a crash or a reboot of our shellserver. You can check the [http://www.ulyssis.org/status status] section of our website for more information about possible downtimes. *Make sure you use the right program (<code>screen</code> if you started a screen session and <code>tmux</code> if you started a tmux session) ==Using ZNC== Alternatively, if you don't like using terminal-based clients, or just want to run your client locally, you can connect with our [https://znc.ulyssis.org/ ZNC server]. However, to use it, you'll need a ULYSSIS account. ZNC connects to our IRC server in your place (fill in the details at the beginning of this article). You can then connect to ZNC with a client of your choice, and it will send you the history you've missed while you were offline. Log in to our ZNC server. In your settings, create a new network. Fill in the basic details (server name, nickname, set <code>BindHost</code> to <code>0.0.0.0</code>). In the server field, fill in <code>irc.ulyssis.org +6668</code>. Add <code>#ulyssis</code> as a channel. You may want to increase the buffer count. Then save at the bottom of the page. In your IRC client, connect to the server <code>znc.ulyssis.org</code> on port 6666 (with SSL) and set <code>username/network:password</code> as password to the server. Replace <code>username</code> with your ULYSSIS username, <code>network</code> with the name of the network in your znc settings, and <code>password</code> with your ULYSSIS password. 1e25f8cf6906a883723b20f9ca6932c464610e0c 659 658 2018-11-23T23:31:09Z Tim 25 wikitext text/x-wiki ULYSSIS hosts its own IRC network. IRC stands for Internet Relay Chat, [https://en.wikipedia.org/wiki/Internet_Relay_Chat IRC on wikipedia]. It is a chat protocol that mainly focuses on group chat, but also allows for private chat. If you have an urgent question, IRC is often the quickest way to contact us. But also if you don't have a question and just want to hang out in our chat, feel free to join! ==Web IRC client== If you won't regularly use our IRC or if you just want to check it out, you can use our web IRC client. You can find it at [https://webirc.ulyssis.org/ webirc.ulyssis.org]. ==IRC network details== Below are specific instructions for some clients, but if you are already familiar with IRC, here are the details you need to connect to our server. We highly recommend using SSL. Server: irc.ulyssis.org Port: 6668 (SSL) Channel: #ulyssis If <code>irc.ulyssis.org</code> is down, you can also try the other server in the same network, hosted at <code>irc2.ulyssis.org</code>. Both are connected to each other and you can use them interchangeably. It is advised to add it as a fallback in your IRC client. ==IRC clients== To use IRC, you'll need an IRC client. We advise the terminal based [https://irssi.org/ irssi] or [https://weechat.org/ weechat] for Linux and [https://hexchat.github.io/ hexchat] or [https://www.mirc.com/ mIRC] for Windows, but there are a lot of other free options. You can only receive messages over IRC while you're connected. Therefore, we advise you to run irssi or weechat in either a screen or a tmux session. With a ULYSSIS account, you can run screen or tmux on our shellservers, as they keep running 24/7 you can use them to keep track of your conversations. Screen and tmux are similar programs. Screen has been around for longer and is more tested, while tmux is more modern with new features and being easier to use for beginners. ===Using irssi on our shell servers=== ====Connect to the shellserver==== Use the ssh command in your Linux or OS X terminal, or use PuTTY to connect on windows. Extensive information on how to do so can be found on [[Accessing shell servers over SSH]]. ====Start irssi in a screen==== *When on the shellserver, enter <code>screen -U</code> to start a screen session, or <code>tmux</code> to start a tmux session. *Enter <code>irssi</code> to start irssi *Connect to the IRC server: <code>/server -ssl irc.ulyssis.org 6668</code> *Connect to the public channel: <code>/join #ulyssis</code> ====Screen usage==== *To exit the screen: press Ctrl-A and press D ('detach') to return to the shellserver. *To reconnect: enter <code>screen -r</code> or <code>screen -DR</code> (the latter will create a new screen if it wasn't already made). ====Tmux usage==== *To exit the tmux session: press Ctrl-B and press D ('detach') to return to the shellserver. *To reconnect: enter <code>tmux attach</code> ====Help, I can't reconnect to my session!==== *Check if you are on the right shell server and didn't make a typing error. *If everything is correct, your screen may have been stopped by a crash or a reboot of our shellserver. You can check the [http://www.ulyssis.org/status status] section of our website for more information about possible downtimes. *Make sure you use the right program (<code>screen</code> if you started a screen session and <code>tmux</code> if you started a tmux session) ==Using ZNC== Alternatively, if you don't like using terminal-based clients, or just want to run your client locally, you can connect with our [https://znc.ulyssis.org/ ZNC server]. However, to use it, you'll need a ULYSSIS account. ZNC connects to our IRC server in your place (fill in the details at the beginning of this article). You can then connect to ZNC with a client of your choice, and it will send you the history you've missed while you were offline. Log in to our ZNC server. In your settings, create a new network. Fill in the basic details (server name, nickname, set <code>BindHost</code> to <code>0.0.0.0</code>). In the server field, fill in <code>irc.ulyssis.org +6668</code>. Add <code>#ulyssis</code> as a channel. You may want to increase the buffer count. Then save at the bottom of the page. In your IRC client, connect to the server <code>znc.ulyssis.org</code> on port 6666 (with SSL) and set <code>username/network:password</code> as password to the server. Replace <code>username</code> with your ULYSSIS username, <code>network</code> with the name of the network in your znc settings, and <code>password</code> with your ULYSSIS password. 111884667f8b065ec6534e8af9c519c9f63e5094 0 98 660 579 2018-11-27T23:09:47Z Yoa 30 /* MWSAllowedDegrees */ wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for login through the Central KU Leuven Login (Shibboleth). The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Central KU Leuven Login) enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code><mediawiki installation folder>/LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] aefcde3f84586e17a840290a5561d6eafc673558 662 660 2018-12-10T14:35:30Z Yoa 30 /* Restricting access to logged-in users only */ wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for login through the Central KU Leuven Login (Shibboleth). The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Central KU Leuven Login) enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code><mediawiki installation folder>/LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] eab20f9171f0ba4a17e95eba462dcfe1d11a647f 663 662 2018-12-10T14:35:36Z Yoa 30 /* MWSStudentsOnly */ wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for login through the Central KU Leuven Login (Shibboleth). The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Central KU Leuven Login) enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code><mediawiki installation folder>/LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] ad8f7444b26c3c9a3c651d8ec35d77a5295db276 664 663 2018-12-10T14:35:42Z Yoa 30 /* MWSAllowedKULids */ wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for login through the Central KU Leuven Login (Shibboleth). The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Central KU Leuven Login) enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code><mediawiki installation folder>/LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 116f3ce426a7e3c64f3d193800d58992193fe88c 665 664 2018-12-10T14:35:47Z Yoa 30 /* MWSAllowedDegrees */ wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for login through the Central KU Leuven Login (Shibboleth). The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Central KU Leuven Login) enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code><mediawiki installation folder>/LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 0c942ea3158936cd6931aabbd529ade32347ebbc 666 665 2018-12-10T14:38:13Z Yoa 30 /* Installation */ wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for login through the Central KU Leuven Login (Shibboleth). The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Central KU Leuven Login) enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Make sure there is now a <code>MediaWikiShibboleth</code> folder in your extensions folder. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code><mediawiki installation folder>/LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 8df15dd8fbcf87f7fbfad3eb5fcb2f3e55bb945b 667 666 2018-12-11T11:30:10Z Yoa 30 Translations wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for login through the Central KU Leuven Login (Shibboleth). The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Central KU Leuven Login) enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Make sure there is now a <code>MediaWikiShibboleth</code> folder in your extensions folder. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code><mediawiki installation folder>/LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. === Translations === It's possible to translate and modify all public MediaWikiShibboleth messages. The translations can be found in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/i18n</code>. Dutch (<code>nl.json</code>) and English (<code>en.json</code>) translations are already provided. Even the provided translations can be customized, we strongly advise you to do so, in order to match them with your Wiki situation. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 6fe29203e6cabe1ccd14ef0d81eab01bea2321a8 668 667 2018-12-11T11:33:29Z Yoa 30 /* Translations */ wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for login through the Central KU Leuven Login (Shibboleth). The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Central KU Leuven Login) enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Make sure there is now a <code>MediaWikiShibboleth</code> folder in your extensions folder. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code><mediawiki installation folder>/LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. === Translations === It's possible to translate and modify all public MediaWikiShibboleth messages. The translations can be found in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/i18n</code>. Dutch (<code>nl.json</code>) and English (<code>en.json</code>) translations are already provided. Even the provided translations can be customized, and we strongly advise you to do so, in order to match them with your Wiki situation. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] ba2b65623f7cea09c9b364a1185c9b1ef05d6171 669 668 2018-12-11T11:33:58Z Yoa 30 /* Installation */ wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for login through the Central KU Leuven Login (Shibboleth). The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Central KU Leuven Login) enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Make sure there is now a <code>MediaWikiShibboleth</code> folder in <code><mediawiki installation folder>/extensions/</code>. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/MediaWikiShibboleth_body.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code><mediawiki installation folder>/LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. === Translations === It's possible to translate and modify all public MediaWikiShibboleth messages. The translations can be found in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/i18n</code>. Dutch (<code>nl.json</code>) and English (<code>en.json</code>) translations are already provided. Even the provided translations can be customized, and we strongly advise you to do so, in order to match them with your Wiki situation. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] ce6772bed02db9f616794cbd97fac25a6956ca8e 673 669 2019-02-03T19:24:38Z Yoa 30 /* Installation */ wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for login through the Central KU Leuven Login (Shibboleth). The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Central KU Leuven Login) enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Make sure there is now a <code>MediaWikiShibboleth</code> folder in <code><mediawiki installation folder>/extensions/</code>. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); include 'extensions/MediaWikiShibboleth/includes/MediaWikiShibboleth.php'; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code><mediawiki installation folder>/LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. === Translations === It's possible to translate and modify all public MediaWikiShibboleth messages. The translations can be found in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/i18n</code>. Dutch (<code>nl.json</code>) and English (<code>en.json</code>) translations are already provided. Even the provided translations can be customized, and we strongly advise you to do so, in order to match them with your Wiki situation. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 45c3a99f6b0a39d6c0885d57765e191e0f9c1c1a 674 673 2019-02-03T19:44:21Z Yoa 30 /* Installation */ wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for login through the Central KU Leuven Login (Shibboleth). The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Central KU Leuven Login) enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Make sure there is now a <code>MediaWikiShibboleth</code> folder in <code><mediawiki installation folder>/extensions/</code>. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); $wgGroupPermissions['*']['createaccount'] = false; $wgRevokePermissions['Shibboleth']['editmyprivateinfo'] = true; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. Though this really defeats the purpose of the extension. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code><mediawiki installation folder>/LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. === Translations === It's possible to translate and modify all public MediaWikiShibboleth messages. The translations can be found in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/i18n</code>. Dutch (<code>nl.json</code>) and English (<code>en.json</code>) translations are already provided. Even the provided translations can be customized, and we strongly advise you to do so, in order to match them with your Wiki situation. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 92234186e078f4567d644215da20038dabd91a83 675 674 2019-02-03T19:47:06Z Yoa 30 /* Installation */ wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for login through the Central KU Leuven Login (Shibboleth). The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Central KU Leuven Login) enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Make sure there is now a <code>MediaWikiShibboleth</code> folder in <code><mediawiki installation folder>/extensions/</code>. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); $wgGroupPermissions['*']['createaccount'] = false; $wgRevokePermissions['Shibboleth']['editmyprivateinfo'] = true; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. This really defeats the purpose of the extension though. ==Configuration== MediaWikiShibboleth has 3 configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code><mediawiki installation folder>/LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. === Translations === It's possible to translate and modify all public MediaWikiShibboleth messages. The translations can be found in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/i18n</code>. Dutch (<code>nl.json</code>) and English (<code>en.json</code>) translations are already provided. Even the provided translations can be customized, and we strongly advise you to do so, in order to match them with your Wiki situation. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 004e2d332cd1ddf2dace4ea1072d013a00c1d71c 676 675 2019-02-03T19:48:59Z Yoa 30 /* Configuration */ wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for login through the Central KU Leuven Login (Shibboleth). The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Central KU Leuven Login) enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Make sure there is now a <code>MediaWikiShibboleth</code> folder in <code><mediawiki installation folder>/extensions/</code>. Finally, add the following lines to your <code><mediawiki installation folder>/LocalSettings.php</code>: wfLoadExtension('MediaWikiShibboleth'); $wgGroupPermissions['*']['createaccount'] = false; $wgRevokePermissions['Shibboleth']['editmyprivateinfo'] = true; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. This really defeats the purpose of the extension though. ==Configuration== MediaWikiShibboleth has some configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code><mediawiki installation folder>/LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. === Translations === It's possible to translate and modify all public MediaWikiShibboleth messages. The translations can be found in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/i18n</code>. Dutch (<code>nl.json</code>) and English (<code>en.json</code>) translations are already provided. Even the provided translations can be customized, and we strongly advise you to do so, in order to match them with your Wiki situation. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 33bc921e866311928d2eca52512b95781da816cd 677 676 2019-02-07T17:41:40Z Yoa 30 /* Installation */ wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for login through the Central KU Leuven Login (Shibboleth). The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Central KU Leuven Login) enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in your <code><mediawiki installation folder>/extensions/</code> directory. Make sure there is now a <code>MediaWikiShibboleth</code> folder in <code><mediawiki installation folder>/extensions/</code>. Finally, locate the <code>LocalSettings.php</code> file in your MediaWiki installation folder and add the following lines to it: wfLoadExtension('MediaWikiShibboleth'); $wgGroupPermissions['*']['createaccount'] = false; $wgRevokePermissions['Shibboleth']['editmyprivateinfo'] = true; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. This really defeats the purpose of the extension though. ==Configuration== MediaWikiShibboleth has some configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code><mediawiki installation folder>/LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. === Translations === It's possible to translate and modify all public MediaWikiShibboleth messages. The translations can be found in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/i18n</code>. Dutch (<code>nl.json</code>) and English (<code>en.json</code>) translations are already provided. Even the provided translations can be customized, and we strongly advise you to do so, in order to match them with your Wiki situation. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 5c0105d7467c264a34f13806911ca9d7932b96ae 678 677 2019-02-07T17:42:20Z Yoa 30 /* Installation */ wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for login through the Central KU Leuven Login (Shibboleth). The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Central KU Leuven Login) enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in the <code>extensions/</code> directory in your MediaWiki installation folder. Make sure there is now a <code>MediaWikiShibboleth</code> folder in <code>extensions/</code>. Finally, locate the <code>LocalSettings.php</code> file in your MediaWiki installation folder and add the following lines to it: wfLoadExtension('MediaWikiShibboleth'); $wgGroupPermissions['*']['createaccount'] = false; $wgRevokePermissions['Shibboleth']['editmyprivateinfo'] = true; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. This really defeats the purpose of the extension though. ==Configuration== MediaWikiShibboleth has some configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. They can be configured in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/extension.json</code> file. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code><mediawiki installation folder>/LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code><mediawiki installation folder>/LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code><mediawiki installation folder>/LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. === Translations === It's possible to translate and modify all public MediaWikiShibboleth messages. The translations can be found in the <code><mediawiki installation folder>/extensions/MediaWikiShibboleth/i18n</code>. Dutch (<code>nl.json</code>) and English (<code>en.json</code>) translations are already provided. Even the provided translations can be customized, and we strongly advise you to do so, in order to match them with your Wiki situation. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] d43b77e53686436bc8dfa5b6850fce4ba7ac2f92 679 678 2019-02-07T17:43:05Z Yoa 30 /* Configuration */ wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for login through the Central KU Leuven Login (Shibboleth). The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Central KU Leuven Login) enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in the <code>extensions/</code> directory in your MediaWiki installation folder. Make sure there is now a <code>MediaWikiShibboleth</code> folder in <code>extensions/</code>. Finally, locate the <code>LocalSettings.php</code> file in your MediaWiki installation folder and add the following lines to it: wfLoadExtension('MediaWikiShibboleth'); $wgGroupPermissions['*']['createaccount'] = false; $wgRevokePermissions['Shibboleth']['editmyprivateinfo'] = true; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. This really defeats the purpose of the extension though. ==Configuration== MediaWikiShibboleth has some configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code>LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code>LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code>LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code>LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. === Translations === It's possible to translate and modify all public MediaWikiShibboleth messages. The translations can be found in the <code>extensions/MediaWikiShibboleth/i18n/</code>. Dutch (<code>nl.json</code>) and English (<code>en.json</code>) translations are already provided. Even the provided translations can be customized, and we strongly advise you to do so, in order to match them with your Wiki situation. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Password Login" to expand a login menu. The new log in page looks like this with "Password Login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] fcec62e6ef60cb12a98a620a30d2adb4476a413d 682 679 2019-02-07T18:19:25Z Yoa 30 /* Operation */ wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for login through the Central KU Leuven Login (Shibboleth). The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Central KU Leuven Login) enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in the <code>extensions/</code> directory in your MediaWiki installation folder. Make sure there is now a <code>MediaWikiShibboleth</code> folder in <code>extensions/</code>. Finally, locate the <code>LocalSettings.php</code> file in your MediaWiki installation folder and add the following lines to it: wfLoadExtension('MediaWikiShibboleth'); $wgGroupPermissions['*']['createaccount'] = false; $wgRevokePermissions['Shibboleth']['editmyprivateinfo'] = true; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. This really defeats the purpose of the extension though. ==Configuration== MediaWikiShibboleth has some configuration options which allow for restricting who can log in to your wiki. These options work especially well with restricting the access of the wiki to logged-in users only. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code>LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code>LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code>LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code>LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. === Translations === It's possible to translate and modify all public MediaWikiShibboleth messages. The translations can be found in the <code>extensions/MediaWikiShibboleth/i18n/</code>. Dutch (<code>nl.json</code>) and English (<code>en.json</code>) translations are already provided. Even the provided translations can be customized, and we strongly advise you to do so, in order to match them with your Wiki situation. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Login without Central KU Leuven login" to expand a login menu. The new log in page looks like this with "Login without Central KU Leuven login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] ea91032eb0f55943284d17a92ff80a8f9d58edad 686 682 2019-03-22T14:37:09Z Yoa 30 /* Configuration */ wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for login through the Central KU Leuven Login (Shibboleth). The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Central KU Leuven Login) enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in the <code>extensions/</code> directory in your MediaWiki installation folder. Make sure there is now a <code>MediaWikiShibboleth</code> folder in <code>extensions/</code>. Finally, locate the <code>LocalSettings.php</code> file in your MediaWiki installation folder and add the following lines to it: wfLoadExtension('MediaWikiShibboleth'); $wgGroupPermissions['*']['createaccount'] = false; $wgRevokePermissions['Shibboleth']['editmyprivateinfo'] = true; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. This really defeats the purpose of the extension though. ==Configuration== MediaWikiShibboleth has some configuration options which allow for restricting who can log in to your wiki. These restrictions are cumulative. For example, it is possible to allow only students enrolled in a specific degree or programme to log in. These options work especially well with restricting the access of the wiki to logged-in users only. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code>LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code>LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code>LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code>LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. === Translations === It's possible to translate and modify all public MediaWikiShibboleth messages. The translations can be found in the <code>extensions/MediaWikiShibboleth/i18n/</code>. Dutch (<code>nl.json</code>) and English (<code>en.json</code>) translations are already provided. Even the provided translations can be customized, and we strongly advise you to do so, in order to match them with your Wiki situation. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Login without Central KU Leuven login" to expand a login menu. The new log in page looks like this with "Login without Central KU Leuven login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] 7c82738fc29bee14a88347a1fa946d79adb6eaa9 0 44 661 194 2018-12-06T19:27:17Z Simon 36 /* Accessing your website */ wikitext text/x-wiki = Location of your files = All the files you want to provide via the web browser must reside in a directory named "www" in your homefolder. Within that folder you can organise your data in sub directories. For more information about accessing your files is available [https://docs.ulyssis.org/Accessing_your_files here]. = Accessing your website = Your webspace is accessible on following url's (with username your username): * http://username.studentenweb.org * http://username.ulyssis.be If you have a domainname like yourname.be, you can link it with our webserver. For more information on this subject, see the [https://docs.ulyssis.org/Adding_domain_names domainnames documentation]. = Troubleshooting = I keep getting an "HTTP Error 403: permission denied" when accessing my website. Try changing the permissions of your www-directory. Log in to a ULYSSIS shell machine and type: <code>chmod o+x ~ chmod o+rx ~/www</code> 21fbce109453aef807c99e5a3c98b6a8cf4aa5e7 711 661 2019-08-28T15:13:11Z Bert 8 wikitext text/x-wiki = Location of your files = All the files you want to provide via the web browser must reside in a directory named "www" in your homefolder. Within that folder you can organise your data in sub directories. For more information about accessing your files is available [https://docs.ulyssis.org/Accessing_your_files here]. = Accessing your website = Your webspace is accessible on following url's (with username your username): * http://username.studentenweb.org * http://username.ulyssis.be If you have a domainname like yourname.be, you can link it with our webserver. For more information on this subject, see the [https://docs.ulyssis.org/Adding_domain_names domainnames documentation]. = Troubleshooting = I keep getting an "HTTP Error 403: permission denied" when accessing my website. Try changing the permissions of your www-directory. Log in to a ULYSSIS shell machine and type: <code>chmod o+x ~ chmod o+rx ~/www</code> [[Category:Webserver]] 889bcd3ce2aa08539657896bec9a230c9c629907 0 45 671 517 2018-12-21T19:24:42Z Lars 26 wikitext text/x-wiki You can always reset your password. In order to reset your password, visit [https://ucc.ulyssis.org/ucc/passwd/reset UCC]. Please keep in mind you need to be logged out of UCC to be able to reset your password. * Fill in your username and click on 'reset password' * Then you will have to sign in using your KU Leuven credentials to make sure it is really you * Choose another password * Click on reset password * You will immediately be logged out of your KU Leuven account again, but your password will have been changed. * Try to log in at UCC with your new password Be wise and pick a [https://xkcd.com/936/ strong and easy to remember password]. adaa62dc9a7fce841e7a8c697d59dfde4cd725bd 702 671 2019-08-28T15:10:40Z Bert 8 wikitext text/x-wiki You can always reset your password. In order to reset your password, visit [https://ucc.ulyssis.org/ucc/passwd/reset UCC]. Please keep in mind you need to be logged out of UCC to be able to reset your password. * Fill in your username and click on 'reset password' * Then you will have to sign in using your KU Leuven credentials to make sure it is really you * Choose another password * Click on reset password * You will immediately be logged out of your KU Leuven account again, but your password will have been changed. * Try to log in at UCC with your new password Be wise and pick a [https://xkcd.com/936/ strong and easy to remember password]. [[Category:Account]] d73b4bbac6689c1f0742513e61fd2c9ffc3c5d72 0 103 672 548 2018-12-23T17:51:27Z Principis 32 Added Node.js paragraph wikitext text/x-wiki While most webhosting providers give you access to a few or even just one programming language and a set amount of libraries, ULYSSIS prefers to offer more flexibility. We hope to give our users the chance to experiment with different languages, libraries and tools. There are of course also limits to what is realistic for us to install. More on that below. == Using a programming language, library or tool that is not installed == If the package that you would like us to install is available in the software repository of our current operating system, then that is usually not a problem. We currently use Ubuntu on all our servers, specifically, we upgrade to the latest LTS every summer vacation following the release of a new one. You can verify which version we are running by executing "cat /etc/lsb-release" on one of our shellservers. After you have verified what version we are running, you can refer to https://packages.ubuntu.com/ to check whether your package is available in that version of Ubuntu. If it is, then you can contact us by email on ulyssis@ulyssis.org which package or packages you would like to have installed, and what you will be using it for. You will most likely get a positive response. If your package is not in the repository, you will have to go for a [[Installing packages#Manual installation|Manual installation]]. == Using a newer/different version == As you can read in the section concerning the installation of new packages, we only offer the version available in the repository of the version of Ubuntu that we are running. In most cases, this means you will have to wait for a version upgrade with the next LTS release, or go for a [[Installing packages#Manual installation|Manual installation]]. However, there are some exceptions. Sometimes multiple version will be available in the repository, such as with Python 2 and 3, or Perl 5 and 6. In such cases, you can refer to the section above for instructions on how to request an installation. == Manual installation == If you want to install a piece of software that is not available in the repository or you wish to install another version, you can always install it manually onto your account. It is important to keep in mind that ULYSSIS will not support manually installed software, and that you are fully responsible for the security of this software. You are free to ask us questions, but we will most probably not help you. If you do require a manual installation of specific software, we expect you to be capable of maintaining it as well. The way you install your software differs depending on the software. You could be using tools such as pip, gem or npm to install to a directory in your home folder, you could be using a virtual environment, or you could be compiling your own binary. We suggest you look at the documentation of the software you're using very thoroughly, and make sure you are comfortable with what you are doing and aware of your responsibilities. After installing your software locally onto your account, you will probably want to add an alias in your dotfiles (for example .profile or .bashrc) to make using your manually installed version easier. In case you are using your piece of software for a web service, you will want to make sure you edit your fastcgi script or any other involved scripts to use your binary by changing the path or hardcoding the location. == Node.js == We do not offer Node.js by default because we can't give you the most recent release. But you can use nvm ([https://github.com/creationix/nvm Node Version Manager]) which installs the required version for you. The installation should be straightforward and a guide can be found [https://github.com/creationix/nvm#installation here]. 455bdb3fad98f891cd2b58a64f1c862340872fcc 6 112 681 2019-02-07T18:09:29Z Yoa 30 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 113 684 2019-02-09T16:19:25Z Lars 26 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 29 685 124 2019-02-09T16:21:39Z Lars 26 Add image with highlighted KU Leuven login link wikitext text/x-wiki To register an account you can follow these easy steps: [[File:UCC Request New Account.png|thumb|right]] * Go to https://ucc.ulyssis.org/accounts and login using your Central KU Leuven Account * Select the kind of account you wish to register ** Most people will want to register a '''regular account''' for '''personal use''' ** If you are a recognised '''faculty''' union, assembly or representational organisation you are entitled to this free account. We verify this using the list of '''recognised "kringen"''' of LOKO, http://loko.be/verenigingen/ . Recognised organisations are not entitled to a free account. ** If you are a '''Recognised organisation''' by LOKO, Studentenraad KU Leuven or the KU Leuven itself you are entitled to an organisation account, this account has a reduced price. * After picking your account type you have to chose what options you want, and choose a username and language. * Next you need to accept the ULYSSIS terms of use and confirm your order. * An email will be sent to your KU Leuven emailaddress to confirm your order and with a request for payment. * As soon as we have received and processed your payment your account will be activated and you will receive instructions to set a password. efe31a43e74f2b68cae73d14e5b115ef1ef08ab7 698 685 2019-08-28T15:07:42Z Bert 8 wikitext text/x-wiki To register an account you can follow these easy steps: [[File:UCC Request New Account.png|thumb|right]] * Go to https://ucc.ulyssis.org/accounts and login using your Central KU Leuven Account * Select the kind of account you wish to register ** Most people will want to register a '''regular account''' for '''personal use''' ** If you are a recognised '''faculty''' union, assembly or representational organisation you are entitled to this free account. We verify this using the list of '''recognised "kringen"''' of LOKO, http://loko.be/verenigingen/ . Recognised organisations are not entitled to a free account. ** If you are a '''Recognised organisation''' by LOKO, Studentenraad KU Leuven or the KU Leuven itself you are entitled to an organisation account, this account has a reduced price. * After picking your account type you have to chose what options you want, and choose a username and language. * Next you need to accept the ULYSSIS terms of use and confirm your order. * An email will be sent to your KU Leuven emailaddress to confirm your order and with a request for payment. * As soon as we have received and processed your payment your account will be activated and you will receive instructions to set a password. [[Category:Account]] 868249f91ae029d66c90a67cddcf9dc1d1b435dc 0 9 688 184 2019-05-29T18:44:36Z Yoa 30 wikitext text/x-wiki You can find all your apache logs (like the access.log and error.log) on all of our shell servers in the directory: /var/log/apache_user/''username'' So if your username is ''foobar'' then you can easily access your logs this way: foobar@zap:~$ cd /var/log/apache_user/foobar foobar@zap:/var/log/apache_user/foobar$ ls foobar.ulyssis.be foobar@zap:/var/log/apache_user/foobar$ cd foobar.ulyssis.be foobar@zap:/var/log/apache_user/foobar/foobar.ulyssis.be$ ls access-2014-05-07.log error-2014-05-07.log foobar@zap:/var/log/apache_user/foobar/foobar.ulyssis.be$ tail error-2014-05-07.log [Wed May 07 01:27:14 2014] [error] [client 10.0.0.1] File does not exist: /home/user/foobar/www/favicon.ico If you can't find your username inside of <code>/var/log/apache_user</code>, don't worry. If you enter it with <code>cd foobar</code>, it will automatically appear. ==With FileZilla== You can also access the log files with an SFTP client, like FileZilla. Just enter <tt>/var/log/apache_user/''username''</tt> (replace ''username'' with your username) on the right hand side, where it says "Remote site", and press <tt>Enter</tt>: [[File:Logs.png]] d6d941fac9d7426c71f02b4b2f08c7db691226cd 0 3 689 645 2019-07-10T18:43:28Z Bert 8 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] * [[Secure file permissions]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] * [[Claiming a port]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 97e2d95cb7d0c2d014c025d3665f2f537989474b 690 689 2019-07-21T00:02:06Z Bert 8 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] * [[Secure file permissions]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Sending email from websites]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] * [[Claiming a port]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 589a8296585dd0b9433853bce23966e586376f25 0 114 691 2019-07-21T01:09:33Z Bert 8 Created page with "Sending email is fairly similar on most hosting service. ULYSSIS hosting is not too different in that sense. We do use a queueing system to detect accounts that are being abus..." wikitext text/x-wiki Sending email is fairly similar on most hosting service. ULYSSIS hosting is not too different in that sense. We do use a queueing system to detect accounts that are being abused by malicious actors to send spam. == How? == == Limitations == 81b5c1ff201049d4fd434abaa7ce566fb8cf39b7 692 691 2019-07-21T02:33:51Z Bert 8 wikitext text/x-wiki Sending email is fairly similar on most hosting service. ULYSSIS hosting is not too different in that sense. We do use a queueing system to detect accounts that are being abused by malicious actors to send spam. == How? == In PHP and most other programming languages, content management systems (CMS), and frameworks, you can use the buildin email function. This may be referred to with names such as buildin, default, standard, local or sendmail. == Delay and limitations == 2bd4f23d1dce6227e429a7dfa22b4a59d14dcd5a 693 692 2019-07-21T02:41:13Z Bert 8 wikitext text/x-wiki Sending email is fairly similar on most hosting service. ULYSSIS hosting is not too different in that sense. We do use a queueing system to detect accounts that are being abused by malicious actors to send spam. == How? == In PHP and most other programming languages, content management systems (CMS), and frameworks, you can use the buildin email function. This may be referred to with names such as buildin, default, standard, local or sendmail. == Delay and limitations == Because of the large amount of users on our hosting services, security breaches and misconfigurations due to user mismanagement happen from time to time. As many malicious actors focus their efforts on abusing servers with a good reputation for the distribution of spam, it is not uncommon to find several thousands of emails being sent once a problem occurs. To combat this, ULYSSIS hosting delays sending of emails for up to 15 minutes and verifies a certain amount of email is never surpassed. If at any point the level is surpassed, ULYSSIS is notified and can take action, while probable spam is stopped from being transmitted. Therefore it is important to keep a potential delay in time when expecting email from your website, but also not to send vast amount of email all at once. It is in general good practice to spread the transmission of for example an email list with several hundred participants. 8ada28a1d8204dbdfbd1670af1c87f4d8963d864 694 693 2019-07-21T02:43:10Z Bert 8 /* Delay and limitations */ wikitext text/x-wiki Sending email is fairly similar on most hosting service. ULYSSIS hosting is not too different in that sense. We do use a queueing system to detect accounts that are being abused by malicious actors to send spam. == How? == In PHP and most other programming languages, content management systems (CMS), and frameworks, you can use the buildin email function. This may be referred to with names such as buildin, default, standard, local or sendmail. == Delay and limitations == '''The delay and limit will be changed on 11 september 2019 to 5 minutes and a maximum of 50 mails for each user in that amount of time''' Because of the large amount of users on our hosting services, security breaches and misconfigurations due to user mismanagement happen from time to time. As many malicious actors focus their efforts on abusing servers with a good reputation for the distribution of spam, it is not uncommon to find several thousands of emails being sent once a problem occurs. To combat this, ULYSSIS hosting delays sending of emails for up to 15 minutes and verifies a certain amount of email is never surpassed. If at any point the level is surpassed, ULYSSIS is notified and can take action, while probable spam is stopped from being transmitted. Therefore it is important to keep a potential delay in time when expecting email from your website, but also not to send vast amount of email all at once. It is in general good practice to spread the transmission of for example an email list with several hundred participants. ae8545730d4d40a53a0cf3d22c3835551895d3c4 695 694 2019-07-21T02:43:16Z Bert 8 /* Delay and limitations */ wikitext text/x-wiki Sending email is fairly similar on most hosting service. ULYSSIS hosting is not too different in that sense. We do use a queueing system to detect accounts that are being abused by malicious actors to send spam. == How? == In PHP and most other programming languages, content management systems (CMS), and frameworks, you can use the buildin email function. This may be referred to with names such as buildin, default, standard, local or sendmail. == Delay and limitations == '''The delay and limit will be changed on 11 september 2019 to 5 minutes and a maximum of 50 mails for each user in that amount of time''' Because of the large amount of users on our hosting services, security breaches and misconfigurations due to user mismanagement happen from time to time. As many malicious actors focus their efforts on abusing servers with a good reputation for the distribution of spam, it is not uncommon to find several thousands of emails being sent once a problem occurs. To combat this, ULYSSIS hosting delays sending of emails for up to 15 minutes and verifies a certain amount of email is never surpassed. If at any point the level is surpassed, ULYSSIS is notified and can take action, while probable spam is stopped from being transmitted. Therefore it is important to keep a potential delay in time when expecting email from your website, but also not to send vast amount of email all at once. It is in general good practice to spread the transmission of for example an email list with several hundred participants. 1a338e335de12e3e2938b0d5f8127c1859566d92 696 695 2019-07-21T02:43:26Z Bert 8 /* Delay and limitations */ wikitext text/x-wiki Sending email is fairly similar on most hosting service. ULYSSIS hosting is not too different in that sense. We do use a queueing system to detect accounts that are being abused by malicious actors to send spam. == How? == In PHP and most other programming languages, content management systems (CMS), and frameworks, you can use the buildin email function. This may be referred to with names such as buildin, default, standard, local or sendmail. == Delay and limitations == The delay and limit will be changed on 11 september 2019 to 5 minutes and a maximum of 50 mails for each user in that amount of time Because of the large amount of users on our hosting services, security breaches and misconfigurations due to user mismanagement happen from time to time. As many malicious actors focus their efforts on abusing servers with a good reputation for the distribution of spam, it is not uncommon to find several thousands of emails being sent once a problem occurs. To combat this, ULYSSIS hosting delays sending of emails for up to 15 minutes and verifies a certain amount of email is never surpassed. If at any point the level is surpassed, ULYSSIS is notified and can take action, while probable spam is stopped from being transmitted. Therefore it is important to keep a potential delay in time when expecting email from your website, but also not to send vast amount of email all at once. It is in general good practice to spread the transmission of for example an email list with several hundred participants. 00089c527d9f985019e81a12e301915054aab723 697 696 2019-07-21T10:04:08Z Bert 8 wikitext text/x-wiki Sending email is fairly similar on most hosting services. ULYSSIS hosting is not too different in that sense. We do use a queueing system to detect accounts that are being abused by malicious actors to send spam. == How? == In PHP and most other programming languages, content management systems (CMS), and frameworks, you can use the buildin email function. This may be referred to with names such as buildin, default, standard, local or sendmail. == Delay and limitations == The delay and limit will be changed on 11 september 2019 to 5 minutes and a maximum of 50 mails for each user in that amount of time Because of the large amount of users on our hosting services, security breaches and misconfigurations due to user mismanagement happen from time to time. As many malicious actors focus their efforts on abusing servers with a good reputation for the distribution of spam, it is not uncommon to find several thousands of emails being sent once a problem occurs. To combat this, ULYSSIS hosting delays sending of emails for up to 15 minutes and verifies a certain amount of email is never surpassed. If at any point the level is surpassed, ULYSSIS is notified and can take action, while probable spam is stopped from being transmitted. Therefore it is important to keep a potential delay in time when expecting email from your website, but also not to send vast amount of email all at once. It is in general good practice to spread the transmission of for example an email list with several hundred participants. b6f7444b6fad5ac08d452b7b564740880391ebba 14 115 700 2019-08-28T15:09:59Z Vincenttc 21 Created blank page wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 15 701 83 2019-08-28T15:10:36Z Bert 8 wikitext text/x-wiki You can transfer the account of your (faculty) organization to a new webmaster. The new webmaster must have a valid Centrale KU Leuven Login. Otherwise the new webmaster can not accept the account transfer. The instructions below must be executed by the current account owner. * Login into [https://ucc.ulyssis.org/ UCC]. * Choose 'Transfer account' in the menu on the right. * Enter the details of the new account owner. (Make sure you type the KULeuven email address correct!) The new owner will get an email to confirm the transfer. [[Category:Account]] 888a3723f37212a40aa49443fd6fcb616b79ea04 0 46 703 208 2019-08-28T15:10:51Z Bert 8 wikitext text/x-wiki If you stumbled upon this question, don't worry; you don't have to (and can't) make an empty transfer. [[Category:Account]] 463f006d2a13c8669b3756112136fef0867ff316 0 5 705 462 2019-08-28T15:12:06Z Bert 8 wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Connecting== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. If your distribution does not contain an option to connect to a server, you can use [https://filezilla-project.org/ FileZilla], which is completely free. See the instructions under [[Accessing_your_files#Windows|Windows]]. [[File:UbuntuConnectToServer.png]] ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ===Mac=== ''[https://filezilla-project.org/ FileZilla], which was mentioned above, is also available for Mac. To use it, follow [[#Windows|the instructions for Windows]]. You can also opt for [http://cyberduck.io/ Cyberduck], though. In that case, follow the instructions below.'' Download the free and open source program [http://cyberduck.io/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> [[File:maccyberduck3.png]] Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. If you want to connect again later on, you can just click the Bookmarks icon on the top left. Next you click on History. And then you can double click to re-open the connection. ==Using FileZilla== When you connect to a server using FileZilla, the following layout will appear: [[File:Base_layout.png|700px|Right]] As you can see, the local files are located on the left-hand side, while the remote (server) files are located on the right-hand side. File navigation and paths are also present. [[File:Layout.png|700px|Right]] To transfer a file or folder, you can drag and drop it, either from the local side to the remote side, or from the remote side to the local side. These operations represent uploading and downloading respectively. [[File:Transfer.png|700px|Right]] You can also press enter while selecting a file, or double-click a file, to transfer it. [[File:Transfer2.png|700px|Right]] To open a folder, you can double-click it, or press enter while selecting it. [[File:Open.png|700px|Right]] You can delete files or folders by pressing the delete button while selecting them, or by right-clicking and clicking 'delete'. [[File:Delete.png|700px|Right]] To create files or folders remotely, you can right-click the remote window and click 'create directory' or 'create new file'. [[File:Create_directory.png|700px|Right]] [[File:Create_file.png|700px|Right]] As you can see, the menu has some more interesting options, for example 'rename' or 'view/edit'. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. [[Category:Files]] 53f79629980f29a8dc7f23c1e78eb6aa6c08c8f4 0 36 706 160 2019-08-28T15:12:07Z Bert 8 wikitext text/x-wiki ULYSSIS doesn't support ftp, because it is insecure. However, we support sftp (ftp over ssh). This works similar as ssh. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Non-graphical methods== The most common way to transfer files is with a terminal by using the <code>scp</code> command.<br/> Copying file to host:<br> <code>scp SourceFile user@host:directory/TargetFile</code><br> Copying file from host:<br> <code>scp user@host:directory/SourceFile TargetFile scp -r user@host:directory/SourceFolder TargetFolder</code> You don't need to use the full path to your file. You may you the relative path, starting from your home directory. For example:<br> <code>scp index.html user@ssh1.ulyssis.org:www/index.html</code> ==Graphical methods== The graphical methods are explained in [[Accessing your files]]. [[Category:Files]] 02f4eb3a02f7c28be5320fcfb15653c79067e0f1 0 41 708 190 2019-08-28T15:12:13Z Bert 8 wikitext text/x-wiki ULYSSIS takes backups of all files, databases, settings and repositories 1-4 times a week. These backups can be restored in case of severe server failure or in case of an emergency (if for example a user by mistake deletes all of their site). It is, however, more convenient that users take their own backups when they do experimental things on their account. == A backup of your files == You can use the graphical methods described in [[Accessing your files]] to download a copy of all of your files. This copy, or certain files, can then easily be uploaded again using the same method to restore backups == A backup of your databases == To take a backup of your database you simple use the export function of PHPMyAdmin as described on [[Using PHPMyAdmin]]. [[Category:Files]] b192829762259c9e965b92d72d9e7af19c0ac567 0 104 709 628 2019-08-28T15:12:18Z Bert 8 wikitext text/x-wiki PHP code is run with PHP-FPM as your ULYSSIS user. This means you can tighten up you website's security by denying other users the permission to read your PHP files. However, due to the way the Apache webserver works, it must be able to determine the existence of your PHP files. Non-PHP files in your www directory must remain readable by other users, because Apache reads these as it's own user. === Recommended permissions === * Homedirectory: See [[#Homedirectory permissions | homedirectory]] * www directory (and other directories from where websites are served), including subdirectories: <code>0705/drwx---r-x</code> * Website files (css, images, html, ...): <code>0604/-rw----r--</code> * Configuration files containing secrets/passwords: <code>0600/-rw-------</code> * Other directories and files that are not part of a website: <code>0600/-rw-------</code> or <code>0700/-rwx------</code> === Securing database login info === Suppose you have a file called <code>config.php</code>, containing login information for your database. To secure this information, you can make it readable and writeable by only you, and nobody else using <code>chmod 600 config.php</code>. In FileZilla, you can do this by right-clicking on the config file, clicking on "File permissions...", and changing the permissions according to the following screenshots: [[File:config-php_dropdown.png]] [[File:config-php_attrs.png]] === Securing uploads directory === Also, if there are directories that you made writeable by others, e.g. an uploads folder, this is no longer necessary. If this directory is called <code>uploads</code>, you can remove write rights for others with <code>chmod go-w uploads</code>. In FileZilla, you can do this by right-clicking on the config file, clicking on "File permissions...", and changing the permissions according to the following screenshots: [[File:uploads_dropdown.png]] [[File:uploads_attrs.png]] === Homedirectory permissions === In order to prevent other users entirely from accessing files in your homedirectory, the permissions on your homedirectory should only allow yourself and the www-data user access. This is by default configured properly for you from the 29th of July, 2018 onward. Note that you should still follow the guidelines as detailed above. If you have changed your permissions on your homedirectory and want to restore the defaults, you can execute <code>nfs4_setfacl -S /home/user/acl ~</code>. The file <code>/home/user/acl</code> contains the default permissions. [[Category:Files]] 95127586c57dc91461e0d284f2d127c8d2215b96 14 116 710 2019-08-28T15:12:30Z Bert 8 Created blank page wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 37 712 614 2019-08-28T15:13:16Z Bert 8 wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <syntaxhighlight lang="apache">Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</syntaxhighlight> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' Do not place sensitive files inside the web accessible folder.Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.</div> It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [[Managing_Cron_jobs | cronjob]] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than were it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> Or, for Python 3: <pre>virtualenv ~/.venv --python=python3</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <syntaxhighlight lang="python">#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </syntaxhighlight> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [http://flask.pocoo.org/docs/0.10/deploying/fastcgi/ Flask documentation for FastCGI] [[Category:Webserver]] 0847db7c2eef01c858a8a00dc16764d00dc56b6d 0 9 713 688 2019-08-28T15:13:20Z Bert 8 wikitext text/x-wiki You can find all your apache logs (like the access.log and error.log) on all of our shell servers in the directory: /var/log/apache_user/''username'' So if your username is ''foobar'' then you can easily access your logs this way: foobar@zap:~$ cd /var/log/apache_user/foobar foobar@zap:/var/log/apache_user/foobar$ ls foobar.ulyssis.be foobar@zap:/var/log/apache_user/foobar$ cd foobar.ulyssis.be foobar@zap:/var/log/apache_user/foobar/foobar.ulyssis.be$ ls access-2014-05-07.log error-2014-05-07.log foobar@zap:/var/log/apache_user/foobar/foobar.ulyssis.be$ tail error-2014-05-07.log [Wed May 07 01:27:14 2014] [error] [client 10.0.0.1] File does not exist: /home/user/foobar/www/favicon.ico If you can't find your username inside of <code>/var/log/apache_user</code>, don't worry. If you enter it with <code>cd foobar</code>, it will automatically appear. ==With FileZilla== You can also access the log files with an SFTP client, like FileZilla. Just enter <tt>/var/log/apache_user/''username''</tt> (replace ''username'' with your username) on the right hand side, where it says "Remote site", and press <tt>Enter</tt>: [[File:Logs.png]] [[Category:Webserver]] 6634c12552c8910eb36fcdac3bae6a5bfab5a914 0 8 714 360 2019-08-28T15:13:23Z Bert 8 wikitext text/x-wiki PHP errors are not displayed by default. If an error occurs, you will simply get a blank page. This is for security reasons: this way, an attacker doesn't know about possible vulnerabilities of your website. If you want to see PHP errors, you can log them to a file, or enable the display of errors. = Logging errors to a file = If your username is ''foobar'', create a <code>.htaccess</code> file (for example: <code>~/www/.htaccess</code>) with this content, if you are a regular user: php_flag log_errors on php_value error_log /home/user/foobar/php_error.log Or if you are an organization: php_flag log_errors on php_value error_log /home/org/foobar/php_error.log = Displaying errors = Create a <code>.htaccess</code> file (for example: <code>~/www/.htaccess</code>) with this content: php_flag display_errors on [[Category:Webserver]] a2c977bcb4d1209234a160798384b3a1e9ab125b 0 32 715 136 2019-08-28T15:13:26Z Bert 8 wikitext text/x-wiki Just like PHP errors, you can set PHP options you would normally set in php.ini using .htaccess. You just add the option preceded by php_flag and follow by the value: php_value upload_max_filesize 20M php_value post_max_size 25M php_value memory_limit 32M You can of course also use the [http://be2.php.net/manual/en/function.ini-set.php ini_set] function. [[Category:Webserver]] d7fc1f53a37610765d9f6458436b934ceeaa2c80 0 114 716 697 2019-08-28T15:13:30Z Bert 8 wikitext text/x-wiki Sending email is fairly similar on most hosting services. ULYSSIS hosting is not too different in that sense. We do use a queueing system to detect accounts that are being abused by malicious actors to send spam. == How? == In PHP and most other programming languages, content management systems (CMS), and frameworks, you can use the buildin email function. This may be referred to with names such as buildin, default, standard, local or sendmail. == Delay and limitations == The delay and limit will be changed on 11 september 2019 to 5 minutes and a maximum of 50 mails for each user in that amount of time Because of the large amount of users on our hosting services, security breaches and misconfigurations due to user mismanagement happen from time to time. As many malicious actors focus their efforts on abusing servers with a good reputation for the distribution of spam, it is not uncommon to find several thousands of emails being sent once a problem occurs. To combat this, ULYSSIS hosting delays sending of emails for up to 15 minutes and verifies a certain amount of email is never surpassed. If at any point the level is surpassed, ULYSSIS is notified and can take action, while probable spam is stopped from being transmitted. Therefore it is important to keep a potential delay in time when expecting email from your website, but also not to send vast amount of email all at once. It is in general good practice to spread the transmission of for example an email list with several hundred participants. [[Category:Webserver]] 2a4934c244d092785a603a6231ce49871e20f382 0 11 717 584 2019-08-28T15:13:34Z Bert 8 wikitext text/x-wiki By default, your website is accessible at the following URLs: * http://''username''.ulyssis.be * http://''username''.studentenweb.org Where ''username'' is your ULYSSIS user name. If you wish, you can also register another domain name. ULYSSIS isn't a domain name registrar, so you'll have to use an external registrar. For example, you can find a list of all registrars for .be at [http://dns.be dns.be]. If you have registered your own domain and you want to use it with your ULYSSIS account, you need to: # Point your domain name to the following ULYSSIS nameservers: ## ns.ulyssis.student.kuleuven.be ## ns3.ulyssis.student.kuleuven.be ## Optionally: ns2.ulyssis.student.kuleuven.be # Mail us at ulyssis@ulyssis.org, with the following details: ## Your ULYSSIS username ## The domain name you registered ## The directory that you want the domain to point at. This could be your <code>www</code> folder, but any other folder within your home directory is possible. ## Whether you want to receive e-mail at that domain name via ULYSSIS. Note that we need to request this with ICTS, so this will take a while. Please do keep in mind that, just like any change to an account, this can only be requested by the account holder. You can find more information about DNS at http://en.wikipedia.org/wiki/Domain_Name_System. [[Category:Webserver]] 59a65b7bab22acee1662aabb6da3e229297b6bf6 0 10 718 603 2019-08-28T15:13:38Z Bert 8 wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. For the first installation of a certificate, you will have to generate a new key as well as a certificate. For renewals, please '''always''' reuse the old key, so we only have to replace your certificate and not the key every few months. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder ''letsencrypt'' in your home folder. Then add a folder per domain or group of domains, then add the relevant files to the right domain folder. Please keep in mind that it is always good practice to have your key be only readable by you, so check your permissions. Always remove irrevelant files, we won't search for the right certificate. Rename your files like this: chain.pem -> interestingdomain.be.chain cert.pem -> interestingdomain.be.crt privkey.pem -> interestingdomain.be.key Your structure should look something like this: letsencrypt/ ├── interestingdomain.be │   ├── interestingdomain.be.chain │   ├── interestingdomain.be.crt │   └── interestingdomain.be.key └── otherdomain.com ├── otherdomain.com.chain ├── otherdomain.com.crt └── otherdomain.com.key Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ===Check certificate for common mistakes=== You can check if your certificate will likely be okay with a command-line tool on our shellservers: <kbd>ulyssis-certificate check interestingdomain.be</kbd>. If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] 655e381295f1590df5ce819b1e5359de110f88e4 0 33 719 615 2019-08-28T15:13:43Z Bert 8 wikitext text/x-wiki Shibboleth is the software powering the Central KU Leuven Login. It's a piece of software used by many universities to supply identification and access management. ULYSSIS works together with ICTS to supply limited access to Shibboleth. We are however only able to supply Shibboleth to those approved by ICTS. In practice all faculty unions will be granted access if they can prove they have the technical ability to use Shibboleth in a safe and privacy friendly way. For other organisations it can be more difficult to get access, therefore it is best to write an extensive explenation of what you plan to do with Shibboleth, why your organisation requires it, what your organisation does, and other relevant information. We will then contact ICTS with your request. == How to request == To request Shibboleth access, you first need to make sure the domain you wish to use Shibboleth on has valid SSL certificates. Lately ICTS has been pushing that all traffic to the website is already over HTTPS before Shibboleth is issued. For more info you can check [[Getting SSL]] If you have SSL set up you need to send an email to request Shibboleth to ulyssis@ulyssis.org. The email must contain the following info: * What domain you wish to use Shibboleth on (this must be a single domain, so keep subdomains and www in mind) * What you will be using Shibboleth for and in general what your application will do. This explanation is required by ICTS. If you fail to convince them they will not grant your domain access. * What attributes you wish to use and what you will do with them (and whether you will store them). You can find the list of attributes on https://admin.kuleuven.be/icts/services/aai/attributes * Explicitly state you grant ULYSSIS permission to edit the .htaccess file to be able to export the required Shibboleth Metadata * If you are not a recognised faculty union you will need to include an extra motivation why you require Shibboleth (as noted above) If your application is complete and correct we will file a formal request. We will of course notify you of ICTS' response. == Deploying Shibboleth == After you have been granted access you can soon start using Shibboleth. The first step is to add the following lines to your .htaccess ShibDisable Off AuthType Shibboleth require shibboleth ShibRequireSession off We disable certain features of Shibboleth here because it will otherwise interfere with any other HTTP-auth options you might be using. Now that you have added this information to .htaccess you are able to serve requests to Shibboleth.sso, if your request is well-formed the sso will handle communication with the IdP (identity provider) of the KU Leuven. A login link follows the following syntax: https://[YOUR_HOSTNAME]/Shibboleth.sso/WAYF/kuleuven?target=[URLENCODED_RETURN_URL] And logout links: https://[YOUR_HOSTNAME]/Shibboleth.sso/Logout?return=[URLENCODED_DISPLAY_URL] It is important to note that on logout the user will stay on the KU Leuven's IdP-page and your link will only be displayed. The user will NOT be redirected (even though this is the normale behaviour according to the Shibboleth documentation). As soon as a user is logged in, his or hers attributes will be available to your application. Attributes are certain properties that an account may have and that supply further information about them. Some examples are: first name, last name, mail, student id. All of these will be available as HTTP headers. But keep in mind that apache might prefix those with REDIRECT_ multiple times (for example when mod_rewrite is used). For an overview of all attributes you can check out http://shib.kuleuven.be/secure/allAttributes More general information on the KU Leuvens implementation can be found on http://shib.kuleuven.be/ . But be aware of the fact that some of the documentation is very outdated (Most notably information about shib 1.3) [[Category:Webserver]] 076b475e1a1ae6d008447767e26489e4bc1b579b 0 53 720 609 2019-08-28T15:13:47Z Bert 8 wikitext text/x-wiki Because in our webserversetup PHP is installed as a FastCGI Proxy basic authentication will not work in its usual way. There is however a workaround. First add a .htaccess file with following code in it: <IfModule mod_rewrite.c> RewriteEngine on \n RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization},L] </IfModule> Next add the following line to your script right before the authentication: <syntaxhighlight lang="php">list($_SERVER['PHP_AUTH_USER'], $_SERVER['PHP_AUTH_PW']) = explode(':' , base64_decode(substr($_SERVER['HTTP_AUTHORIZATION'], 6)));</syntaxhighlight> Now your script should work with basic authentication. [[Category:Webserver]] 61b6abf6355ce0144e4d459eb256681d4edbaa66 0 102 721 544 2019-08-28T15:13:51Z Bert 8 wikitext text/x-wiki == Short answer == You can't, no use in trying. == Long answer == We do not permit aribitrary access to ports from our firewall and users are not supposed to try claiming ports. We offer classic webhosting, version control, and basic shell access. You are free to run applications, within bounds of what is reasonable, legal and ethical, on our shellservers. But they cannot claim arbitrary ports and you won't be able to access those ports anyway. Besides the fact that this is not a service we wish to offer, it's also very hard to do this in an orderly and secure way. We would have to assign users specific ports, and check those are used correctly, furthermore proxies would be necessary for production, as no one wants their visitors to be forced to enter port numbers. Beyond that, there are tons more practical issues that would have to be solved. In most cases, you are better off using FastCGI or CGI. We support both of these protocols, and have documentation and examples for our users on [[Using (Fast)CGI for non-PHP websites]]. If this is not what you are looking for, then we are afraid you will have to look at other services, such as VPSes, by commercial providers. [[Category:Webserver]] 5cd0a43f9d8e899243ad9dce28c82bde54ef2f33 752 721 2019-08-28T15:22:42Z Bert 8 wikitext text/x-wiki == Short answer == You can't, no use in trying. == Long answer == We do not permit aribitrary access to ports from our firewall and users are not supposed to try claiming ports. We offer classic webhosting, version control, and basic shell access. You are free to run applications, within bounds of what is reasonable, legal and ethical, on our shellservers. But they cannot claim arbitrary ports and you won't be able to access those ports anyway. Besides the fact that this is not a service we wish to offer, it's also very hard to do this in an orderly and secure way. We would have to assign users specific ports, and check those are used correctly, furthermore proxies would be necessary for production, as no one wants their visitors to be forced to enter port numbers. Beyond that, there are tons more practical issues that would have to be solved. In most cases, you are better off using FastCGI or CGI. We support both of these protocols, and have documentation and examples for our users on [[Using (Fast)CGI for non-PHP websites]]. If this is not what you are looking for, then we are afraid you will have to look at other services, such as VPSes, by commercial providers. [[Category:Webserver]] [[Category:Shell]] dcb1b975000e716488b28d14f642c53392edbafa 14 117 722 2019-08-28T15:13:58Z Bert 8 Created blank page wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 109 723 651 2019-08-28T15:14:43Z Bert 8 wikitext text/x-wiki By default, any ULYSSIS account comes with a single email address, specifically your username on our main domain, ulyssis.org: <code>''username''@ulyssis.org</code>. You can either use this address as your only mailbox, or as a forwarder to another email address. You can find more information about your mailbox [[Mailbox|here]]. For any other addresses, you will need a domain (for example a .com or .be). It is possible to have a domain already connected to your ULYSSIS account as a regular website, but not activated for email. It is also possible to use a domain just for email and not for a website. More information about adding and activating domains can be found [[Adding_domain_names|here]]. Keep in mind ULYSSIS does not currently sell domains, but you can buy them from lots of different companies. If you have an email domain activated on your account, you will be able to add [[forwarders]] in our control panel [https://ucc.ulyssis.org UCC]. You can create as many forwarders as you like, and have the addresses forward to a single address or several. Lots of organisations use forwarders as an easy way to contact a team of people responsible for a certain task, for example your PR team or the president of your organisation. This way you can have an address such as preses@kringleuven.be forward to jan.peeters@gmail.com, but can easily change it every year. This way external contacts only have to use a single address and will always end up contacting the right people. Since forwarders relay emails to one or several addresses, you may want to reply using the forwarder address instead of your personal one. In that case you want to [[Using_a_forwarder_as_an_alias|add an alias]]. We offer instructions for our own webmail, the Thunderbird email client, Gmail and Hotmail/Outlook.com. If instructions are missing for your email client or service, we can of course try and help you if you send us an email. Currently we do not offer mailboxes for your own domains, only the single mailbox that comes with your account by default. If you have any further questions about email, you can always contact our team at ulyssis@ulyssis.org [[Category:Mail]] 38b23310b3fc1ddc147dbd8171edd70f3b316a26 0 19 724 643 2019-08-28T15:14:46Z Bert 8 wikitext text/x-wiki Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mailbox regularly, because all important information will be sent to this address. You can check your e-mail using the webmail or an email client of your own. It is also possible to configure your email address in UCC to automatically [[Forwarders|forward]] all correspondence to another address. ==Webmail== You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to enter the website. ==POP and IMAP access== You can access your ulyssis mail by POP or IMAP protocol. The configuration parameters are: * '''server''': <tt>mail.ulyssis.org</tt> * '''username''': ''your ULYSSIS username'' * '''password''': ''your ULYSSIS password'' * '''security''': SSL ==SMTP== ULYSSIS doesn't offer SMTP. Instead, you can use KULeuven's SMTP server: * '''server''': <tt>smtps.kuleuven.be</tt> * '''port''': 443 * '''username''': ''your student id'' * '''password''': ''your KULeuven password'' * '''security''': SSL == Advanced == Your emails are stored within your account under ~/Maildir. These files can of course be read with a command line email client such as alpine or mutt. We support sendmail style local delivery using .forward. More information is available in the official documentation of [https://www.sendmail.org/~ca/email/doc8.9/op-sh-2.html#sh-2.8 Sendmail] and [http://www.postfix.org/local.8.html Postfix]. You can also use procmail on our servers. A very detailed explanation on procmail is available on the [https://wiki.archlinux.org/index.php/Procmail ArchWiki]. [[Category:Mail]] bbc30fd50c2a3535ce4db4e24c84da60e27a1a52 0 43 725 636 2019-08-28T15:14:50Z Bert 8 wikitext text/x-wiki You may want to receive e-mail from ulyssis on another email provider. It is very easy to set this up. == Change the forwarders for your @ulyssis.org email address == # Go to ucc.ulyssis.org and log in with your username and password. # On the right side, click on '''Mail'''. # Under '''Address forward''' you can change the forward address of your ULYSSIS mail by clicking on '''edit'''. # Choose '''forward''' and enter the email address you want to forward your ULYSSIS mail to and save the changes. # If you forward to Gmail, Hotmail. or use Thunderbird, we recommend looking at [[Using a forwarder as an alias]] so you can send mails under the forwarding address instead of just your own. == Change the forwarders for other domains == # Go to ucc.ulyssis.org and log in with your username and password. # On the right side, click on '''Mail'''. [[File:Forwarder Step1.png|700px]] # Under '''Virtual Domains''', click on the domain you want to change. [[File:Forwarder Step2.png|700px]] # You can change a forwarder by clicking on '''edit''' or on '''Add alias''' and add the forwarders you want. [[File:Forwarder Step3.png|700px]] # Save your changes == Use your mailbox and forwarders at the same time == An alternative way to set the forwarders, that will also allow you to use your mailbox and the webinterface, is to use a .forward file. On each line of this file, you can specify to wich addresses you want to forward the email. If one of the addresses is the same as your @ulyssis address, then the mail will also be placed in your ULYSSIS mailbox. In the following example, your @ulyssis email address is <code>user@ulyssis.org</code>. Example .forward file: user@ulyssis.org example@gmail.com example2@skynet.be This will place the email in your ULYSSIS mailbox so that you can access it from the webinterface or your local mailclient. It will also forward the mail to <code>example@gmail.com</code> and <code>example2@skynet.be</code>. To use this, place a .forward file with the prefered email addresses in your homedir, see [[Accessing your files]], and set your forwarder to 'Inbox' in https://ucc.ulyssis.org/mail [[Category:Mail]] 35990622dffe6e7d8c31a3005c38f4d7e3701ce5 0 80 726 410 2019-08-28T15:14:53Z Bert 8 wikitext text/x-wiki You may want to send an email from your @ulyssis address or one of your forwarders. You can do this using the [https://webmail.ulyssis.org ULYSSIS Webmail] (for other clients see [[Add an alias in Gmail]], [[Add an alias in Thunderbird]] and [[Add an alias in Hotmail/Outlook]]) # Login into the [https://webmail.ulyssis.org webinterface] using your ulyssis account and passsword # Go to '''Settings''' (dutch: '''Instellingen''') in the top right # Go to '''Identities''' (dutch: '''Identiteiten''') # Click on the plus sign in the bottom left # Fill the alias you want to use in in the '''Email''' (dutch: '''E-mail''') field and the name you want to be displayed in front of the address in the '''Display Name''' (dutch: '''Weergavenaam''') field. All the other fields are optional. # Click on '''Save''' (dutch: '''Opslaan''') You can now select the alias when creating an email in the webinterface. [[Category:Mail]] be2b8bbb315a972313511da25b5400b96c8ce33f 0 34 727 155 2019-08-28T15:14:57Z Bert 8 wikitext text/x-wiki You may want to send e-mail from Gmail using your @ulyssis.org-address, or another domain name that you use for your account. Gmail allows you to do this, but asks for SMTP info. We don't provide SMTP on our own mail server, but you can use the SMTP servers of the KU Leuven. # In Gmail, go to '''Settings''' (in Dutch: '''Instellingen'''). # Go to the tab '''Accounts and Import''' (in Dutch: '''Accounts en import''') # Under '''Send mail as:''' ('''E-mailberichten sturen vanaf'''), click on: '''Add another email address you own''' ('''Nog een e-mailadres toevoegen waarvan je eigenaar bent'''). # Fill in your name and the e-mail address, and check '''Treat as an alias.''' ('''Beschouwen als alias.''') More info: https://support.google.com/a/answer/1710338 # Click on '''Next step''' ('''Volgende stap'''). # Fill in the following information SMTP information (https://admin.kuleuven.be/icts/services/email/begrippen): #* '''SMTP server''': '''smtp.kuleuven.be''' #* '''port''': 465 #* '''Username''': your student id #* '''Password''': your KU Leuven password #* SSL # Press on '''Add Account''' ('''Account toevoegen'''). [[Category:Mail]] 7558a8e3ed485f4e910de558487130de04b029eb 0 72 728 365 2019-08-28T15:15:00Z Bert 8 wikitext text/x-wiki You may want to send e-mail from Hotmail using your @ulyssis.org address, or another domain name that you use for your account. Hotmail allows you to do this by configuring a few settings. Because you should only be able to send mails from an e-mail address you actually own, make sure that you configured receiving mails before starting this process. Hotmail will send a confirmation mail to the provided e-mail address to confirm that you own it. Note that Outlook's SMTP will still add your original address as "Sender" in the mail headers. Depending on the recipient's mail client, he might still see this. If you use a local mail client, you might be able to avoid this by using a custom SMTP server. #Click on the gear icon at the top right and choose '''Connected accounts''' (Dutch: '''Verbonden accounts''') #At the bottom you see the title '''Email aliases''' (Dutch: '''E-mailaliassen''') with a link '''Manage or choose a primary alias''' (Dutch: '''Primaire alias beheren of kiezen''') below. Click it. You will have to log in again to proceed. #Click on '''Add Email''' (Dutch: '''E-mailadres toevoegen''') and choose the second option: '''Add an existing email address as a Microsoft account alias''' (Dutch: '''Een bestaand e-mailadres als een Microsoft-accountalias toevoegen'''). Fill in the e-mail address you want to use to send mail from, and click '''Add alias''' (Dutch: '''Alias toevoegen''') #At this point, you should receive an e-mail on the address you just provided. It will contain a URL to confirm adding the alias. Click it. #At this point, you have confirmed that you are the owner of the e-mail address. Congratulations, you can now use it to send mail! [[Category:Mail]] 526f13e0b273f2cdfb6dafeb04f57c818d53ecd5 0 77 729 403 2019-08-28T15:15:04Z Bert 8 wikitext text/x-wiki You may want to send e-mail from Thunderbird using your @ulyssis.org-address, or another domain name that you use for your account. Thunderbird allows you to do this, but to configure this properly, you should not use your provider's SMTP server. They will add an extra header stating the original e-mail address the e-mail is sent from. Some e-mail clients show this information, which might be unwanted. The KU Leuven also provides an SMTP server which you can use as a student. It accepts e-mail originating from any e-mail adress, and can therefore be used for this purpose. It should be noted that this is an '''authenticated''' server, so any potential abuse can be tracked back to you. You should '''not''' use this for any malicious purpose. == Adding the KU Leuven SMTP server in Thunderbird == If you already have set up your KU Leuven e-mail in Thunderbird, you can skip this step and proceed to [[#Configure an identity for your e-mail account]] below. Go to your '''Account Settings''' (Edit > Account Settings or Tools > Account Settings, depending on your operating system). At the bottom of the left sidebar, you will find an entry named '''Outgoing Server (SMTP)'''. Click this to access your SMTP settings. In your SMTP settings, you should see a list of existing SMTP servers. We want to add a new entry, so click the '''Add...''' button. In the screen that pops up, fill in the settings as in the example screenshot below. Replace the displayed user name with your own student number. You will have to fill in the corresponding password on first use. [[File:Thunderbird-SMTPS.png]] == Configure an identity for your e-mail account == Back in the '''Account Settings''' screen, click on your e-mail address (not on any of its children). In the screen that opens, there will be a button '''Manage Identities...''' at the bottom. Click it. In the new screen, there will be one existing identity already: the default identity corresponding with your normal e-mail address. We want to add a new identity, so click the '''Add...''' button. In the screen that pops up, fill the name and e-mail address you wish to use. At the bottom, make sure you choose the SMTP server of your student account. This is shown in the image below. [[File:Thunderbird-Identity.png]] == Sending your first e-mail == When you compose a new e-mail, you can change the sender in the "From" field to the identity you just configured. If everything was installed correctly, Thunderbird will show you a pop-up to enter your KU Leuven password when you try to send the e-mail. In this pop-up, you can choose to save this password for later use. [[Category:Mail]] 56d079af486b1e084e0f07e823887fb184d4587c 0 17 730 87 2019-08-28T15:15:08Z Bert 8 wikitext text/x-wiki <p>You can use our shell-servers to forward mails from your KULeuven mailbox to an email provider of your choice (e.g. GMail).</p> <p>DOING THIS IS ENTIRELY ON YOUR OWN RISK. ULYSSIS CANNOT BE HELD RESPONSIBLE FOR LOST/DELAY MAILS. BY HAVING OUR SERVERS FORWARD YOUR KULEUVEN MAIL, YOU TAKE FULL RESPONSIBILITY.</p> <p>This tutorial is based on http://ronin.ulyssis.be/files/kulmail_gmail2.txt</p> <p>We wrote a script that configures everything automatically. To use it, log in on one of our shell servers and execute the following commands:</p> <ul> <li>wget ftp://ftp.ulyssis.org/kulforward/kulforwardsetup.sh</li> <li>chmod u+x kulforwardsetup.sh</li> <li>./kulforwardsetup.sh</li> <li>Follow the instructions on the screen.</li> </ul> <p>Alternatively, you can configure everything yourself. Below we briefly explain how to do this.</p> <ul> <li>Create a directory to save the SSL certificates:<br />mkdir .certs</li> <li>Put the necessary certificates in the .certs directory:<br />cd .certs<br />wget ftp://ftp.ulyssis.org/kulforward/imapkul.pem<br />wget ftp://ftp.ulyssis.org/kulforward/usertrust.pem<br />cp /etc/ssl/certs/AddTrust_External_Root.pem .<br />cd </li> <li>Rehash them:<br />c_rehash ~/.certs/</li> <li>Create the fetchmail configuration file with your favourite text editor and enter the confiration details:<br /> $login = your KULeuven login (e.g. s0123456)<br /> $pass = your KULeuven password<br /> $mail = the email address to forward your KULeuven mail to (TRIPLECHECK IT!!)<br /> keep = "" (delete forwarded mails from your KULeuven mailbox) or "keep" (keep forwarded emails)<br /> set daemon 600 # Check every 10 minutes<br /> poll imaps.student.kuleuven.be port 993 protocol imap username "$login" password "$pass" smtpname "$mail" ssl sslcertck $keep sslcertpath .certs/</li> <li>Add it to your crontab<br /> crontab -e<br /> @reboot fetchmail </li> <li>Because of our setup fetchmail cannot be started automatically when the shell server is restarted. But you if you add it to your crontab, you'll get email that it failed. You can then manually login on our shell servers to start fetchmail again.</li> <li>Start fetchmail:<br /> fetchmail</li> </ul> [[Category:Mail]] 89891388d7b409ab64e599394602f42be6ba85cd 14 118 731 2019-08-28T15:15:19Z Bert 8 Created blank page wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 47 732 215 2019-08-28T15:15:48Z Bert 8 wikitext text/x-wiki This page will go through a basic setup of MediaWiki. It is based on [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wikipage], and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. This tutorial we'll use a ULYSSIS-account with username "me". =Putting setup-files in place= First we'll have to download the setup file which you can find over at [http://www.mediawiki.org/wiki/Download the official MediaWiki website]. It's an archived file, so you need to extract it first and put the files in a subdirectory of your "document root". The default is just a www directory in your home folder. Putting your files in document_root/wiki/ will make your wiki be located at usersname.ulyssis.be/wiki/. If you prefer, you can do this all graphically using the manual [[Accessing_your_files]]. If you prefer the command line; <pre> homeuser@home:~$ ssh me@ssh1.ulyssis.org enter super secret password: me@zap:~$ wget http://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.6.tar.gz me@zap:~$ tar xvxf mediawiki-1.23.6.tar.gz me@zap:~$ mv mediawiki-1.23.6 www/wiki me@zap:~$ rm -r mediawiki-1.23.6.tar.gz </pre> =Setting up database= Like the [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wiki] tells us, we have three different options to choose from; PostgreSQL, MySQL and SQLite. It's easy to set a PostgreSQL or MySQL database; just go to the UCC. For this tutorial we will continue with a MySQL database (PostgreSQL installation steps are quite similar). Let us visit https://ucc.ulyssis.org/mysql; if this is your first time using MySQL you'll need to create a new account by putting in a super secret password. The wizard will create your MySQL account with the same name as your user-account. We'll also create a new database with an appropriate name by clicking on 'Add database'. In this tutorial we will choose; "wiki", notice that it will be prepended with our username, so we'll end up with a new database named "me_wiki". =Setup your wiki= If all went well, you can access your website at http://username.ulyssis.be/the_folder_you_used and start the setup wizard. In our example, will surf to http://me.ulyssis.be/wiki. The wizard will guide you through some configuration options. Most of them our pretty straight-forward. When in doubt, you can always click the question mark wich will show you some sensible and recommended default... We'll just discuss the page were the wizard asks you for the database. In our example; <pre> Database host: mysql.ulyssis.org Database name: me_wiki // The name of our database; i.e. the name we chose, prepended by our username. Database table prefix: // We can leave this blank. Database user: me // This is the name of our MySQL-user, which was named after our ULLYSIS-username. Database password: supersecretpassword // Please note that this is not your ULLYSIS-password, but the password you used in UCC when creating the MySQL user! </pre> =Creating the wiki= After the setup wizard is complete, you can begin the installation procedure. If all went well, you'll be greeted by a page which congratulates you with your new installation. =Finalizing steps= The setup will offer you a configuration file (containing some settings you specified) that you need to download to your server (more specifically in directory where your MediaWiki-files reside in). You again can do this graphically, or if you prefer a terminal; <pre> homeuser@home:~$ scp path_to_file/LocalSettings.php me@ssh1.ulyssis.org:~/www/wiki enter super secret password: </pre> After this is done, you can finally start using your wiki. !!! Note that this is only a very basic case of a wiki install. Please refer to [http://www.mediawiki.org/wiki/MediaWiki the original MediaWiki wiki] for a more in depth source. !!! !!! Please know that managing a wiki comes with great responsibility, keep your wiki up to date and follow healthy and recommended security practices. !!! [[Category:CMSs]] f6dcdb9a2cd4105701f2a6930a60be6496495931 0 49 733 465 2019-08-28T15:15:52Z Bert 8 wikitext text/x-wiki ==Installing Joomla on our servers is definitely easy== Installing Joomla on our servers is definitely easy. You download the install components from the http://joomla.org joomla-site. Here you get a compressed file (.zip) which you have to extract.. You get a folder with files, those files (so no the folder) you copy via filezilla or an other ftp programme to your www-map on your shellaccount. Afterwards you go to your account, I.E username.ulyssis.be, here you get a notification telling you your MySQL database needs to be configured. The fist part is the "main configuration" which will be individual for every user. Afterwards click on ''Next'' which will prompt you for your database credentials & information: *'''Databasetype: ''' Select ''MySQL'' from the dropdown. *'''Hostname: ''' this is the location of the database server, use <code>mysql.ulyssis.org</code>. *'''Username: ''' this is the name you gave during the creation of your mysql account, often this is the same as your username with ULYSSIS. *'''password: ''' the password hat you gave during the creation of your mysql account * You don't change the last two fields When you're done click on “Next” twice since ftp is already configured. Here you can see the last few details. Afterwards the install will run by its own and that's it, you have succesfully installed Joomla. ==Setting up multiple instances of Joomla== If you want to have multiple instances of a Joomla site then you the create a new folder in your homedir from your shell account. You need a new virtual host, you can send us an [mailto:ulyssis@ulyssis.org email] and we will create one for you. After your new virtual host is ready, you need to do all the same steps as for a regular Joomla installation. Another option is to use the Joomla [https://docs.joomla.org/Multiple_Domains_and_Web_Sites_in_a_single_Joomla!_installation multisite] option. [[Category:CMSs]] 3dcece46cebcf80845fe4dc42f267417ea4d4046 0 50 734 529 2019-08-28T15:15:56Z Bert 8 wikitext text/x-wiki ==How to install Drupal for your account== First you will need to install Drupal from their website, http://drupal.org. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. The files that you've extracted will need to be moved to your www-directory on your shell account. You can do this by copying them there using Filezilla or any other FTP client. After you've copied those files to your www-directory, you'll have to go to your account on *your username here*.ulyssis.be. Click on the Drupal directory and the installer will start loading. First it will ask you to choose a language and after that a profile. If you do not know what profile to choose, you should choose the standard one. If the installer doesn't skip the ''Verify requirements'' page, then you should just follow the steps described there. Finally the installer will ask you to set your database configuration: *'''Database name:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll have to create it here. The default database is: "username_username". *'''Database username:''' The name you used during the creation of your database account. *'''Database password:''' The password you used during the creation of your database account. *'''Database host:''' This is <code>mysql.ulyssis.org</code>. You will need to click on ''Advanced options'' to set this option. After that you can proceed in the wizard where you can fill in some last few details. By then the wizard will do the rest except for asking some basic questions about the site and, congratulations, you have installed Drupal. ==Setting up multiple instances of Drupal== If you want to have multiple instances of a Drupal site there are two options. The multiple instances can either share drupal code or be fully seperate. For fully seperate installs you can simply create a (sub)folder to store another copy of the drupal code in. You can then access it either from your default domain or have us attach another domain to it for you, more info about that on [[Adding domain names]] If you wish for multiple websites to share the same codebase it is easiest to use multiple domains. More information about how to set this up in your drupal is available in the drupal documentation: https://www.drupal.org/documentation/install/multi-site. As soon as you have made your preperations you can contact us about hooking up the domain name, more info about that on [[Adding domain names]] [[Category:CMSs]] 1e827b04d353d3863f5de635a8fa7a9dcbc8855e 0 20 735 637 2019-08-28T15:16:00Z Bert 8 wikitext text/x-wiki ==How to install Wordpress for your account== First you will need to download Wordpress from their website, https://wordpress.org. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. The files that you've extracted will need to be moved to your `www` directory on your shell account. You can do this by copying them there using Filezilla or any other FTP client. After you've copied those files to your `www` directory, you'll have to go to your account on *your username here*.ulyssis.be. You will then receive a notification telling you your <code>wp-config.php</code> has to be created. The easiest way to do this is by following the wizard, so you can click on "Create a configuration file". Go through to the wizard until it prompts you for your database configuration: *'''Database Name/Databasenaam:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll have to create it here. The default database is: "username_username". *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is <code>mysql.ulyssis.org</code> or <code>postgresql.ulyssis.org</code>. It depends on whether you want to use a MySQL or PostgreSQL database. * You don't need to change the last field. After that you can proceed in the wizard where you can fill in some last few details. By then the wizard will do the rest and, congratulations, you have installed Wordpress. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you will need to create a new folder in your www-directory on your shell account. Then you'll need a virtual host for this folder, so you'll have to send us an email asking for this. After your new virtual host has been configured, you will need to do the same steps that you would need to do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about it [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 0ae6595046a842a2168edb9868a7d27d9a9a3204 0 96 736 520 2019-08-28T15:16:05Z Bert 8 wikitext text/x-wiki ==Introduction== Content Management Systems, or CMS's, are easy tools to set up a website without requiring much programming or configuration. However, as is common in a lot of popular and wide-spread software, bugs or errors in the code occur. These errors can be exploited by hackers to gain access to websites or databases connected to those CMS's. Whenever a new update for a CMS, or other popular software (MediaWiki, PhpBB) is released, those hackers will try to implement them as fast as possible in order to hack the most websites. This is why it's critical to update a CMS, plugins/themes, or any related software as soon as the update comes out. To help you facilitate this, we have created a tool to help you keep the most popular software up-to-date. Currently this feature is only active if you have an organisation or student union (kring/facultair overlegorgaan) account. ==I received an e-mail!== If you receive an e-mail from the Version Checker, it's best you update the software mentioned in the e-mail as soon as possible. Make sure to download the latest public version, not just any newer version. It's also best to check if any other software you run is up-to-date: not all software is checked by the tool. (As seen below) ==Supported Software== * Drupal, Drupal Modules, Drupal Themes * Joomla (Joomla Plugins are not supported yet) * MediaWiki (MediaWiki Extensions and Themes are not supported yet) * PhpBB, PhpBB Plugins, PhpBB Styles * WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the Version Checker performs the following steps: * Retrieve all outdated software and respective locations from a database, and check their version * Mail accounts using outdated software * Scan relevant files, detect supported software, and store in database ==Stored Data== The following data is stored in the database: * The location of the CMS, plugin/extension or theme * The responsible organisation or student union (kring/facultair overlegorgaan) * The detected software version * The type and name of the software * The update URL for the software * The date the entry was added ==Ignored Paths== The Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. ==Ignored Organisations/Student Unions== In addition to the ignored paths feature, the Version Checker can also ignore specific Organisations or Student Unions entirely. This feature is possible on request, but only after extensive deliberation with ULYSSIS. Enabling this feature also carries possible consequences: no more mails about outdated software, ever (unless enabled on request), no support if/when your account gets hacked (the account will be expired immediately)... [[Category:CMSs]] 4455e2a1254b227917b3f0393c7165ccb0da88df 744 736 2019-08-28T15:19:22Z Bert 8 wikitext text/x-wiki ==Introduction== Content Management Systems, or CMS's, are easy tools to set up a website without requiring much programming or configuration. However, as is common in a lot of popular and wide-spread software, bugs or errors in the code occur. These errors can be exploited by hackers to gain access to websites or databases connected to those CMS's. Whenever a new update for a CMS, or other popular software (MediaWiki, PhpBB) is released, those hackers will try to implement them as fast as possible in order to hack the most websites. This is why it's critical to update a CMS, plugins/themes, or any related software as soon as the update comes out. To help you facilitate this, we have created a tool to help you keep the most popular software up-to-date. Currently this feature is only active if you have an organisation or student union (kring/facultair overlegorgaan) account. ==I received an e-mail!== If you receive an e-mail from the Version Checker, it's best you update the software mentioned in the e-mail as soon as possible. Make sure to download the latest public version, not just any newer version. It's also best to check if any other software you run is up-to-date: not all software is checked by the tool. (As seen below) ==Supported Software== * Drupal, Drupal Modules, Drupal Themes * Joomla (Joomla Plugins are not supported yet) * MediaWiki (MediaWiki Extensions and Themes are not supported yet) * PhpBB, PhpBB Plugins, PhpBB Styles * WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the Version Checker performs the following steps: * Retrieve all outdated software and respective locations from a database, and check their version * Mail accounts using outdated software * Scan relevant files, detect supported software, and store in database ==Stored Data== The following data is stored in the database: * The location of the CMS, plugin/extension or theme * The responsible organisation or student union (kring/facultair overlegorgaan) * The detected software version * The type and name of the software * The update URL for the software * The date the entry was added ==Ignored Paths== The Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. ==Ignored Organisations/Student Unions== In addition to the ignored paths feature, the Version Checker can also ignore specific Organisations or Student Unions entirely. This feature is possible on request, but only after extensive deliberation with ULYSSIS. Enabling this feature also carries possible consequences: no more mails about outdated software, ever (unless enabled on request), no support if/when your account gets hacked (the account will be expired immediately)... [[Category:CMSs]] [[Category:Security & anti-spam]] 234e52124242e351181c64943dd4c8e6ef962409 14 119 737 2019-08-28T15:16:19Z Bert 8 Created blank page wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 98 738 686 2019-08-28T15:18:34Z Bert 8 wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for login through the Central KU Leuven Login (Shibboleth). The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Central KU Leuven Login) enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest github]. Make sure to click the <code>MediaWikiShibboleth.zip</code> download button. Then, unzip the zip file in the <code>extensions/</code> directory in your MediaWiki installation folder. Make sure there is now a <code>MediaWikiShibboleth</code> folder in <code>extensions/</code>. Finally, locate the <code>LocalSettings.php</code> file in your MediaWiki installation folder and add the following lines to it: wfLoadExtension('MediaWikiShibboleth'); $wgGroupPermissions['*']['createaccount'] = false; $wgRevokePermissions['Shibboleth']['editmyprivateinfo'] = true; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. This really defeats the purpose of the extension though. ==Configuration== MediaWikiShibboleth has some configuration options which allow for restricting who can log in to your wiki. These restrictions are cumulative. For example, it is possible to allow only students enrolled in a specific degree or programme to log in. These options work especially well with restricting the access of the wiki to logged-in users only. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code>LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code>LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code>LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code>LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. === Translations === It's possible to translate and modify all public MediaWikiShibboleth messages. The translations can be found in the <code>extensions/MediaWikiShibboleth/i18n/</code>. Dutch (<code>nl.json</code>) and English (<code>en.json</code>) translations are already provided. Even the provided translations can be customized, and we strongly advise you to do so, in order to match them with your Wiki situation. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Login without Central KU Leuven login" to expand a login menu. The new log in page looks like this with "Login without Central KU Leuven login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] [[Category:Security & anti-spam]] 38296489e566f3e93f2c01ae781021383fef2c47 14 120 739 2019-08-28T15:18:42Z Bert 8 Created blank page wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 54 740 418 2019-08-28T15:18:49Z Bert 8 wikitext text/x-wiki ==Google's recaptcha== ===What is recaptcha and how/will it help prevent spam ?=== For answers to those questions you can look at google's page about recaptcha( https://google.com/recaptcha) ===Installation=== This installation guide requires mediawiki '''1.26''' or higher * Go to google's recaptcha administrator page(https://www.google.com/recaptcha/admin) and register your site * Open your *LocalSettings.php* file which is in your mediawiki instalation folder * Put the following piece of text in the above mentioned file <code> require_once "$IP/extensions/ConfirmEdit/ConfirmEdit.php"; wfLoadExtension( 'ConfirmEdit/ReCaptchaNoCaptcha' ); $wgCaptchaClass = 'ReCaptchaNoCaptcha'; $wgReCaptchaSiteKey = ' '''your public/site key here''' '; $wgReCaptchaSecretKey = ' '''your private key here''' '; </code> example of public and private key (https://i.imgur.com/vGJKEXx.png) * mediawiki wil start loading recaptcha in the background and once done wil start using recaptcha for defending you from bots [[Category:Security & anti-spam]] bc7b4dab8b19d9e27d9fdd0ab567ac42592045a4 0 56 741 266 2019-08-28T15:18:55Z Bert 8 wikitext text/x-wiki ==Google's recaptcha== ===What is recaptcha and how/will it help prevent spam ?=== For answers to those questions you can look at google's page about recaptcha(https://google.com/recaptcha) ===Installation=== This installation guide requires drupal '''6,7 or preferably 8''' (or higher). '''Note this installation requires captcha and recaptcha, these are different plugins and not a type error.''' * Go to drupal's captcha page and download the appropriate version at the bottom of the page (https://www.drupal.org/project/captcha) * Go to drupal's recaptcha page and download the appropriate version at the bottom of the page (https://www.drupal.org/project/recaptcha) ** Extract the archives into '''sites/all/modules/[recaptcha/captcha]'''respectively and relative to your own drupal installation '''(this folder may need to be created manually)''' * Now navigate to your drupal administration page in your browser (/admin/modules) ** Search for captcha and enable it ** Search for recaptcha and enable it * Once complete it is '''critical''' to configure your captcha setting in the web interface (/admin/config/people/captcha) '''and do not forget to enable the captcha-points (/admin/config/people/captcha/captcha-points). [[Category:Security & anti-spam]] 1240c6a77c266df2e0badc07bfe838c3c888bfaf 0 57 742 272 2019-08-28T15:19:04Z Bert 8 wikitext text/x-wiki ==Google's recaptcha== ===What is recaptcha and how does/will it help prevent spam ?=== For answers to those questions you can look at google's page about recaptcha(https://google.com/recaptcha) ===Installation=== This installation guide requires joomla '''3.4''' (or higher). * Go to google's recaptcha administrator page(https://www.google.com/recaptcha/admin) and register your site **example of public and private key (https://i.imgur.com/vGJKEXx.png) * Navigate to the admin panel of your joomla instalation ** Select plugins from the extentions panel in the top menu. * Search for recaptcha in the search box ** Enable recaptcha by clicking on the status icon next to recaptcha * One complete it is '''critical''' that you configure your recaptcha properly ** Go to recaptcha's configuration page by selecting recaptcha in the above mentioned panel ** '''make sure you select version 2 (default is version 1)''' ** Fill in the required keys you got on google's recaptcha's administrator page * Once done joomla will begin to require recaptcha's [[Category:Security & anti-spam]] 2605e8e015196b94a08ad2aa9ccec6ec9bdba536 0 55 743 262 2019-08-28T15:19:10Z Bert 8 wikitext text/x-wiki ==Google's recaptcha== ===What is recaptcha and how/will it help prevent spam ?=== For answers to those questions you can look at google's page about recaptcha(https://google.com/recaptcha) ===Installation=== This installation guide requires Wordpress '''3.8''' or higher * Go to the Wordpress recaptcha plugin site (https://wordpress.org/plugins/google-captcha/) and download the latest version on our site in to the Wordpress installation folder * Extract the contents of the archive in to '''./wp-content/plugins/ ''' * Navigate to the Wordpress admin dashbord and select the plugin link (on the left side of the dashboard) * Activate the google recaptcha plugin * This will give you a link to the configuration page of the plugin or you can select the settings link located below the plugin * Follow the instructions on the page and depending on your configuration recaptcha will start ===Video instructions=== The makers of the Wordpress recaptcha have a video tutorial. This will supplement the above instructions, particularly the last step. (https://youtu.be/RUJ9VwZLFSY) [[Category:Security & anti-spam]] 3511ec74d965f24685af36172b9f95d6cd9aac8b 0 104 745 709 2019-08-28T15:19:29Z Bert 8 wikitext text/x-wiki PHP code is run with PHP-FPM as your ULYSSIS user. This means you can tighten up you website's security by denying other users the permission to read your PHP files. However, due to the way the Apache webserver works, it must be able to determine the existence of your PHP files. Non-PHP files in your www directory must remain readable by other users, because Apache reads these as it's own user. === Recommended permissions === * Homedirectory: See [[#Homedirectory permissions | homedirectory]] * www directory (and other directories from where websites are served), including subdirectories: <code>0705/drwx---r-x</code> * Website files (css, images, html, ...): <code>0604/-rw----r--</code> * Configuration files containing secrets/passwords: <code>0600/-rw-------</code> * Other directories and files that are not part of a website: <code>0600/-rw-------</code> or <code>0700/-rwx------</code> === Securing database login info === Suppose you have a file called <code>config.php</code>, containing login information for your database. To secure this information, you can make it readable and writeable by only you, and nobody else using <code>chmod 600 config.php</code>. In FileZilla, you can do this by right-clicking on the config file, clicking on "File permissions...", and changing the permissions according to the following screenshots: [[File:config-php_dropdown.png]] [[File:config-php_attrs.png]] === Securing uploads directory === Also, if there are directories that you made writeable by others, e.g. an uploads folder, this is no longer necessary. If this directory is called <code>uploads</code>, you can remove write rights for others with <code>chmod go-w uploads</code>. In FileZilla, you can do this by right-clicking on the config file, clicking on "File permissions...", and changing the permissions according to the following screenshots: [[File:uploads_dropdown.png]] [[File:uploads_attrs.png]] === Homedirectory permissions === In order to prevent other users entirely from accessing files in your homedirectory, the permissions on your homedirectory should only allow yourself and the www-data user access. This is by default configured properly for you from the 29th of July, 2018 onward. Note that you should still follow the guidelines as detailed above. If you have changed your permissions on your homedirectory and want to restore the defaults, you can execute <code>nfs4_setfacl -S /home/user/acl ~</code>. The file <code>/home/user/acl</code> contains the default permissions. [[Category:Files]] [[Category:Security & anti-spam]] 97697d586b016e10578bdcb98adf14e2e12dff6e 0 12 746 652 2019-08-28T15:20:04Z Bert 8 wikitext text/x-wiki = Creating a database = You can create one or more PostgreSQL databases in [https://ucc.ulyssis.org UCC]. The first database you create will have the same name as your username. Subsequent databases will be prefixed with "''username''_". = Managing your database = * The easiest way to manage your database is using [https://phppgadmin.ulyssis.org phpPgAdmin]. * You can also access it via the [[Accessing shell servers over SSH|command line]] with: psql -h pgsql.ulyssis.org = Connecting to the database = You can connect to the database with the following details: * Host: <code>pgsql.ulyssis.org</code> * Login: your ULYSSIS username * Password: the PostgreSQL password you chose in UCC * Database: the database you created in UCC Note that some CMSs will assume that you use "localhost" as the host, and will hide the host option under advanced settings in the installation process. If you can't find anywhere to enter the hostname, look under advanced settings. == Connection string == If you are programming your application yourself, PostgreSQL often uses the following connection format: host=$host user=$username password=$password db=$dbname Where you replace the parts starting with <code>$</code> with the above connection details. == pg_connect == If you are using PHP's [http://www.php.net/manual/en/function.pg-connect.php pg_connect] to connect to the database, and your username is "foo", your password is "password" and your database name is "foo": <syntaxhighlight lang="php"> $connection = pg_connect("host=pgsql.ulyssis.org user=foo password=password db=foo"); </syntaxhighlight> == PDO == If you want to connect using [http://be2.php.net/manual/en/intro.pdo.php PDO], your username is "foo", your password is "password" and your database is "foo": <syntaxhighlight lang="php"> $pdo = new PDO('pgsql:host=pgsql.ulyssis.org;dbname=foo', 'foo', 'password'); </syntaxhighlight> =Accessing PostgreSQL from outside of our network= To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH-tunnel. On Linux, Mac OSX and other Unix-like Operating Systems it is easily possible to use the following command to create a tunnel to a local port (in this case 5400): ssh username@ssh2.ulyssis.org -L 5400:pgsql.ulyssis.org:5432 -N You can use "ssh -f username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N": the f-argument will put the command in the background. = PostGIS = If necessary for an application or website you wish to use on ULYSSIS, we can always enable PostGIS for the specific database you wish to use it on. Contact us at ulyssis@ulyssis.org and let us know you would like to get PostGIS enabled and on which specific database. [[Category:Databases]] 4d933076246e13320d25d260ac02dfc295fd8661 0 6 747 653 2019-08-28T15:20:08Z Bert 8 wikitext text/x-wiki ==Creating a MySQL user== To use MySQL on your ULYSSIS account you first need to create a MySQL user on [https://ucc.ulyssis.org UCC]. In the MySQL section of the panel you will be suggested to click a link to create a user. Then fill in a password for the database user. It is highly recommended that this password differs from the password you use for your account. Then you just click ''Create user'' and you are ready to go. ==Creating a MySQL database== After creating a MySQL user, you can simple press ''Add database'' in [https://ucc.ulyssis.org UCC] and enter the name for your new database. It will automatically be prefixed by your username. ==Using MySQL for your website or application== Host: mysql.ulyssis.org Username: your account's username Password: the password you chose when you made the MySQL user Database: the database name you chose, prefixed by your username For example, if my username is foobar, I made a database called website and I were to create a PHP website I would use something like: <syntaxhighlight lang="php">$db = new mysqli('mysql.ulyssis.org', 'foobar', 'correct horse battery staple', 'foobar_website');</syntaxhighlight> or <syntaxhighlight lang="php">$db = new PDO('mysql:host=mysql.ulyssis.org;dbname=foobar_website', 'foobar', 'correct horse battery staple');</syntaxhighlight> ==Managing MySQL with PHPMyAdmin== Using your username and password you can easily manage your MySQL databases, tables and records on https://phpmyadmin.ulyssis.org ==Accessing MySQL from outside of our network== To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH-tunnel. In many MySQL management tools this is already supported. === MySQL Workbench === While [https://www.mysql.com/products/workbench/ MySQL Workbench] might not fully support our MySQL database, all commonly used operations work perfectly. You can connect to our database using MySQL Workbench by creating a connection as follows ([username] should be replaced by your username, of course): [[File:MySQL_Workbench_SSH.png]] === Linux, Mac OSX === On Linux, Mac OSX and other Unix-like Operating Systems it is also easily possible to use the following command to create a tunnel to a local port (in this case 3300) ssh username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N While this command is running, you can connect to the MySQL server with host 'localhost' and port '3300'. To terminate the port forwarding, press ctrl-C in the terminal. You can use "ssh -f username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N": the f-argument will put the command in the background. [[Category:Databases]] c6d836503e615a8bf9fdeb82168e9e5e0647fa6c 0 40 748 186 2019-08-28T15:20:11Z Bert 8 wikitext text/x-wiki You can access your MySQL databases using PHPMyAdmin. This application can be found on https://phpmyadmin.ulyssis.org. To login you need to use your MySQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your MySQL password you can get it from your websites configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. == Basic Usage == On the left you will see your username, you can click the plus sign to reveal all your databases. You can then view databases and tables. For each table you can view the records, view and change the structure, add records, take backups, etc. == Taking Backups == To take a backup of all your databases you simple select "Export" on the main menu and press start. You can later restore backups by uploading the file to the "Import" page. [[Category:Databases]] af6aff10230826414ed69edd620b9fbd60d77754 14 121 749 2019-08-28T15:20:17Z Bert 8 Created blank page wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 103 750 672 2019-08-28T15:22:21Z Bert 8 wikitext text/x-wiki While most webhosting providers give you access to a few or even just one programming language and a set amount of libraries, ULYSSIS prefers to offer more flexibility. We hope to give our users the chance to experiment with different languages, libraries and tools. There are of course also limits to what is realistic for us to install. More on that below. == Using a programming language, library or tool that is not installed == If the package that you would like us to install is available in the software repository of our current operating system, then that is usually not a problem. We currently use Ubuntu on all our servers, specifically, we upgrade to the latest LTS every summer vacation following the release of a new one. You can verify which version we are running by executing "cat /etc/lsb-release" on one of our shellservers. After you have verified what version we are running, you can refer to https://packages.ubuntu.com/ to check whether your package is available in that version of Ubuntu. If it is, then you can contact us by email on ulyssis@ulyssis.org which package or packages you would like to have installed, and what you will be using it for. You will most likely get a positive response. If your package is not in the repository, you will have to go for a [[Installing packages#Manual installation|Manual installation]]. == Using a newer/different version == As you can read in the section concerning the installation of new packages, we only offer the version available in the repository of the version of Ubuntu that we are running. In most cases, this means you will have to wait for a version upgrade with the next LTS release, or go for a [[Installing packages#Manual installation|Manual installation]]. However, there are some exceptions. Sometimes multiple version will be available in the repository, such as with Python 2 and 3, or Perl 5 and 6. In such cases, you can refer to the section above for instructions on how to request an installation. == Manual installation == If you want to install a piece of software that is not available in the repository or you wish to install another version, you can always install it manually onto your account. It is important to keep in mind that ULYSSIS will not support manually installed software, and that you are fully responsible for the security of this software. You are free to ask us questions, but we will most probably not help you. If you do require a manual installation of specific software, we expect you to be capable of maintaining it as well. The way you install your software differs depending on the software. You could be using tools such as pip, gem or npm to install to a directory in your home folder, you could be using a virtual environment, or you could be compiling your own binary. We suggest you look at the documentation of the software you're using very thoroughly, and make sure you are comfortable with what you are doing and aware of your responsibilities. After installing your software locally onto your account, you will probably want to add an alias in your dotfiles (for example .profile or .bashrc) to make using your manually installed version easier. In case you are using your piece of software for a web service, you will want to make sure you edit your fastcgi script or any other involved scripts to use your binary by changing the path or hardcoding the location. == Node.js == We do not offer Node.js by default because we can't give you the most recent release. But you can use nvm ([https://github.com/creationix/nvm Node Version Manager]) which installs the required version for you. The installation should be straightforward and a guide can be found [https://github.com/creationix/nvm#installation here]. [[Category:Shell]] 2d46bb52dc6f8fc367b9ad73eb3e62cf5cde3e1d 14 122 751 2019-08-28T15:22:32Z Bert 8 Created blank page wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 87 753 445 2019-08-28T15:22:49Z Bert 8 wikitext text/x-wiki Cron is a job scheduler, a utility that can be used to execute shell commands at specific points in time. These jobs are also called Cron jobs, and can be edited using the crontab command. ==The Crontab Command== To edit the cron table (crontab) file, you will use the crontab command. The crontab command has a few options: * <code>crontab -e</code>: Edit the crontab for the current user * <code>crontab -l</code>: List the cron jobs for the current user * <code>crontab -r</code>: Remove all cron jobs for the current user (Use the -i option to prompt before deleting) =Editing The Crontab= Perform these steps to edit the crontab. * Execute the <code>crontab -e</code> command * If this is the first time editing the crontab, a prompt will appear asking you to specify your text editor. If you don't know what to reply, we suggest you choose <code>nano</code>. * If everything is performed correctly, a file should appear. * You can edit this file. (Remember that everything after # is a comment) To add a new line to the file, you should follow this format: ┌───────────── minute (0 - 59) │ ┌───────────── hour (0 - 23) │ │ ┌───────────── day of month (1 - 31) │ │ │ ┌───────────── month (1 - 12) │ │ │ │ ┌───────────── day of week (0 - 6) (Sunday to Saturday; │ │ │ │ │ 7 is also Sunday) │ │ │ │ │ │ │ │ │ │ * * * * * command to execute You can use an asterisk (*) if a field does not matter. For example: <code>0 * * * * python somescript.py</code> will run <code>python somescript.py</code> every hour. <code>1 0 15 * 0 somecommand</code> will run <code>somecommand</code> every month the 15th day '''or''' if the day is a Sunday, at 1 past midnight (00:01). ==Real-life Example: Scheduling Drush Updates== Drush and Cron can be used to update Drupal automatically. * First, run the <code>crontab -e</code> command. More info can be found in the previous section. * Next, add the following line to the file: <code>0 0 * * * cd /path/to/your/drupal/folder/ && drush pm-update</code> This will execute the <code>cd /path/to/your/drupal/folder/</code> command, changing the current directory to your drupal folder, and the <code>drush pm-update</code> command, updating Drupal, every day, at midnight. The <code>&&</code> indicates a new command follows. * Finally, save and exit the file and you're good to go! [[Category:Shell]] b23f1d64cde3237b5786a399bd14765f78ac552d 0 16 754 86 2019-08-28T15:22:55Z Bert 8 wikitext text/x-wiki Once you've connected, you can use these commands to use the ULYSSIS shell. First of all, whenever you need to type a longer command or filename, try the <code>TAB</code> key as it will try to complete the name of the command or file you are typing. Pressing <code>TAB</code> twice will show a list of possible completions. A more extensive document on this can be found at http://info.ee.surrey.ac.uk/Teaching/Unix/. ==Basic file managment== <code>cd directoryname</code> Change directory. Works the same as under MS-DOS. cd without argument changes to your home directory (like My Documents in windows). Go to the parent directory with <code>cd ..</code> <code>ls</code> List the contents of the current directory. Many different formats are available, a common one is <code>ls -al</code>. To accomodate MS-DOS/Windows users, <code>dir</code> is an alias (synonym) for <code>ls -alF</code>, which gives output similar to the <code>dir</code> command in MS-DOS/Windows. <code>cp inputfile targetfile</code> Copy inputfile to targetfile. Additional arguments (e.g. -r or -v are explained in the man-page.) <code>mv inputfile targetfile</code> Move inputfile to targetfile. Additional arguments (e.g. -i or -v are explained in the man-page.) This is the way to rename a file. Note that you cannot use a construction like mv *.htm *.html to add an ``l'' to a bunch of files. A small shell script can provide a way to do this: <code>for i in *.htm; do mv i; done</code> <code>rm filename</code> Remove filename. Additional arguments (e.g. -r or -v are explained in the man-page.) Note: there is no undelete-alike function in most unices. <code>mkdir dirname</code> Creates a directory called dirname. <code>rmdir dirname</code> Removes an empty directory. Use rm -r to delete a directory and recursively everything in it. Add -f to disable any prompts (dangerous!). ==Getting help== <code>man command-name</code> Displays manual pages, if available. E.g. man ls. Use 'q' to exit. Relatives: apropos, help. <code>apropos word</code> Searches through headers of all man pages. <code>help command-name</code> Displays help about command-name. Only for internal bash-functions. <code>bash</code> The Bourne Again SHell. Widely used successor of sh, the Bourne shell. This is the program you're working under after you open a ssh-session (you don't have to start it to use it). Bash interprets your commands, and executes them. Tab-completion, * and ? expansions, etc are all bash functions. man bash will give you tons of info about it. Alternatives : tcsh, zsh, rc ==Text editors== It's easier to use a text editor on a server, than editing your file locally and uploading that file. <code>pico</code> or <code>nano</code> Probably the easiest text editor. Should be self-explanatory. <code>joe</code> Another easy text editor. Press Ctrl+C to quit. <code>vim</code> Probably the best text editor. Start editing by pressing <code>i</code>. Stop editing by pressing the <code>escape</code> key. Save and quit with <code>:wq</code>. Quit without saving with <code>:q!</code>. ==Utilities== <code>df</code> Displays info about the free diskspace on the system. df . will give info about the filesystem where the current directory resides. The output becomes a bit more readable with the -h switch. <code>du</code> Displays info about the diskusage in the current directory (and its subdirectories. A common parameter is -s , equivalent to -summarize , to summarize the disk-usage (without the per-subdir totals). <code>quota</code> Displays info about your diskusage, and your disk quota. Quota are limits on diskusage, imposed by the system administrator. The system will warn you if you exceed these limits. <code>ps</code> Displays info about processes. Various options possible, for example ps auxf gives info on all processes, including process owner, memory usage, and parent-child indication. <code>htop</code> Displays top CPU processes. Use it to see what gets most cpu power at the moment. Don't leave top open for a long time, since it eats cpu time itself. (quit with 'q'). [[Category:Shell]] 4145511b41c397f6d2c76518dda5bec7c75fac97 0 7 755 659 2019-08-28T15:23:02Z Bert 8 wikitext text/x-wiki ULYSSIS hosts its own IRC network. IRC stands for Internet Relay Chat, [https://en.wikipedia.org/wiki/Internet_Relay_Chat IRC on wikipedia]. It is a chat protocol that mainly focuses on group chat, but also allows for private chat. If you have an urgent question, IRC is often the quickest way to contact us. But also if you don't have a question and just want to hang out in our chat, feel free to join! ==Web IRC client== If you won't regularly use our IRC or if you just want to check it out, you can use our web IRC client. You can find it at [https://webirc.ulyssis.org/ webirc.ulyssis.org]. ==IRC network details== Below are specific instructions for some clients, but if you are already familiar with IRC, here are the details you need to connect to our server. We highly recommend using SSL. Server: irc.ulyssis.org Port: 6668 (SSL) Channel: #ulyssis If <code>irc.ulyssis.org</code> is down, you can also try the other server in the same network, hosted at <code>irc2.ulyssis.org</code>. Both are connected to each other and you can use them interchangeably. It is advised to add it as a fallback in your IRC client. ==IRC clients== To use IRC, you'll need an IRC client. We advise the terminal based [https://irssi.org/ irssi] or [https://weechat.org/ weechat] for Linux and [https://hexchat.github.io/ hexchat] or [https://www.mirc.com/ mIRC] for Windows, but there are a lot of other free options. You can only receive messages over IRC while you're connected. Therefore, we advise you to run irssi or weechat in either a screen or a tmux session. With a ULYSSIS account, you can run screen or tmux on our shellservers, as they keep running 24/7 you can use them to keep track of your conversations. Screen and tmux are similar programs. Screen has been around for longer and is more tested, while tmux is more modern with new features and being easier to use for beginners. ===Using irssi on our shell servers=== ====Connect to the shellserver==== Use the ssh command in your Linux or OS X terminal, or use PuTTY to connect on windows. Extensive information on how to do so can be found on [[Accessing shell servers over SSH]]. ====Start irssi in a screen==== *When on the shellserver, enter <code>screen -U</code> to start a screen session, or <code>tmux</code> to start a tmux session. *Enter <code>irssi</code> to start irssi *Connect to the IRC server: <code>/server -ssl irc.ulyssis.org 6668</code> *Connect to the public channel: <code>/join #ulyssis</code> ====Screen usage==== *To exit the screen: press Ctrl-A and press D ('detach') to return to the shellserver. *To reconnect: enter <code>screen -r</code> or <code>screen -DR</code> (the latter will create a new screen if it wasn't already made). ====Tmux usage==== *To exit the tmux session: press Ctrl-B and press D ('detach') to return to the shellserver. *To reconnect: enter <code>tmux attach</code> ====Help, I can't reconnect to my session!==== *Check if you are on the right shell server and didn't make a typing error. *If everything is correct, your screen may have been stopped by a crash or a reboot of our shellserver. You can check the [http://www.ulyssis.org/status status] section of our website for more information about possible downtimes. *Make sure you use the right program (<code>screen</code> if you started a screen session and <code>tmux</code> if you started a tmux session) ==Using ZNC== Alternatively, if you don't like using terminal-based clients, or just want to run your client locally, you can connect with our [https://znc.ulyssis.org/ ZNC server]. However, to use it, you'll need a ULYSSIS account. ZNC connects to our IRC server in your place (fill in the details at the beginning of this article). You can then connect to ZNC with a client of your choice, and it will send you the history you've missed while you were offline. Log in to our ZNC server. In your settings, create a new network. Fill in the basic details (server name, nickname, set <code>BindHost</code> to <code>0.0.0.0</code>). In the server field, fill in <code>irc.ulyssis.org +6668</code>. Add <code>#ulyssis</code> as a channel. You may want to increase the buffer count. Then save at the bottom of the page. In your IRC client, connect to the server <code>znc.ulyssis.org</code> on port 6666 (with SSL) and set <code>username/network:password</code> as password to the server. Replace <code>username</code> with your ULYSSIS username, <code>network</code> with the name of the network in your znc settings, and <code>password</code> with your ULYSSIS password. [[Category:Shell]] 2f575d6a195d467d249826e52e5b072e55b8a2f8 762 755 2019-08-28T15:24:40Z Bert 8 wikitext text/x-wiki ULYSSIS hosts its own IRC network. IRC stands for Internet Relay Chat, [https://en.wikipedia.org/wiki/Internet_Relay_Chat IRC on wikipedia]. It is a chat protocol that mainly focuses on group chat, but also allows for private chat. If you have an urgent question, IRC is often the quickest way to contact us. But also if you don't have a question and just want to hang out in our chat, feel free to join! ==Web IRC client== If you won't regularly use our IRC or if you just want to check it out, you can use our web IRC client. You can find it at [https://webirc.ulyssis.org/ webirc.ulyssis.org]. ==IRC network details== Below are specific instructions for some clients, but if you are already familiar with IRC, here are the details you need to connect to our server. We highly recommend using SSL. Server: irc.ulyssis.org Port: 6668 (SSL) Channel: #ulyssis If <code>irc.ulyssis.org</code> is down, you can also try the other server in the same network, hosted at <code>irc2.ulyssis.org</code>. Both are connected to each other and you can use them interchangeably. It is advised to add it as a fallback in your IRC client. ==IRC clients== To use IRC, you'll need an IRC client. We advise the terminal based [https://irssi.org/ irssi] or [https://weechat.org/ weechat] for Linux and [https://hexchat.github.io/ hexchat] or [https://www.mirc.com/ mIRC] for Windows, but there are a lot of other free options. You can only receive messages over IRC while you're connected. Therefore, we advise you to run irssi or weechat in either a screen or a tmux session. With a ULYSSIS account, you can run screen or tmux on our shellservers, as they keep running 24/7 you can use them to keep track of your conversations. Screen and tmux are similar programs. Screen has been around for longer and is more tested, while tmux is more modern with new features and being easier to use for beginners. ===Using irssi on our shell servers=== ====Connect to the shellserver==== Use the ssh command in your Linux or OS X terminal, or use PuTTY to connect on windows. Extensive information on how to do so can be found on [[Accessing shell servers over SSH]]. ====Start irssi in a screen==== *When on the shellserver, enter <code>screen -U</code> to start a screen session, or <code>tmux</code> to start a tmux session. *Enter <code>irssi</code> to start irssi *Connect to the IRC server: <code>/server -ssl irc.ulyssis.org 6668</code> *Connect to the public channel: <code>/join #ulyssis</code> ====Screen usage==== *To exit the screen: press Ctrl-A and press D ('detach') to return to the shellserver. *To reconnect: enter <code>screen -r</code> or <code>screen -DR</code> (the latter will create a new screen if it wasn't already made). ====Tmux usage==== *To exit the tmux session: press Ctrl-B and press D ('detach') to return to the shellserver. *To reconnect: enter <code>tmux attach</code> ====Help, I can't reconnect to my session!==== *Check if you are on the right shell server and didn't make a typing error. *If everything is correct, your screen may have been stopped by a crash or a reboot of our shellserver. You can check the [http://www.ulyssis.org/status status] section of our website for more information about possible downtimes. *Make sure you use the right program (<code>screen</code> if you started a screen session and <code>tmux</code> if you started a tmux session) ==Using ZNC== Alternatively, if you don't like using terminal-based clients, or just want to run your client locally, you can connect with our [https://znc.ulyssis.org/ ZNC server]. However, to use it, you'll need a ULYSSIS account. ZNC connects to our IRC server in your place (fill in the details at the beginning of this article). You can then connect to ZNC with a client of your choice, and it will send you the history you've missed while you were offline. Log in to our ZNC server. In your settings, create a new network. Fill in the basic details (server name, nickname, set <code>BindHost</code> to <code>0.0.0.0</code>). In the server field, fill in <code>irc.ulyssis.org +6668</code>. Add <code>#ulyssis</code> as a channel. You may want to increase the buffer count. Then save at the bottom of the page. In your IRC client, connect to the server <code>znc.ulyssis.org</code> on port 6666 (with SSL) and set <code>username/network:password</code> as password to the server. Replace <code>username</code> with your ULYSSIS username, <code>network</code> with the name of the network in your znc settings, and <code>password</code> with your ULYSSIS password. [[Category:Shell]] [[Category:ULYSSIS Public Services]] a552148fb9e7b6072310486e26b7b36ffd68ba3b 0 4 756 39 2019-08-28T15:23:08Z Bert 8 wikitext text/x-wiki Users can access the ULYSSIS servers through two machines: <code>ssh1.ulyssis.org</code> and <code>ssh2.ulyssis.org</code>. Both of them run Linux. You can run commands on these servers or use them to access the files on your ULYSSIS account. The servers can only be accessed trough SSH, not through FTP or any other protocol. =Running commands= To run a command on the shell servers, you will need to connect to them using a terminal. Our servers do not support a full graphical interface. ==Linux== On Linux, you can just open a terminal and connect to the servers by using one of the following commands (with <code>username</code> your username): <code>ssh username@ssh1.ulyssis.org</code><br /> <code>ssh username@ssh2.ulyssis.org</code> Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. ==Windows== Windows doesn't support native terminals, so you will have to download a program first. A good option is [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty], which is completely free and doesn't require any installation. Just download it and run the .exe file. The parameters: *Host name: ssh1.ulyssis.org or ssh2.ulyssis.org *Protocol: SSH *Port: 22 (should be set automatically) You can save these options for later on. Next, you will be asked to give your password. Doing all this will open a terminal to the remote server which can be used the same way as a Linux terminal. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. More information about Putty can be found at http://the.earth.li/~sgtatham/putty/0.60/htmldoc/. ==Mac== On Mac, you can just open Terminal. This application can be found in the Utilities folder within your Application folder. If you don't find it there, you can use Spotlight to find it. You can now connect to the servers by using one of the following commands (with <code>username</code> your username): <code>ssh username@ssh1.ulyssis.org</code><br /> <code>ssh username@ssh2.ulyssis.org</code> Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use ctrl+D. ==Useful ideas== Here are some useful ideas about what you could do with your shell server access: *[[Accessing your files]] *[[Fetch your KU Leuven email into another email address]] *[[ULYSSIS public IRC]] ==Useful commands== Some useful commands can be found [[Useful Linux Commands|here]]. [[Category:Shell]] 94e4529bb019944cc13a4b0b3989274dfb2a0586 0 36 757 706 2019-08-28T15:23:16Z Bert 8 wikitext text/x-wiki ULYSSIS doesn't support ftp, because it is insecure. However, we support sftp (ftp over ssh). This works similar as ssh. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Non-graphical methods== The most common way to transfer files is with a terminal by using the <code>scp</code> command.<br/> Copying file to host:<br> <code>scp SourceFile user@host:directory/TargetFile</code><br> Copying file from host:<br> <code>scp user@host:directory/SourceFile TargetFile scp -r user@host:directory/SourceFolder TargetFolder</code> You don't need to use the full path to your file. You may you the relative path, starting from your home directory. For example:<br> <code>scp index.html user@ssh1.ulyssis.org:www/index.html</code> ==Graphical methods== The graphical methods are explained in [[Accessing your files]]. [[Category:Files]] [[Category:Shell]] 3b258d0050b5c55d62d0d7bfb8b3cedc30f2b1d4 0 5 758 705 2019-08-28T15:23:24Z Bert 8 wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Connecting== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. If your distribution does not contain an option to connect to a server, you can use [https://filezilla-project.org/ FileZilla], which is completely free. See the instructions under [[Accessing_your_files#Windows|Windows]]. [[File:UbuntuConnectToServer.png]] ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ===Mac=== ''[https://filezilla-project.org/ FileZilla], which was mentioned above, is also available for Mac. To use it, follow [[#Windows|the instructions for Windows]]. You can also opt for [http://cyberduck.io/ Cyberduck], though. In that case, follow the instructions below.'' Download the free and open source program [http://cyberduck.io/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> [[File:maccyberduck3.png]] Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. If you want to connect again later on, you can just click the Bookmarks icon on the top left. Next you click on History. And then you can double click to re-open the connection. ==Using FileZilla== When you connect to a server using FileZilla, the following layout will appear: [[File:Base_layout.png|700px|Right]] As you can see, the local files are located on the left-hand side, while the remote (server) files are located on the right-hand side. File navigation and paths are also present. [[File:Layout.png|700px|Right]] To transfer a file or folder, you can drag and drop it, either from the local side to the remote side, or from the remote side to the local side. These operations represent uploading and downloading respectively. [[File:Transfer.png|700px|Right]] You can also press enter while selecting a file, or double-click a file, to transfer it. [[File:Transfer2.png|700px|Right]] To open a folder, you can double-click it, or press enter while selecting it. [[File:Open.png|700px|Right]] You can delete files or folders by pressing the delete button while selecting them, or by right-clicking and clicking 'delete'. [[File:Delete.png|700px|Right]] To create files or folders remotely, you can right-click the remote window and click 'create directory' or 'create new file'. [[File:Create_directory.png|700px|Right]] [[File:Create_file.png|700px|Right]] As you can see, the menu has some more interesting options, for example 'rename' or 'view/edit'. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): <code>scp file.txt username@ssh1.ulyssis.org:/home/user/username </code> For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. [[Category:Files]] [[Category:Shell]] 9e52327489362441837b0ffb4927de5929f5968e 0 13 759 490 2019-08-28T15:23:55Z Bert 8 wikitext text/x-wiki If you want to use [http://git-scm.com/ git] for version control to work privately on personal projects, or collaborate with others on projects, you can use GitLab for central repositories, and for tracking bugs. = Accessing GitLab = You can access our GitLab server at https://gitlab.ulyssis.org. You can log in with your standard ULYSSIS username and password. = Getting started with Git = If you want to get acquainted with git, these are good free resources: * [https://try.github.io Try Git]: an interactive introduction to git * [http://git-scm.com/book Pro Git]: a book that you can read for free online * [http://git-scm.com/docs The official Git reference documentation] = Guest users = Sadly, we do not provide automated guest user support for GitLab yet, as we do for Subversion. If not everyone who works on your project has their own ULYSSIS account, you can request a Gitlab guest account via email. You simply send an email with the guest account's username (which will be prefixed with an underscore), full name, KU Leuven uid (m/s/r/u number) and email address to ulyssis@ulyssis.org and we will create it. Do keep in mind you bear full responsibility for all guests created for your account. [[Category:Versioning]] da6a779d9cf2f0d58d058e111ee828ec9f67a3be 14 123 760 2019-08-28T15:24:02Z Bert 8 Created blank page wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 14 124 764 2019-08-28T15:24:53Z Bert 8 Created blank page wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 73 765 516 2019-08-28T15:25:16Z Bert 8 wikitext text/x-wiki We often get the question at our LaTeX workshop how to properly install the kulemt package. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading "kulemt-tds.zip" from ftp://ftp.esat.kuleuven.be/latex/kulemt/. == One-time use == Most people will only use this package once, for their master thesis. In this case, you can just put the necessary files in the same folder as your LaTeX project. The easiest way to accomplish this, is to unzip the downloaded file and in the unzipped folder, navigate to the directory "tex/latex/kulemt". Here, copy the following files to the same directory as your LaTeX project: kulemt.cfg, kulemt.cls, kulemtx.sty, logokul.eps and logokuleng.eps. == User-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package in a central location where LaTeX can find it autonomously. When using TeXLive, as we recommend, this involves a bit more work. First, you should find where to install the packages for your user. This is called the TEXMFHOME. The default location of this folder is: * For Windows: the folder "texmf" in your %USERPROFILE% (C:\Users\YourUsername for Windows Vista and up). * For Linux: "~/texmf" * For OS X/macOS: "~/Library/texmf" It is possible that this folder needs to be created first. From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location (note: the directory itself, not only its contents). If this does not work, or if you want to check the directory first, please refer to the section [[#Finding the TEXMFHOME]] at the bottom of this document. For a more technical overview, you can follow the general guidelines provided by the department: ftp://ftp.esat.kuleuven.be/latex/kulemt/README.html. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English}, % in case of a Dutch master udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> == Finding the TEXMFHOME == In case the default location for the TEXMFHOME as stated above does not work, you can find the correct directory through command-line. In Linux and macOS, look for an app called "Terminal". In Windows, search for "cmd" using the start menu. The program has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf If you have found this folder, copy the entire "tex" directory from the extracted kulemt-tds.zip to this location, as stated before. Create the folder if needed. == Troubleshooting == The kulemt package requires the memoir package. Make sure you have this package. We recommend installing the texlive-full package on Ubuntu. When you use the installer from [ftp://ftp.ulyssis.org/LaTeX-Workshop/installers/ our FTP server] for Windows or OS X/macOS, you will automatically have the entire LaTeX suite. [[Category:Tutorials]] 2354bd22fab6bfc011913f69aa9ad6704af2562b 0 78 766 513 2019-08-28T15:25:23Z Bert 8 wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. # Set up agenda sync on KU Loket ## Visit [http://kuloket.be/ KU Loket] ## Go to the '''Education & Students''' (Onderwijs & studenten) tab [[File:KULoket-Agenda-Step1.png|thumb|200px]] ## Click '''Agenda sync''' ## Click '''Configure agenda''' (Agenda instellen) [[File:KULoket-Agenda-Step2.png|thumb|200px]] ## Change the switch '''Show schedule in my agenda''' (Toon uurrooster in mijn agenda) to '''On'''. [[File:KULoket-Agenda-Step3.png|thumb|200px]] You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (Agenda) # On the top right (below the menu bar), click the '''Share''' (Delen) button. A side-panel appears. # Enter a non-KU Leuven email address in the '''Share with''' (Delen met) textfield. After filling the email address, press the enter key. # Make sure '''Full details''' (Volledige informatie) is selected in the dropdown next to your email address # Click the '''Send''' (Verzenden) button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> [[Category:Tutorials]] 69a3c408ea009789002952a298622ff35fc8cbff 14 125 767 2019-08-28T15:25:31Z Bert 8 Created blank page wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 47 768 732 2019-08-28T19:11:48Z Bert 8 wikitext text/x-wiki This page will go through a basic setup of MediaWiki. It is based on [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wikipage], and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. This tutorial we'll use a ULYSSIS-account with username "me". == Putting setup-files in place == First we'll have to download the setup file which you can find over at [http://www.mediawiki.org/wiki/Download the official MediaWiki website]. It's an archived file, so you need to extract it first and put the files in a subdirectory of your "document root". The default is just a www directory in your home folder. Putting your files in document_root/wiki/ will make your wiki be located at usersname.ulyssis.be/wiki/. If you prefer, you can do this all graphically using the manual [[Accessing_your_files]]. If you prefer the command line; <pre> homeuser@home:~$ ssh me@ssh1.ulyssis.org enter super secret password: me@zap:~$ wget http://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.6.tar.gz me@zap:~$ tar xvxf mediawiki-1.23.6.tar.gz me@zap:~$ mv mediawiki-1.23.6 www/wiki me@zap:~$ rm -r mediawiki-1.23.6.tar.gz </pre> =Setting up database= Like the [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wiki] tells us, we have three different options to choose from; PostgreSQL, MySQL and SQLite. It's easy to set a PostgreSQL or MySQL database; just go to the UCC. For this tutorial we will continue with a MySQL database (PostgreSQL installation steps are quite similar). Let us visit https://ucc.ulyssis.org/mysql; if this is your first time using MySQL you'll need to create a new account by putting in a super secret password. The wizard will create your MySQL account with the same name as your user-account. We'll also create a new database with an appropriate name by clicking on 'Add database'. In this tutorial we will choose; "wiki", notice that it will be prepended with our username, so we'll end up with a new database named "me_wiki". =Setup your wiki= If all went well, you can access your website at http://username.ulyssis.be/the_folder_you_used and start the setup wizard. In our example, will surf to http://me.ulyssis.be/wiki. The wizard will guide you through some configuration options. Most of them our pretty straight-forward. When in doubt, you can always click the question mark wich will show you some sensible and recommended default... We'll just discuss the page were the wizard asks you for the database. In our example; <pre> Database host: mysql.ulyssis.org Database name: me_wiki // The name of our database; i.e. the name we chose, prepended by our username. Database table prefix: // We can leave this blank. Database user: me // This is the name of our MySQL-user, which was named after our ULLYSIS-username. Database password: supersecretpassword // Please note that this is not your ULLYSIS-password, but the password you used in UCC when creating the MySQL user! </pre> =Creating the wiki= After the setup wizard is complete, you can begin the installation procedure. If all went well, you'll be greeted by a page which congratulates you with your new installation. =Finalizing steps= The setup will offer you a configuration file (containing some settings you specified) that you need to download to your server (more specifically in directory where your MediaWiki-files reside in). You again can do this graphically, or if you prefer a terminal; <pre> homeuser@home:~$ scp path_to_file/LocalSettings.php me@ssh1.ulyssis.org:~/www/wiki enter super secret password: </pre> After this is done, you can finally start using your wiki. !!! Note that this is only a very basic case of a wiki install. Please refer to [http://www.mediawiki.org/wiki/MediaWiki the original MediaWiki wiki] for a more in depth source. !!! !!! Please know that managing a wiki comes with great responsibility, keep your wiki up to date and follow healthy and recommended security practices. !!! [[Category:CMSs]] 877d2a334cba72e0589992af664729e915dc4392 769 768 2019-08-28T19:12:04Z Bert 8 wikitext text/x-wiki This page will go through a basic setup of MediaWiki. It is based on [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wikipage], and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. This tutorial we'll use a ULYSSIS-account with username "me". == Putting setup-files in place == First we'll have to download the setup file which you can find over at [http://www.mediawiki.org/wiki/Download the official MediaWiki website]. It's an archived file, so you need to extract it first and put the files in a subdirectory of your "document root". The default is just a www directory in your home folder. Putting your files in document_root/wiki/ will make your wiki be located at usersname.ulyssis.be/wiki/. If you prefer, you can do this all graphically using the manual [[Accessing_your_files]]. If you prefer the command line; <pre> homeuser@home:~$ ssh me@ssh1.ulyssis.org enter super secret password: me@zap:~$ wget http://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.6.tar.gz me@zap:~$ tar xvxf mediawiki-1.23.6.tar.gz me@zap:~$ mv mediawiki-1.23.6 www/wiki me@zap:~$ rm -r mediawiki-1.23.6.tar.gz </pre> =Setting up database= Like the [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wiki] tells us, we have three different options to choose from; PostgreSQL, MySQL and SQLite. It's easy to set a PostgreSQL or MySQL database; just go to the UCC. For this tutorial we will continue with a MySQL database (PostgreSQL installation steps are quite similar). Let us visit https://ucc.ulyssis.org/mysql; if this is your first time using MySQL you'll need to create a new account by putting in a super secret password. The wizard will create your MySQL account with the same name as your user-account. We'll also create a new database with an appropriate name by clicking on 'Add database'. In this tutorial we will choose; "wiki", notice that it will be prepended with our username, so we'll end up with a new database named "me_wiki". ==Setup your wiki== If all went well, you can access your website at http://username.ulyssis.be/the_folder_you_used and start the setup wizard. In our example, will surf to http://me.ulyssis.be/wiki. The wizard will guide you through some configuration options. Most of them our pretty straight-forward. When in doubt, you can always click the question mark wich will show you some sensible and recommended default... We'll just discuss the page were the wizard asks you for the database. In our example; <pre> Database host: mysql.ulyssis.org Database name: me_wiki // The name of our database; i.e. the name we chose, prepended by our username. Database table prefix: // We can leave this blank. Database user: me // This is the name of our MySQL-user, which was named after our ULLYSIS-username. Database password: supersecretpassword // Please note that this is not your ULLYSIS-password, but the password you used in UCC when creating the MySQL user! </pre> ==Creating the wiki== After the setup wizard is complete, you can begin the installation procedure. If all went well, you'll be greeted by a page which congratulates you with your new installation. ==Finalizing steps== The setup will offer you a configuration file (containing some settings you specified) that you need to download to your server (more specifically in directory where your MediaWiki-files reside in). You again can do this graphically, or if you prefer a terminal; <pre> homeuser@home:~$ scp path_to_file/LocalSettings.php me@ssh1.ulyssis.org:~/www/wiki enter super secret password: </pre> After this is done, you can finally start using your wiki. !!! Note that this is only a very basic case of a wiki install. Please refer to [http://www.mediawiki.org/wiki/MediaWiki the original MediaWiki wiki] for a more in depth source. !!! !!! Please know that managing a wiki comes with great responsibility, keep your wiki up to date and follow healthy and recommended security practices. !!! [[Category:CMSs]] 372f4e25fac8a2b94cca628e0447d0a8e184f775 770 769 2019-08-28T19:12:46Z Bert 8 wikitext text/x-wiki This page will go through a basic setup of MediaWiki. It is based on [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wikipage], and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. This tutorial we'll use a ULYSSIS-account with username "me". == Putting setup-files in place == First we'll have to download the setup file which you can find over at [http://www.mediawiki.org/wiki/Download the official MediaWiki website]. It's an archived file, so you need to extract it first and put the files in a subdirectory of your "document root". The default is just a www directory in your home folder. Putting your files in document_root/wiki/ will make your wiki be located at usersname.ulyssis.be/wiki/. If you prefer, you can do this all graphically using the manual [[Accessing_your_files]]. If you prefer the command line; <pre> homeuser@home:~$ ssh me@ssh1.ulyssis.org enter super secret password: me@zap:~$ wget http://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.6.tar.gz me@zap:~$ tar xvxf mediawiki-1.23.6.tar.gz me@zap:~$ mv mediawiki-1.23.6 www/wiki me@zap:~$ rm -r mediawiki-1.23.6.tar.gz </pre> ==Setting up database== Like the [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wiki] tells us, we have three different options to choose from; PostgreSQL, MySQL and SQLite. It's easy to set a PostgreSQL or MySQL database; just go to the UCC. For this tutorial we will continue with a MySQL database (PostgreSQL installation steps are quite similar). Let us visit https://ucc.ulyssis.org/mysql; if this is your first time using MySQL you'll need to create a new account by putting in a super secret password. The wizard will create your MySQL account with the same name as your user-account. We'll also create a new database with an appropriate name by clicking on 'Add database'. In this tutorial we will choose; "wiki", notice that it will be prepended with our username, so we'll end up with a new database named "me_wiki". ==Setup your wiki== If all went well, you can access your website at http://username.ulyssis.be/the_folder_you_used and start the setup wizard. In our example, will surf to http://me.ulyssis.be/wiki. The wizard will guide you through some configuration options. Most of them our pretty straight-forward. When in doubt, you can always click the question mark wich will show you some sensible and recommended default... We'll just discuss the page were the wizard asks you for the database. In our example; <pre> Database host: mysql.ulyssis.org Database name: me_wiki // The name of our database; i.e. the name we chose, prepended by our username. Database table prefix: // We can leave this blank. Database user: me // This is the name of our MySQL-user, which was named after our ULLYSIS-username. Database password: supersecretpassword // Please note that this is not your ULLYSIS-password, but the password you used in UCC when creating the MySQL user! </pre> ==Creating the wiki== After the setup wizard is complete, you can begin the installation procedure. If all went well, you'll be greeted by a page which congratulates you with your new installation. ==Finalizing steps== The setup will offer you a configuration file (containing some settings you specified) that you need to download to your server (more specifically in directory where your MediaWiki-files reside in). You again can do this graphically, or if you prefer a terminal; <pre> homeuser@home:~$ scp path_to_file/LocalSettings.php me@ssh1.ulyssis.org:~/www/wiki enter super secret password: </pre> After this is done, you can finally start using your wiki. !!! Note that this is only a very basic case of a wiki install. Please refer to [http://www.mediawiki.org/wiki/MediaWiki the original MediaWiki wiki] for a more in depth source. !!! !!! Please know that managing a wiki comes with great responsibility, keep your wiki up to date and follow healthy and recommended security practices. !!! [[Category:CMSs]] 27ab65eb1c1605868080f76e0e22c9f6293e2254 771 770 2019-08-28T19:16:55Z Bert 8 /* Finalizing steps */ wikitext text/x-wiki This page will go through a basic setup of MediaWiki. It is based on [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wikipage], and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. This tutorial we'll use a ULYSSIS-account with username "me". == Putting setup-files in place == First we'll have to download the setup file which you can find over at [http://www.mediawiki.org/wiki/Download the official MediaWiki website]. It's an archived file, so you need to extract it first and put the files in a subdirectory of your "document root". The default is just a www directory in your home folder. Putting your files in document_root/wiki/ will make your wiki be located at usersname.ulyssis.be/wiki/. If you prefer, you can do this all graphically using the manual [[Accessing_your_files]]. If you prefer the command line; <pre> homeuser@home:~$ ssh me@ssh1.ulyssis.org enter super secret password: me@zap:~$ wget http://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.6.tar.gz me@zap:~$ tar xvxf mediawiki-1.23.6.tar.gz me@zap:~$ mv mediawiki-1.23.6 www/wiki me@zap:~$ rm -r mediawiki-1.23.6.tar.gz </pre> ==Setting up database== Like the [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wiki] tells us, we have three different options to choose from; PostgreSQL, MySQL and SQLite. It's easy to set a PostgreSQL or MySQL database; just go to the UCC. For this tutorial we will continue with a MySQL database (PostgreSQL installation steps are quite similar). Let us visit https://ucc.ulyssis.org/mysql; if this is your first time using MySQL you'll need to create a new account by putting in a super secret password. The wizard will create your MySQL account with the same name as your user-account. We'll also create a new database with an appropriate name by clicking on 'Add database'. In this tutorial we will choose; "wiki", notice that it will be prepended with our username, so we'll end up with a new database named "me_wiki". ==Setup your wiki== If all went well, you can access your website at http://username.ulyssis.be/the_folder_you_used and start the setup wizard. In our example, will surf to http://me.ulyssis.be/wiki. The wizard will guide you through some configuration options. Most of them our pretty straight-forward. When in doubt, you can always click the question mark wich will show you some sensible and recommended default... We'll just discuss the page were the wizard asks you for the database. In our example; <pre> Database host: mysql.ulyssis.org Database name: me_wiki // The name of our database; i.e. the name we chose, prepended by our username. Database table prefix: // We can leave this blank. Database user: me // This is the name of our MySQL-user, which was named after our ULLYSIS-username. Database password: supersecretpassword // Please note that this is not your ULLYSIS-password, but the password you used in UCC when creating the MySQL user! </pre> ==Creating the wiki== After the setup wizard is complete, you can begin the installation procedure. If all went well, you'll be greeted by a page which congratulates you with your new installation. ==Finalizing steps== The setup will offer you a configuration file (containing some settings you specified) that you need to download to your server (more specifically in directory where your MediaWiki-files reside in). You again can do this graphically, or if you prefer a terminal; <pre> homeuser@home:~$ scp path_to_file/LocalSettings.php me@ssh1.ulyssis.org:~/www/wiki enter super secret password: </pre> After this is done, you can finally start using your wiki. Please refer to [http://www.mediawiki.org/wiki/MediaWiki the original MediaWiki documentation] for a more detailed or advanced information. [[Category:CMSs]] 2a07683f1e5fa48a2d5ef4f76997211a2e950c93 772 771 2019-08-28T19:36:47Z Bert 8 wikitext text/x-wiki This page will go through a basic setup of MediaWiki. It is based on [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wikipage], and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. This tutorial we'll use a ULYSSIS-account with username "me". == Putting setup-files in place == First we'll have to download the setup file which you can find over at [http://www.mediawiki.org/wiki/Download the official MediaWiki website]. It's an archived file, so you need to extract it first and put the files in a subdirectory of your "document root". The default is just a www directory in your home folder. Putting your files in document_root/wiki/ will make your wiki be located at usersname.ulyssis.be/wiki/. If you prefer, you can do this all graphically using the manual [[Accessing_your_files]]. If you prefer the command line; <pre> homeuser@home:~$ ssh me@ssh1.ulyssis.org enter super secret password: me@zap:~$ wget http://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.6.tar.gz me@zap:~$ tar xvxf mediawiki-1.23.6.tar.gz me@zap:~$ mv mediawiki-1.23.6 www/wiki me@zap:~$ rm -r mediawiki-1.23.6.tar.gz </pre> ==Setting up database== Like the [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wiki] tells us, we have three different options to choose from; PostgreSQL, MySQL and SQLite. It's easy to set a PostgreSQL or MySQL database; just go to the UCC. For this tutorial we will continue with a MySQL database (PostgreSQL installation steps are quite similar). Let us visit https://ucc.ulyssis.org/mysql; if this is your first time using MySQL you'll need to create a new account by putting in a super secret password. The wizard will create your MySQL account with the same name as your user-account. We'll also create a new database with an appropriate name by clicking on 'Add database'. In this tutorial we will choose; "wiki", notice that it will be prepended with our username, so we'll end up with a new database named "me_wiki". ==Setup your wiki== If all went well, you can access your website at http://username.ulyssis.be/the_folder_you_used and start the setup wizard. In our example, will surf to http://me.ulyssis.be/wiki. The wizard will guide you through some configuration options. Most of them our pretty straight-forward. When in doubt, you can always click the question mark wich will show you some sensible and recommended default... We'll just discuss the page were the wizard asks you for the database. In our example; <pre> Database host: mysql.ulyssis.org Database name: me_wiki // The name of our database; i.e. the name we chose, prepended by our username. Database table prefix: // We can leave this blank. Database user: me // This is the name of our MySQL-user, which was named after our ULLYSIS-username. Database password: supersecretpassword // Please note that this is not your ULLYSIS-password, but the password you used in UCC when creating the MySQL user! </pre> ==Creating the wiki== After the setup wizard is complete, you can begin the installation procedure. If all went well, you'll be greeted by a page which congratulates you with your new installation. ==Finishing up installation== The setup will offer you a configuration file (containing some settings you specified) that you need to download to your server (more specifically in directory where your MediaWiki-files reside in). You again can do this graphically, or if you prefer a terminal; <pre> homeuser@home:~$ scp path_to_file/LocalSettings.php me@ssh1.ulyssis.org:~/www/wiki enter super secret password: </pre> After this is done, you can finally start using your wiki. Please refer to [http://www.mediawiki.org/wiki/MediaWiki the original MediaWiki documentation] for a more detailed or advanced information. == Extending MediaWiki == By default, every MediaWiki installation looks and works identical. While that is convenient for users, it can be less than ideal if you need specific functionality or wish to adapt your wiki to your style. === Extensions === === Skins === Skins are similar to themes, templates or styles within other software. By default MediaWiki uses the well known Vector skin. But other skins are available. Sadly, MediaWiki doesn't maintain a complete list of all available skins and whether they work with recent releases, so it may take a bit of perseverance. General information on Skins is available on the [https://www.mediawiki.org/wiki/Manual:Skins Official Manual]. Besides that there's the [https://www.mediawiki.org/wiki/Manual:Gallery_of_user_styles the user style gallery] and [https://www.mediawiki.org/wiki/Category:All_skins the list of skins] [[Category:CMSs]] 7041855846c7e4b76f83c756805b9df409a2a385 773 772 2019-08-28T19:37:01Z Bert 8 /* Extending MediaWiki */ wikitext text/x-wiki This page will go through a basic setup of MediaWiki. It is based on [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wikipage], and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. This tutorial we'll use a ULYSSIS-account with username "me". == Putting setup-files in place == First we'll have to download the setup file which you can find over at [http://www.mediawiki.org/wiki/Download the official MediaWiki website]. It's an archived file, so you need to extract it first and put the files in a subdirectory of your "document root". The default is just a www directory in your home folder. Putting your files in document_root/wiki/ will make your wiki be located at usersname.ulyssis.be/wiki/. If you prefer, you can do this all graphically using the manual [[Accessing_your_files]]. If you prefer the command line; <pre> homeuser@home:~$ ssh me@ssh1.ulyssis.org enter super secret password: me@zap:~$ wget http://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.6.tar.gz me@zap:~$ tar xvxf mediawiki-1.23.6.tar.gz me@zap:~$ mv mediawiki-1.23.6 www/wiki me@zap:~$ rm -r mediawiki-1.23.6.tar.gz </pre> ==Setting up database== Like the [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wiki] tells us, we have three different options to choose from; PostgreSQL, MySQL and SQLite. It's easy to set a PostgreSQL or MySQL database; just go to the UCC. For this tutorial we will continue with a MySQL database (PostgreSQL installation steps are quite similar). Let us visit https://ucc.ulyssis.org/mysql; if this is your first time using MySQL you'll need to create a new account by putting in a super secret password. The wizard will create your MySQL account with the same name as your user-account. We'll also create a new database with an appropriate name by clicking on 'Add database'. In this tutorial we will choose; "wiki", notice that it will be prepended with our username, so we'll end up with a new database named "me_wiki". ==Setup your wiki== If all went well, you can access your website at http://username.ulyssis.be/the_folder_you_used and start the setup wizard. In our example, will surf to http://me.ulyssis.be/wiki. The wizard will guide you through some configuration options. Most of them our pretty straight-forward. When in doubt, you can always click the question mark wich will show you some sensible and recommended default... We'll just discuss the page were the wizard asks you for the database. In our example; <pre> Database host: mysql.ulyssis.org Database name: me_wiki // The name of our database; i.e. the name we chose, prepended by our username. Database table prefix: // We can leave this blank. Database user: me // This is the name of our MySQL-user, which was named after our ULLYSIS-username. Database password: supersecretpassword // Please note that this is not your ULLYSIS-password, but the password you used in UCC when creating the MySQL user! </pre> ==Creating the wiki== After the setup wizard is complete, you can begin the installation procedure. If all went well, you'll be greeted by a page which congratulates you with your new installation. ==Finishing up installation== The setup will offer you a configuration file (containing some settings you specified) that you need to download to your server (more specifically in directory where your MediaWiki-files reside in). You again can do this graphically, or if you prefer a terminal; <pre> homeuser@home:~$ scp path_to_file/LocalSettings.php me@ssh1.ulyssis.org:~/www/wiki enter super secret password: </pre> After this is done, you can finally start using your wiki. Please refer to [http://www.mediawiki.org/wiki/MediaWiki the original MediaWiki documentation] for a more detailed or advanced information. == Extending MediaWiki == By default, every MediaWiki installation looks and works identical. While that is convenient for users, it can be less than ideal if you need specific functionality or wish to adapt your wiki to your style. === Extensions === === Skins === Skins are similar to themes, templates or styles within other software. By default MediaWiki uses the well known Vector skin. But other skins are available. Sadly, MediaWiki doesn't maintain a complete list of all available skins and whether they work with recent releases, so it may take a bit of perseverance. General information on Skins is available on the [https://www.mediawiki.org/wiki/Manual:Skins Official Manual]. Besides that there's the [https://www.mediawiki.org/wiki/Manual:Gallery_of_user_styles the user style gallery] and [https://www.mediawiki.org/wiki/Category:All_skins the list of skins]. [[Category:CMSs]] efb01086b0c8b44698df32357a9fa443e8d4ea54 774 773 2019-08-28T20:00:56Z Bert 8 /* Extensions */ wikitext text/x-wiki This page will go through a basic setup of MediaWiki. It is based on [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wikipage], and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. This tutorial we'll use a ULYSSIS-account with username "me". == Putting setup-files in place == First we'll have to download the setup file which you can find over at [http://www.mediawiki.org/wiki/Download the official MediaWiki website]. It's an archived file, so you need to extract it first and put the files in a subdirectory of your "document root". The default is just a www directory in your home folder. Putting your files in document_root/wiki/ will make your wiki be located at usersname.ulyssis.be/wiki/. If you prefer, you can do this all graphically using the manual [[Accessing_your_files]]. If you prefer the command line; <pre> homeuser@home:~$ ssh me@ssh1.ulyssis.org enter super secret password: me@zap:~$ wget http://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.6.tar.gz me@zap:~$ tar xvxf mediawiki-1.23.6.tar.gz me@zap:~$ mv mediawiki-1.23.6 www/wiki me@zap:~$ rm -r mediawiki-1.23.6.tar.gz </pre> ==Setting up database== Like the [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wiki] tells us, we have three different options to choose from; PostgreSQL, MySQL and SQLite. It's easy to set a PostgreSQL or MySQL database; just go to the UCC. For this tutorial we will continue with a MySQL database (PostgreSQL installation steps are quite similar). Let us visit https://ucc.ulyssis.org/mysql; if this is your first time using MySQL you'll need to create a new account by putting in a super secret password. The wizard will create your MySQL account with the same name as your user-account. We'll also create a new database with an appropriate name by clicking on 'Add database'. In this tutorial we will choose; "wiki", notice that it will be prepended with our username, so we'll end up with a new database named "me_wiki". ==Setup your wiki== If all went well, you can access your website at http://username.ulyssis.be/the_folder_you_used and start the setup wizard. In our example, will surf to http://me.ulyssis.be/wiki. The wizard will guide you through some configuration options. Most of them our pretty straight-forward. When in doubt, you can always click the question mark wich will show you some sensible and recommended default... We'll just discuss the page were the wizard asks you for the database. In our example; <pre> Database host: mysql.ulyssis.org Database name: me_wiki // The name of our database; i.e. the name we chose, prepended by our username. Database table prefix: // We can leave this blank. Database user: me // This is the name of our MySQL-user, which was named after our ULLYSIS-username. Database password: supersecretpassword // Please note that this is not your ULLYSIS-password, but the password you used in UCC when creating the MySQL user! </pre> ==Creating the wiki== After the setup wizard is complete, you can begin the installation procedure. If all went well, you'll be greeted by a page which congratulates you with your new installation. ==Finishing up installation== The setup will offer you a configuration file (containing some settings you specified) that you need to download to your server (more specifically in directory where your MediaWiki-files reside in). You again can do this graphically, or if you prefer a terminal; <pre> homeuser@home:~$ scp path_to_file/LocalSettings.php me@ssh1.ulyssis.org:~/www/wiki enter super secret password: </pre> After this is done, you can finally start using your wiki. Please refer to [http://www.mediawiki.org/wiki/MediaWiki the original MediaWiki documentation] for a more detailed or advanced information. == Extending MediaWiki == By default, every MediaWiki installation looks and works identical. While that is convenient for users, it can be less than ideal if you need specific functionality or wish to adapt your wiki to your style. === Extensions === === Skins === Skins are similar to themes, templates or styles within other software. By default MediaWiki uses the well known Vector skin. But other skins are available. Sadly, MediaWiki doesn't maintain a complete list of all available skins and whether they work with recent releases, so it may take a bit of perseverance. General information on Skins is available on the [https://www.mediawiki.org/wiki/Manual:Skins Official Manual]. Besides that there's the [https://www.mediawiki.org/wiki/Manual:Gallery_of_user_styles the user style gallery] and [https://www.mediawiki.org/wiki/Category:All_skins the list of skins]. [[Category:CMSs]] 07848469b655deed652271b190ba74ba0ecfab44 776 774 2019-08-28T20:18:49Z Bert 8 /* Extensions */ wikitext text/x-wiki This page will go through a basic setup of MediaWiki. It is based on [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wikipage], and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. This tutorial we'll use a ULYSSIS-account with username "me". == Putting setup-files in place == First we'll have to download the setup file which you can find over at [http://www.mediawiki.org/wiki/Download the official MediaWiki website]. It's an archived file, so you need to extract it first and put the files in a subdirectory of your "document root". The default is just a www directory in your home folder. Putting your files in document_root/wiki/ will make your wiki be located at usersname.ulyssis.be/wiki/. If you prefer, you can do this all graphically using the manual [[Accessing_your_files]]. If you prefer the command line; <pre> homeuser@home:~$ ssh me@ssh1.ulyssis.org enter super secret password: me@zap:~$ wget http://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.6.tar.gz me@zap:~$ tar xvxf mediawiki-1.23.6.tar.gz me@zap:~$ mv mediawiki-1.23.6 www/wiki me@zap:~$ rm -r mediawiki-1.23.6.tar.gz </pre> ==Setting up database== Like the [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wiki] tells us, we have three different options to choose from; PostgreSQL, MySQL and SQLite. It's easy to set a PostgreSQL or MySQL database; just go to the UCC. For this tutorial we will continue with a MySQL database (PostgreSQL installation steps are quite similar). Let us visit https://ucc.ulyssis.org/mysql; if this is your first time using MySQL you'll need to create a new account by putting in a super secret password. The wizard will create your MySQL account with the same name as your user-account. We'll also create a new database with an appropriate name by clicking on 'Add database'. In this tutorial we will choose; "wiki", notice that it will be prepended with our username, so we'll end up with a new database named "me_wiki". ==Setup your wiki== If all went well, you can access your website at http://username.ulyssis.be/the_folder_you_used and start the setup wizard. In our example, will surf to http://me.ulyssis.be/wiki. The wizard will guide you through some configuration options. Most of them our pretty straight-forward. When in doubt, you can always click the question mark wich will show you some sensible and recommended default... We'll just discuss the page were the wizard asks you for the database. In our example; <pre> Database host: mysql.ulyssis.org Database name: me_wiki // The name of our database; i.e. the name we chose, prepended by our username. Database table prefix: // We can leave this blank. Database user: me // This is the name of our MySQL-user, which was named after our ULLYSIS-username. Database password: supersecretpassword // Please note that this is not your ULLYSIS-password, but the password you used in UCC when creating the MySQL user! </pre> ==Creating the wiki== After the setup wizard is complete, you can begin the installation procedure. If all went well, you'll be greeted by a page which congratulates you with your new installation. ==Finishing up installation== The setup will offer you a configuration file (containing some settings you specified) that you need to download to your server (more specifically in directory where your MediaWiki-files reside in). You again can do this graphically, or if you prefer a terminal; <pre> homeuser@home:~$ scp path_to_file/LocalSettings.php me@ssh1.ulyssis.org:~/www/wiki enter super secret password: </pre> After this is done, you can finally start using your wiki. Please refer to [http://www.mediawiki.org/wiki/MediaWiki the original MediaWiki documentation] for a more detailed or advanced information. == Extending MediaWiki == By default, every MediaWiki installation looks and works identical. While that is convenient for users, it can be less than ideal if you need specific functionality or wish to adapt your wiki to your style. === Extensions === Extensions add functionality to a wiki. This can be authentication, layout elements for articles, filters, etc. An overview of what kinds of extensions are possible can be found on [https://www.mediawiki.org/wiki/Manual:Extensions the official manual]. Some noteworthy extensions can be used to prevent spam or unauthorised access. You can find more information on [[Preventing spam on MediaWiki]] and [[Securing MediaWiki using Centrale KU Leuven Login]]. We've also found that users sometimes have problems with high amounts of disk space usage. To help those users out, we've developed a MediaWiki extension that can automatically reduce file size of new uploads. Specifically it's possible to compress PDFs, convert inefficient image formats such as BMP and TIFF to PNG, loslessly compress PNG, lossy compress JPG, resize images and strip EXIF data. You can find more details on [https://github.com/ULYSSIS-KUL/CompressUploads] === Skins === Skins are similar to themes, templates or styles within other software. By default MediaWiki uses the well known Vector skin. But other skins are available. Sadly, MediaWiki doesn't maintain a complete list of all available skins and whether they work with recent releases, so it may take a bit of perseverance. General information on Skins is available on the [https://www.mediawiki.org/wiki/Manual:Skins Official Manual]. Besides that there's the [https://www.mediawiki.org/wiki/Manual:Gallery_of_user_styles the user style gallery] and [https://www.mediawiki.org/wiki/Category:All_skins the list of skins]. [[Category:CMSs]] b5de279e4779224250b8e8f797a43b48526599d6 777 776 2019-08-28T20:19:00Z Bert 8 /* Extensions */ wikitext text/x-wiki This page will go through a basic setup of MediaWiki. It is based on [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wikipage], and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. This tutorial we'll use a ULYSSIS-account with username "me". == Putting setup-files in place == First we'll have to download the setup file which you can find over at [http://www.mediawiki.org/wiki/Download the official MediaWiki website]. It's an archived file, so you need to extract it first and put the files in a subdirectory of your "document root". The default is just a www directory in your home folder. Putting your files in document_root/wiki/ will make your wiki be located at usersname.ulyssis.be/wiki/. If you prefer, you can do this all graphically using the manual [[Accessing_your_files]]. If you prefer the command line; <pre> homeuser@home:~$ ssh me@ssh1.ulyssis.org enter super secret password: me@zap:~$ wget http://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.6.tar.gz me@zap:~$ tar xvxf mediawiki-1.23.6.tar.gz me@zap:~$ mv mediawiki-1.23.6 www/wiki me@zap:~$ rm -r mediawiki-1.23.6.tar.gz </pre> ==Setting up database== Like the [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wiki] tells us, we have three different options to choose from; PostgreSQL, MySQL and SQLite. It's easy to set a PostgreSQL or MySQL database; just go to the UCC. For this tutorial we will continue with a MySQL database (PostgreSQL installation steps are quite similar). Let us visit https://ucc.ulyssis.org/mysql; if this is your first time using MySQL you'll need to create a new account by putting in a super secret password. The wizard will create your MySQL account with the same name as your user-account. We'll also create a new database with an appropriate name by clicking on 'Add database'. In this tutorial we will choose; "wiki", notice that it will be prepended with our username, so we'll end up with a new database named "me_wiki". ==Setup your wiki== If all went well, you can access your website at http://username.ulyssis.be/the_folder_you_used and start the setup wizard. In our example, will surf to http://me.ulyssis.be/wiki. The wizard will guide you through some configuration options. Most of them our pretty straight-forward. When in doubt, you can always click the question mark wich will show you some sensible and recommended default... We'll just discuss the page were the wizard asks you for the database. In our example; <pre> Database host: mysql.ulyssis.org Database name: me_wiki // The name of our database; i.e. the name we chose, prepended by our username. Database table prefix: // We can leave this blank. Database user: me // This is the name of our MySQL-user, which was named after our ULLYSIS-username. Database password: supersecretpassword // Please note that this is not your ULLYSIS-password, but the password you used in UCC when creating the MySQL user! </pre> ==Creating the wiki== After the setup wizard is complete, you can begin the installation procedure. If all went well, you'll be greeted by a page which congratulates you with your new installation. ==Finishing up installation== The setup will offer you a configuration file (containing some settings you specified) that you need to download to your server (more specifically in directory where your MediaWiki-files reside in). You again can do this graphically, or if you prefer a terminal; <pre> homeuser@home:~$ scp path_to_file/LocalSettings.php me@ssh1.ulyssis.org:~/www/wiki enter super secret password: </pre> After this is done, you can finally start using your wiki. Please refer to [http://www.mediawiki.org/wiki/MediaWiki the original MediaWiki documentation] for a more detailed or advanced information. == Extending MediaWiki == By default, every MediaWiki installation looks and works identical. While that is convenient for users, it can be less than ideal if you need specific functionality or wish to adapt your wiki to your style. === Extensions === Extensions add functionality to a wiki. This can be authentication, layout elements for articles, filters, etc. An overview of what kinds of extensions are possible can be found on [https://www.mediawiki.org/wiki/Manual:Extensions the official manual]. Some noteworthy extensions can be used to prevent spam or unauthorised access. You can find more information on [[Preventing spam on MediaWiki]] and [[Securing MediaWiki using Centrale KU Leuven Login]]. We've also found that users sometimes have problems with high amounts of disk space usage. To help those users out, we've developed a MediaWiki extension that can automatically reduce file size of new uploads. Specifically it's possible to compress PDFs, convert inefficient image formats such as BMP and TIFF to PNG, loslessly compress PNG, lossy compress JPG, resize images and strip EXIF data. You can find more details on https://github.com/ULYSSIS-KUL/CompressUploads === Skins === Skins are similar to themes, templates or styles within other software. By default MediaWiki uses the well known Vector skin. But other skins are available. Sadly, MediaWiki doesn't maintain a complete list of all available skins and whether they work with recent releases, so it may take a bit of perseverance. General information on Skins is available on the [https://www.mediawiki.org/wiki/Manual:Skins Official Manual]. Besides that there's the [https://www.mediawiki.org/wiki/Manual:Gallery_of_user_styles the user style gallery] and [https://www.mediawiki.org/wiki/Category:All_skins the list of skins]. [[Category:CMSs]] 6201ed0bb71935b8f82e478da0d65757b9130ec0 778 777 2019-08-28T20:23:39Z Bert 8 /* Extensions */ wikitext text/x-wiki This page will go through a basic setup of MediaWiki. It is based on [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wikipage], and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. This tutorial we'll use a ULYSSIS-account with username "me". == Putting setup-files in place == First we'll have to download the setup file which you can find over at [http://www.mediawiki.org/wiki/Download the official MediaWiki website]. It's an archived file, so you need to extract it first and put the files in a subdirectory of your "document root". The default is just a www directory in your home folder. Putting your files in document_root/wiki/ will make your wiki be located at usersname.ulyssis.be/wiki/. If you prefer, you can do this all graphically using the manual [[Accessing_your_files]]. If you prefer the command line; <pre> homeuser@home:~$ ssh me@ssh1.ulyssis.org enter super secret password: me@zap:~$ wget http://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.6.tar.gz me@zap:~$ tar xvxf mediawiki-1.23.6.tar.gz me@zap:~$ mv mediawiki-1.23.6 www/wiki me@zap:~$ rm -r mediawiki-1.23.6.tar.gz </pre> ==Setting up database== Like the [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wiki] tells us, we have three different options to choose from; PostgreSQL, MySQL and SQLite. It's easy to set a PostgreSQL or MySQL database; just go to the UCC. For this tutorial we will continue with a MySQL database (PostgreSQL installation steps are quite similar). Let us visit https://ucc.ulyssis.org/mysql; if this is your first time using MySQL you'll need to create a new account by putting in a super secret password. The wizard will create your MySQL account with the same name as your user-account. We'll also create a new database with an appropriate name by clicking on 'Add database'. In this tutorial we will choose; "wiki", notice that it will be prepended with our username, so we'll end up with a new database named "me_wiki". ==Setup your wiki== If all went well, you can access your website at http://username.ulyssis.be/the_folder_you_used and start the setup wizard. In our example, will surf to http://me.ulyssis.be/wiki. The wizard will guide you through some configuration options. Most of them our pretty straight-forward. When in doubt, you can always click the question mark wich will show you some sensible and recommended default... We'll just discuss the page were the wizard asks you for the database. In our example; <pre> Database host: mysql.ulyssis.org Database name: me_wiki // The name of our database; i.e. the name we chose, prepended by our username. Database table prefix: // We can leave this blank. Database user: me // This is the name of our MySQL-user, which was named after our ULLYSIS-username. Database password: supersecretpassword // Please note that this is not your ULLYSIS-password, but the password you used in UCC when creating the MySQL user! </pre> ==Creating the wiki== After the setup wizard is complete, you can begin the installation procedure. If all went well, you'll be greeted by a page which congratulates you with your new installation. ==Finishing up installation== The setup will offer you a configuration file (containing some settings you specified) that you need to download to your server (more specifically in directory where your MediaWiki-files reside in). You again can do this graphically, or if you prefer a terminal; <pre> homeuser@home:~$ scp path_to_file/LocalSettings.php me@ssh1.ulyssis.org:~/www/wiki enter super secret password: </pre> After this is done, you can finally start using your wiki. Please refer to [http://www.mediawiki.org/wiki/MediaWiki the original MediaWiki documentation] for a more detailed or advanced information. == Extending MediaWiki == By default, every MediaWiki installation looks and works identical. While that is convenient for users, it can be less than ideal if you need specific functionality or wish to adapt your wiki to your style. === Extensions === Extensions add functionality to a wiki, such as more fine-grained authentication, extra layout elements for articles or text filters. An overview of what kinds of extensions are possible can be found on [https://www.mediawiki.org/wiki/Manual:Extensions the official manual]. Some noteworthy extensions can be used to prevent spam or unauthorised access. You can find more information on [[Preventing spam on MediaWiki]] and [[Securing MediaWiki using Centrale KU Leuven Login]]. We've also found that users sometimes have problems with high amounts of disk space usage. To help those users out, we've developed a MediaWiki extension that can automatically reduce file size of new uploads. Specifically it's possible to compress PDFs, convert inefficient image formats such as BMP and TIFF to PNG, loslessly compress PNG, lossy compress JPG, resize images and strip EXIF data. You can find more details on https://github.com/ULYSSIS-KUL/CompressUploads === Skins === Skins are similar to themes, templates or styles within other software. By default MediaWiki uses the well known Vector skin. But other skins are available. Sadly, MediaWiki doesn't maintain a complete list of all available skins and whether they work with recent releases, so it may take a bit of perseverance. General information on Skins is available on the [https://www.mediawiki.org/wiki/Manual:Skins Official Manual]. Besides that there's the [https://www.mediawiki.org/wiki/Manual:Gallery_of_user_styles the user style gallery] and [https://www.mediawiki.org/wiki/Category:All_skins the list of skins]. [[Category:CMSs]] 32a2fcab3b1b027d448e9f7afad1d1cd99d2bfe3 0 54 775 740 2019-08-28T20:05:32Z Yoa 30 wikitext text/x-wiki == About ReCaptcha == Google introduced a new generation of ReCaptcha, called NoCaptcha in 2014. Using the MediaWiki extension ConfirmEdit, NoCaptcha can be used to prevent spam on wikis. ConfirmEdit is bundled with MediaWiki by default, but to enable NoCaptcha, you will have to get an API key from Google. == Installation == The NoCaptcha ConfirmEdit extension requires MediaWiki 1.26 or higher. First, you have to get an API key from Google. Go to Google's ReCaptcha administrator page https://www.google.com/recaptcha/admin and register your website. You will need to select '''reCAPTCHA v2''', and '''"I'm not a robot" Checkbox'''. After registering your website, you will be presented with a public '''site key''' and a private '''secret key'''. Now you have to install and configure the ConfirmEdit extension. Locate the <code>LocalSettings.php</code> file in your MediaWiki installation folder and add the following lines to it: wfLoadExtensions([ 'ConfirmEdit', 'ConfirmEdit/ReCaptchaNoCaptcha' ]); $wgCaptchaClass = 'ReCaptchaNoCaptcha'; $wgReCaptchaSiteKey = 'your public/site key here'; $wgReCaptchaSecretKey = 'your private/secret key here'; More information about the configuration options for advanced usage can be found here: https://www.mediawiki.org/wiki/Extension:ConfirmEdit#Configuration [[Category:Security & anti-spam]] 71d202bf32dcc49916ec43346641b25c21abf2a1 779 775 2019-08-28T20:37:16Z Yoa 30 wikitext text/x-wiki Because MediaWiki allows for unrestricted page editing by anonymous users and unrestricted account creation, MediaWiki websites often suffer from automated spam problems. There are 2 main ways to prevent spam on MediaWiki: using a captcha to block automated edits, and restricting account creation to trusted users. == Using captcha == === About ReCaptcha === Google introduced a new generation of ReCaptcha, called NoCaptcha in 2014. Using the MediaWiki extension ConfirmEdit, NoCaptcha can be used to prevent spam on wikis. ConfirmEdit is bundled with MediaWiki by default, but to enable NoCaptcha, you will have to get an API key from Google. === Installation === The NoCaptcha ConfirmEdit extension requires MediaWiki 1.26 or higher. First, you have to get an API key from Google. Go to Google's ReCaptcha [https://www.google.com/recaptcha/admin administrator page] and register your website. You will need to select '''reCAPTCHA v2''', and '''"I'm not a robot" Checkbox'''. After registering your website, you will be presented with a public '''site key''' and a private '''secret key'''. Now you have to install and configure the ConfirmEdit extension. Locate the <code>LocalSettings.php</code> file in your MediaWiki installation folder and add the following lines to it: wfLoadExtensions([ 'ConfirmEdit', 'ConfirmEdit/ReCaptchaNoCaptcha' ]); $wgCaptchaClass = 'ReCaptchaNoCaptcha'; $wgReCaptchaSiteKey = 'your public/site key here'; $wgReCaptchaSecretKey = 'your private/secret key here'; $wgCaptchaTriggers['edit'] = true; // Trigger captcha for page edits. $wgCaptchaTriggers['create'] = true; // Trigger captcha for page creation. $wgCaptchaTriggers['addurl'] = true; // Trigger captcha for page edits containing URLs. $wgCaptchaTriggers['createaccount'] = true; // Trigger captcha for account creation. $wgCaptchaTriggers['badlogin'] = true; // Trigger captcha for login hacking attempts. More information about the configuration options for advanced usage can be found here: https://www.mediawiki.org/wiki/Extension:ConfirmEdit#Configuration == Restricting account creation == Because MediaWiki allows unregistered (anonymous) users to edit pages, this technique obviously relies on restricting page edits to logged-in users. To enable this, locate the <code>LocalSettings.php</code> file in your MediaWiki installation folder and add the following lines to it: $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; Now only registered users can edit or create pages. However, the problem is not solved, as bots can automatically create an account to perform the spamming. There are 3 options to prevent this. === Centrale KU Leuven Login === Wikis connected to the KU Leuven Association can install an extension to use the Centrale KU Leuven Login. For more information about this option, there is the documentation page [[Securing MediaWiki using Centrale KU Leuven Login]]. === Sysop account creation === Account creation can be restricted to only website administrators ('sysop'). Add the following line to <code>LocalSettings.php</code>: $wgGroupPermissions['*']['createaccount'] = false; === Account creation queue === Using the extension [https://www.mediawiki.org/wiki/Extension:ConfirmAccount ConfirmAccount], account creation has to be manually confirmed by website administrators. Users are still able to create an account, but the account has to be confirmed before the user can log in. For more information, installation instructions and configuration, refer to the link above. [[Category:Security & anti-spam]] f9d6775dd0bcade9ff2865d646a53293d3244f43 780 779 2019-08-28T20:37:35Z Yoa 30 wikitext text/x-wiki Because MediaWiki allows for unrestricted page editing by anonymous users and unrestricted account creation, MediaWiki websites often suffer from automated spam problems. There are 2 main ways to prevent spam on MediaWiki: using a captcha to block automated edits, or restricting account creation to trusted users. == Using captcha == === About ReCaptcha === Google introduced a new generation of ReCaptcha, called NoCaptcha in 2014. Using the MediaWiki extension ConfirmEdit, NoCaptcha can be used to prevent spam on wikis. ConfirmEdit is bundled with MediaWiki by default, but to enable NoCaptcha, you will have to get an API key from Google. === Installation === The NoCaptcha ConfirmEdit extension requires MediaWiki 1.26 or higher. First, you have to get an API key from Google. Go to Google's ReCaptcha [https://www.google.com/recaptcha/admin administrator page] and register your website. You will need to select '''reCAPTCHA v2''', and '''"I'm not a robot" Checkbox'''. After registering your website, you will be presented with a public '''site key''' and a private '''secret key'''. Now you have to install and configure the ConfirmEdit extension. Locate the <code>LocalSettings.php</code> file in your MediaWiki installation folder and add the following lines to it: wfLoadExtensions([ 'ConfirmEdit', 'ConfirmEdit/ReCaptchaNoCaptcha' ]); $wgCaptchaClass = 'ReCaptchaNoCaptcha'; $wgReCaptchaSiteKey = 'your public/site key here'; $wgReCaptchaSecretKey = 'your private/secret key here'; $wgCaptchaTriggers['edit'] = true; // Trigger captcha for page edits. $wgCaptchaTriggers['create'] = true; // Trigger captcha for page creation. $wgCaptchaTriggers['addurl'] = true; // Trigger captcha for page edits containing URLs. $wgCaptchaTriggers['createaccount'] = true; // Trigger captcha for account creation. $wgCaptchaTriggers['badlogin'] = true; // Trigger captcha for login hacking attempts. More information about the configuration options for advanced usage can be found here: https://www.mediawiki.org/wiki/Extension:ConfirmEdit#Configuration == Restricting account creation == Because MediaWiki allows unregistered (anonymous) users to edit pages, this technique obviously relies on restricting page edits to logged-in users. To enable this, locate the <code>LocalSettings.php</code> file in your MediaWiki installation folder and add the following lines to it: $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; Now only registered users can edit or create pages. However, the problem is not solved, as bots can automatically create an account to perform the spamming. There are 3 options to prevent this. === Centrale KU Leuven Login === Wikis connected to the KU Leuven Association can install an extension to use the Centrale KU Leuven Login. For more information about this option, there is the documentation page [[Securing MediaWiki using Centrale KU Leuven Login]]. === Sysop account creation === Account creation can be restricted to only website administrators ('sysop'). Add the following line to <code>LocalSettings.php</code>: $wgGroupPermissions['*']['createaccount'] = false; === Account creation queue === Using the extension [https://www.mediawiki.org/wiki/Extension:ConfirmAccount ConfirmAccount], account creation has to be manually confirmed by website administrators. Users are still able to create an account, but the account has to be confirmed before the user can log in. For more information, installation instructions and configuration, refer to the link above. [[Category:Security & anti-spam]] 1d0c95010677b2f1daa16eb2e08bbf820beb27d3 781 780 2019-08-28T20:43:45Z Yoa 30 wikitext text/x-wiki Because MediaWiki allows for unrestricted page editing by anonymous users and unrestricted account creation, MediaWiki websites often suffer from automated spam problems. There are 2 main ways to prevent spam on MediaWiki: using a captcha to block automated edits, or restricting account creation to trusted users. == Using captcha == === About ReCaptcha === Google introduced a new generation of ReCaptcha, called NoCaptcha in 2014. Using the MediaWiki extension ConfirmEdit, NoCaptcha can be used to prevent spam on wikis. ConfirmEdit is bundled with MediaWiki by default, but to enable NoCaptcha, you will have to get an API key from Google. === Installation === The NoCaptcha ConfirmEdit extension requires MediaWiki 1.26 or higher. First, you have to get an API key from Google. Go to Google's ReCaptcha [https://www.google.com/recaptcha/admin administrator page] and register your website. You will need to select '''reCAPTCHA v2''', and '''"I'm not a robot" Checkbox'''. After registering your website, you will be presented with a public '''site key''' and a private '''secret key'''. Now you have to install and configure the ConfirmEdit extension. Locate the <code>LocalSettings.php</code> file in your MediaWiki installation folder and add the following lines to it: wfLoadExtensions([ 'ConfirmEdit', 'ConfirmEdit/ReCaptchaNoCaptcha' ]); $wgCaptchaClass = 'ReCaptchaNoCaptcha'; $wgReCaptchaSiteKey = ''''your public/site key here''''; $wgReCaptchaSecretKey = ''''your private/secret key here''''; $wgCaptchaTriggers['edit'] = true; // Trigger captcha for page edits. $wgCaptchaTriggers['create'] = true; // Trigger captcha for page creation. $wgCaptchaTriggers['addurl'] = true; // Trigger captcha for page edits containing URLs. $wgCaptchaTriggers['createaccount'] = true; // Trigger captcha for account creation. $wgCaptchaTriggers['badlogin'] = true; // Trigger captcha for login hacking attempts. More information about the configuration options for advanced usage can be found here: https://www.mediawiki.org/wiki/Extension:ConfirmEdit#Configuration == Restricting account creation == Because MediaWiki allows unregistered (anonymous) users to edit pages, this technique obviously relies on restricting page edits to logged-in users. To enable this, locate the <code>LocalSettings.php</code> file in your MediaWiki installation folder and add the following lines to it: $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; Now only registered users can edit or create pages. However, the problem is not solved, as bots can automatically create an account to perform the spamming. There are 3 options to prevent this. === Centrale KU Leuven Login === Wikis connected to the KU Leuven Association can install an extension to use the Centrale KU Leuven Login. For more information about this option, there is the documentation page [[Securing MediaWiki using Centrale KU Leuven Login]]. === Sysop account creation === Account creation can be restricted to only website administrators ('sysop'). Add the following line to <code>LocalSettings.php</code>: $wgGroupPermissions['*']['createaccount'] = false; === Account creation queue === Using the extension [https://www.mediawiki.org/wiki/Extension:ConfirmAccount ConfirmAccount], account creation has to be manually confirmed by website administrators. Users are still able to create an account, but the account has to be confirmed before the user can log in. For more information, installation instructions and configuration, refer to the link above. [[Category:Security & anti-spam]] f7c8795f3a1310e1f52c6386cedbb93d4d02e541 0 98 782 738 2019-08-28T22:50:32Z Yoa 30 /* Installation */ wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for login through the Central KU Leuven Login (Shibboleth). The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Central KU Leuven Login) enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest/MediaWikiShibboleth.zip github]. Unzip the zip file in the <code>extensions/</code> directory in your MediaWiki installation folder. Make sure there is now a <code>MediaWikiShibboleth</code> folder in <code>extensions/</code>. Finally, locate the <code>LocalSettings.php</code> file in your MediaWiki installation folder and add the following lines to it: wfLoadExtension('MediaWikiShibboleth'); $wgGroupPermissions['*']['createaccount'] = false; $wgRevokePermissions['Shibboleth']['editmyprivateinfo'] = true; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. This really defeats the purpose of the extension though. ==Configuration== MediaWikiShibboleth has some configuration options which allow for restricting who can log in to your wiki. These restrictions are cumulative. For example, it is possible to allow only students enrolled in a specific degree or programme to log in. These options work especially well with restricting the access of the wiki to logged-in users only. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code>LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code>LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code>LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code>LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. === Translations === It's possible to translate and modify all public MediaWikiShibboleth messages. The translations can be found in the <code>extensions/MediaWikiShibboleth/i18n/</code>. Dutch (<code>nl.json</code>) and English (<code>en.json</code>) translations are already provided. Even the provided translations can be customized, and we strongly advise you to do so, in order to match them with your Wiki situation. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Login without Central KU Leuven login" to expand a login menu. The new log in page looks like this with "Login without Central KU Leuven login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] [[Category:Security & anti-spam]] b60508558689b24750e7b3809565b68a696f7a0a 783 782 2019-08-28T22:51:02Z Yoa 30 /* Installation */ wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for login through the Central KU Leuven Login (Shibboleth). The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Central KU Leuven Login) enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest/download/MediaWikiShibboleth.zip github]. Unzip the zip file in the <code>extensions/</code> directory in your MediaWiki installation folder. Make sure there is now a <code>MediaWikiShibboleth</code> folder in <code>extensions/</code>. Finally, locate the <code>LocalSettings.php</code> file in your MediaWiki installation folder and add the following lines to it: wfLoadExtension('MediaWikiShibboleth'); $wgGroupPermissions['*']['createaccount'] = false; $wgRevokePermissions['Shibboleth']['editmyprivateinfo'] = true; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. This really defeats the purpose of the extension though. ==Configuration== MediaWikiShibboleth has some configuration options which allow for restricting who can log in to your wiki. These restrictions are cumulative. For example, it is possible to allow only students enrolled in a specific degree or programme to log in. These options work especially well with restricting the access of the wiki to logged-in users only. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code>LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code>LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code>LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow persons enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code>LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. === Translations === It's possible to translate and modify all public MediaWikiShibboleth messages. The translations can be found in the <code>extensions/MediaWikiShibboleth/i18n/</code>. Dutch (<code>nl.json</code>) and English (<code>en.json</code>) translations are already provided. Even the provided translations can be customized, and we strongly advise you to do so, in order to match them with your Wiki situation. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Login without Central KU Leuven login" to expand a login menu. The new log in page looks like this with "Login without Central KU Leuven login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] [[Category:Security & anti-spam]] 46848c43e313598d696d8300cc4af23e3b940e7b 0 40 784 748 2019-09-09T15:35:54Z Bert 8 wikitext text/x-wiki You can access your MySQL databases using PHPMyAdmin. This application can be found on https://phpmyadmin.ulyssis.org. To login you need to use your MySQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your MySQL password you can get it from your websites configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. == Basic Usage == On the left you will see your username, you can click the plus sign to reveal all your databases. You can then view databases and tables. For each table you can view the records, view and change the structure, add records, take backups, etc. Detailed documentation is available on the PHPMyAdmin [[https://www.phpmyadmin.net/docs/ official documentation website]] == Taking Backups == To take a backup of all your databases you simple select "Export" on the main menu and press start. You can later restore backups by uploading the file to the "Import" page. [[Category:Databases]] 9d7c9e6f54aa54ecaa524090c4eeb4bc0589b4b4 785 784 2019-09-09T15:36:00Z Bert 8 wikitext text/x-wiki You can access your MySQL databases using PHPMyAdmin. This application can be found on https://phpmyadmin.ulyssis.org. To login you need to use your MySQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your MySQL password you can get it from your websites configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. == Basic Usage == On the left you will see your username, you can click the plus sign to reveal all your databases. You can then view databases and tables. For each table you can view the records, view and change the structure, add records, take backups, etc. Detailed documentation is available on the PHPMyAdmin [https://www.phpmyadmin.net/docs/ official documentation website] == Taking Backups == To take a backup of all your databases you simple select "Export" on the main menu and press start. You can later restore backups by uploading the file to the "Import" page. [[Category:Databases]] defd084a6c7b039f50a92baa9a64b8c1304d49ae 786 785 2019-09-09T15:37:25Z Bert 8 wikitext text/x-wiki You can access your MySQL databases using PHPMyAdmin. This application can be found on https://phpmyadmin.ulyssis.org. To login you need to use your MySQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your MySQL password you can get it from your websites configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. == Basic Usage == Once you've logged in, you will see your username on the left, you can click the plus sign to reveal all your databases. You can then view databases and tables. For each table you can view the records, view and change the structure, add records, take backups, etc. Detailed documentation is available on the PHPMyAdmin [https://www.phpmyadmin.net/docs/ official documentation website] == Taking Backups == To take a backup of all your databases you simple select "Export" on the main menu and press start. You can later restore backups by uploading the file to the "Import" page. [[Category:Databases]] c1b33b47c847c8f550b6318f9b87f03c8f576de5 787 786 2019-09-09T15:43:49Z Bert 8 wikitext text/x-wiki You can access your MySQL databases using PHPMyAdmin. This application can be found on https://phpmyadmin.ulyssis.org. To login you need to use your MySQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your MySQL password you can get it from your websites configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. == Basic Usage == Once you've logged in, you will see your username on the left, you can click the plus sign to reveal all your databases. You can then view databases and tables. For each table you can view the records, view and change the structure, add records, take backups, etc. Detailed documentation is available on the PHPMyAdmin [https://www.phpmyadmin.net/docs/ official documentation website] == Taking Backups == To take a backup of all your databases you simply select "Export" on the main menu and press start. You can later restore backups by uploading the file to the "Import" page. [[Category:Databases]] 09d34072321f028ba51aae01d511467a50fff0b0 797 787 2019-09-10T14:12:56Z Bert 8 wikitext text/x-wiki You can access your MySQL databases using PHPMyAdmin. This application can be found on https://phpmyadmin.ulyssis.org. To login you need to use your MySQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your MySQL password you can get it from your websites configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. == Basic Usage == Once you've logged in, you will see your username on the left, you can click the plus sign to reveal all your databases. You can then view databases and tables. For each table you can view the records, view and change the structure, add records, take backups, etc. Detailed documentation is available on the PHPMyAdmin [https://www.phpmyadmin.net/docs/ official documentation website] == Making Backups == To take a backup of all your databases you simply select "Export" on the main menu and press start. You can later restore backups by uploading the file to the "Import" page. [[Category:Databases]] d4d4cfcec2a3425e1648c13a8ad6e2cf08354021 798 797 2019-09-11T01:41:59Z Bert 8 /* Making Backups */ wikitext text/x-wiki You can access your MySQL databases using PHPMyAdmin. This application can be found on https://phpmyadmin.ulyssis.org. To login you need to use your MySQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your MySQL password you can get it from your websites configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. == Basic Usage == Once you've logged in, you will see your username on the left, you can click the plus sign to reveal all your databases. You can then view databases and tables. For each table you can view the records, view and change the structure, add records, take backups, etc. Detailed documentation is available on the PHPMyAdmin [https://www.phpmyadmin.net/docs/ official documentation website] == Making Backups == PHPMyAdmin has an export option which can be used to backup the structure and/or data of databases and tables. When no databases or table has been selected, the export tab in the top menu allows to export all databases at the same time. When a specific database or table is selected, that database or table is exported on the export tab. You can either accept the default settings, or ask for more settings to specificy whether any checks, DROPs or time settings are required, as well as to specify if you wish to export the structure, the data or both. You can later restore backups by uploading the file through the form on the import tab. To make restoring easier, we suggest you backup individual databases or even individual tables. [[Category:Databases]] 76b7221b608096b972fff23549e5936c06fd42f3 799 798 2019-09-11T01:43:06Z Bert 8 /* Making Backups */ wikitext text/x-wiki You can access your MySQL databases using PHPMyAdmin. This application can be found on https://phpmyadmin.ulyssis.org. To login you need to use your MySQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your MySQL password you can get it from your websites configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. == Basic Usage == Once you've logged in, you will see your username on the left, you can click the plus sign to reveal all your databases. You can then view databases and tables. For each table you can view the records, view and change the structure, add records, take backups, etc. Detailed documentation is available on the PHPMyAdmin [https://www.phpmyadmin.net/docs/ official documentation website] == Making Backups == PHPMyAdmin has an export option which can be used to backup the structure and/or data of databases and tables. When no database or table has been selected, the export tab in the top menu allows to export all databases at the same time. When a specific database or table is selected, that database or table is exported. You can either accept the default settings, or ask for more settings, to specificy whether any checks, DROPs or time settings are required, as well as to specify if you wish to export the structure, the data or both. You can later restore backups by uploading the file through the form on the import tab. To make restoring easier, we suggest you backup individual databases or even individual tables. [[Category:Databases]] 18cd11247bcd118cd8b2b7fede405a09aa46233a 802 799 2019-09-11T02:57:16Z Bert 8 wikitext text/x-wiki You can access your MySQL databases using PHPMyAdmin. This application can be found on https://phpmyadmin.ulyssis.org. To login you need to use your MySQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your MySQL password you can get it from your websites configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. You can change your database passwords through our control panel [https://ucc.ulyssis.org/ UCC], but keep in mind to then also change the password in relevant configuration files, or you applications may stop working correctly. == Basic Usage == Once you've logged in, you will see your username on the left, you can click the plus sign to reveal all your databases. You can then view databases and tables. For each table you can view the records, view and change the structure, add records, take backups, etc. Detailed documentation is available on the PHPMyAdmin [https://www.phpmyadmin.net/docs/ official documentation website] == Making Backups == PHPMyAdmin has an export option which can be used to backup the structure and/or data of databases and tables. When no database or table has been selected, the export tab in the top menu allows to export all databases at the same time. When a specific database or table is selected, that database or table is exported. You can either accept the default settings, or ask for more settings, to specificy whether any checks, DROPs or time settings are required, as well as to specify if you wish to export the structure, the data or both. You can later restore backups by uploading the file through the form on the import tab. To make restoring easier, we suggest you backup individual databases or even individual tables. [[Category:Databases]] c00dca3b3273072eded809a76fb8dc9d3b61d32c 0 126 788 2019-09-09T15:46:18Z Bert 8 Created page with "You can access your PostgreSQL databases using PHPPgAdmin. This application can be found on https://phppgadmin.ulyssis.org. To login you need to use your PostgreSQL password,..." wikitext text/x-wiki You can access your PostgreSQL databases using PHPPgAdmin. This application can be found on https://phppgadmin.ulyssis.org. To login you need to use your PostgreSQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your PostgreSQL password you can get it from your websites configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. == Basic Usage == You can login by clicking on the only server in the left sidebar ''PostgreSQL voor gebruikers, kringen en organisaties''. Once you've logged in, you will see an overview of all your databases. You can then view databases, schemas and tables by clicking on them or navigating through the sidebar. For each table you can view the records, view and change the structure, add records, take backups, etc. Official documentation of all functionality is sadly lacking, but you can still refer to [http://phppgadmin.sourceforge.net/doku.php?id=faq_docs the official documentation] == Taking Backups == To take a backup of all your databases you simple select "Export" on the main menu, define whether you wish to export data, structure or both, and press export. You can later restore backups by uploading the file to the "SQL" page. To make restoring easier, we suggest however you backup individual databases or even individual tables and use the SQL format instead of COPY. [[Category:Databases]] 227d80ca3320708e68e16c412f57911c7fc756b1 794 788 2019-09-09T21:03:06Z Yoa 30 /* Taking Backups */ wikitext text/x-wiki You can access your PostgreSQL databases using PHPPgAdmin. This application can be found on https://phppgadmin.ulyssis.org. To login you need to use your PostgreSQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your PostgreSQL password you can get it from your websites configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. == Basic Usage == You can login by clicking on the only server in the left sidebar ''PostgreSQL voor gebruikers, kringen en organisaties''. Once you've logged in, you will see an overview of all your databases. You can then view databases, schemas and tables by clicking on them or navigating through the sidebar. For each table you can view the records, view and change the structure, add records, take backups, etc. Official documentation of all functionality is sadly lacking, but you can still refer to [http://phppgadmin.sourceforge.net/doku.php?id=faq_docs the official documentation] == Taking Backups == To take a backup of all your databases you simply select "Export" on the main menu, define whether you wish to export data, structure or both, and press export. You can later restore backups by uploading the file to the "SQL" page. To make restoring easier, we suggest however you backup individual databases or even individual tables and use the SQL format instead of COPY. [[Category:Databases]] 4b4edcf6822cf73c59875c027f3d217868c290bf 796 794 2019-09-10T14:12:52Z Bert 8 wikitext text/x-wiki You can access your PostgreSQL databases using PHPPgAdmin. This application can be found on https://phppgadmin.ulyssis.org. To login you need to use your PostgreSQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your PostgreSQL password you can get it from your websites configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. == Basic Usage == You can login by clicking on the only server in the left sidebar ''PostgreSQL voor gebruikers, kringen en organisaties''. Once you've logged in, you will see an overview of all your databases. You can then view databases, schemas and tables by clicking on them or navigating through the sidebar. For each table you can view the records, view and change the structure, add records, take backups, etc. Official documentation of all functionality is sadly lacking, but you can still refer to [http://phppgadmin.sourceforge.net/doku.php?id=faq_docs the official documentation] == Making Backups == To take a backup of all your databases you simply select "Export" on the main menu, define whether you wish to export data, structure or both, and press export. You can later restore backups by uploading the file to the "SQL" page. To make restoring easier, we suggest however you backup individual databases or even individual tables and use the SQL format instead of COPY. [[Category:Databases]] a205f576e98304c624ef69dc5c10879f20a4aac1 800 796 2019-09-11T02:10:37Z Bert 8 /* Making Backups */ wikitext text/x-wiki You can access your PostgreSQL databases using PHPPgAdmin. This application can be found on https://phppgadmin.ulyssis.org. To login you need to use your PostgreSQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your PostgreSQL password you can get it from your websites configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. == Basic Usage == You can login by clicking on the only server in the left sidebar ''PostgreSQL voor gebruikers, kringen en organisaties''. Once you've logged in, you will see an overview of all your databases. You can then view databases, schemas and tables by clicking on them or navigating through the sidebar. For each table you can view the records, view and change the structure, add records, take backups, etc. Official documentation of all functionality is sadly lacking, but you can still refer to [http://phppgadmin.sourceforge.net/doku.php?id=faq_docs the official documentation] == Making Backups == PHPPgAdmin has an export option which can be used to backup the structure and/or data of databases, schemas and tables, as well as more advanced features such as sequences and functions. When no database, schema or table has been selected, the export tab in the top menu allows to export all databases at the same time. When a specific database or table is selected, that database or table is exported. You can decide whether you wish to export the structure, the data or both, as well as the format and if DROPs need to be included. You can later restore backups by uploading the file through the form on the SQL page (top right corner). To make restoring easier, we suggest you backup individual databases or even individual tables and use the SQL format instead of COPY. [[Category:Databases]] 363f8630d83c60bd45b9c355cb3e36c3c3137b4d 803 800 2019-09-11T02:57:20Z Bert 8 wikitext text/x-wiki You can access your PostgreSQL databases using PHPPgAdmin. This application can be found on https://phppgadmin.ulyssis.org. To login you need to use your PostgreSQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your PostgreSQL password you can get it from your websites configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. You can change your database passwords through our control panel [https://ucc.ulyssis.org/ UCC], but keep in mind to then also change the password in relevant configuration files, or you applications may stop working correctly. == Basic Usage == You can login by clicking on the only server in the left sidebar ''PostgreSQL voor gebruikers, kringen en organisaties''. Once you've logged in, you will see an overview of all your databases. You can then view databases, schemas and tables by clicking on them or navigating through the sidebar. For each table you can view the records, view and change the structure, add records, take backups, etc. Official documentation of all functionality is sadly lacking, but you can still refer to [http://phppgadmin.sourceforge.net/doku.php?id=faq_docs the official documentation] == Making Backups == PHPPgAdmin has an export option which can be used to backup the structure and/or data of databases, schemas and tables, as well as more advanced features such as sequences and functions. When no database, schema or table has been selected, the export tab in the top menu allows to export all databases at the same time. When a specific database or table is selected, that database or table is exported. You can decide whether you wish to export the structure, the data or both, as well as the format and if DROPs need to be included. You can later restore backups by uploading the file through the form on the SQL page (top right corner). To make restoring easier, we suggest you backup individual databases or even individual tables and use the SQL format instead of COPY. [[Category:Databases]] 17e1fceba00bbf75a7af3d88820ce3881c27ef02 0 127 789 2019-09-09T16:39:39Z Bert 8 Created page with "You can access both your MySQL and PostgreSQL databases using Adminer, though not both at the same time. This application can be found on https://adminer.ulyssis.org. To login..." wikitext text/x-wiki You can access both your MySQL and PostgreSQL databases using Adminer, though not both at the same time. This application can be found on https://adminer.ulyssis.org. To login you need to use your MySQL or PostgreSQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your passwords you can get it from your websites configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. To use MySQL, please use the server mysql.ulyssis.org. In case of PostgreSQL, please use pgsql.ulyssis.org. == Basic Usage == When logging in using MySQL, you will see an overview of all your databases. When using PostgreSQL you will see all databases that have been created by all of our users (this is a known problem with Adminer), though you won't be able to view them. You can then view databases and tables. For each table you can view the records, view and change the structure, add records, take backups, etc. Sadly no official documentation is available, though Adminer has a [https://sourceforge.net/p/adminer/discussion/ forum] where you can ask for help. == Taking Backups == At all stages of browsing databases using Adminer you can use the export button in the left sidebar to backup the database(s) or table(s) you're viewing. You can then restore your backup using the import button in the sidebar. To make restoring easier, we suggest however you backup individual databases or even individual tables. [[Category:Databases]] ff82508b0f187977303556cd5bbbd3118e0d594b 795 789 2019-09-10T14:12:47Z Bert 8 wikitext text/x-wiki You can access both your MySQL and PostgreSQL databases using Adminer, though not both at the same time. This application can be found on https://adminer.ulyssis.org. To login you need to use your MySQL or PostgreSQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your passwords you can get it from your websites configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. To use MySQL, please use the server mysql.ulyssis.org. In case of PostgreSQL, please use pgsql.ulyssis.org. == Basic Usage == When logging in using MySQL, you will see an overview of all your databases. When using PostgreSQL you will see all databases that have been created by all of our users (this is a known problem with Adminer), though you won't be able to view them. You can then view databases and tables. For each table you can view the records, view and change the structure, add records, take backups, etc. Sadly no official documentation is available, though Adminer has a [https://sourceforge.net/p/adminer/discussion/ forum] where you can ask for help. == Making Backups == At all stages of browsing databases using Adminer you can use the export button in the left sidebar to backup the database(s) or table(s) you're viewing. You can then restore your backup using the import button in the sidebar. To make restoring easier, we suggest however you backup individual databases or even individual tables. [[Category:Databases]] f8931d703587953c72e2f338f21bb8854c193c30 801 795 2019-09-11T02:23:28Z Bert 8 /* Making Backups */ wikitext text/x-wiki You can access both your MySQL and PostgreSQL databases using Adminer, though not both at the same time. This application can be found on https://adminer.ulyssis.org. To login you need to use your MySQL or PostgreSQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your passwords you can get it from your websites configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. To use MySQL, please use the server mysql.ulyssis.org. In case of PostgreSQL, please use pgsql.ulyssis.org. == Basic Usage == When logging in using MySQL, you will see an overview of all your databases. When using PostgreSQL you will see all databases that have been created by all of our users (this is a known problem with Adminer), though you won't be able to view them. You can then view databases and tables. For each table you can view the records, view and change the structure, add records, take backups, etc. Sadly no official documentation is available, though Adminer has a [https://sourceforge.net/p/adminer/discussion/ forum] where you can ask for help. == Making Backups == Adminer has an export option which can be used to backup the structure and/or data of databases and tables. When no database or table has been selected, the export button in the sidebar allows to export all databases at the same time. When a specific database or table is selected, that database or table is exported. You can specify to save the file, in what format, and whether structures and data should be dropped, truncated or created. You can later restore backups by uploading the file through the form available through the import button in the sidebar. To make restoring easier, we suggest you backup individual databases or even individual tables and use the SQL format. [[Category:Databases]] e363c44646b087a2500b6b2abfac9c873e01bde8 804 801 2019-09-11T02:57:31Z Bert 8 wikitext text/x-wiki You can access both your MySQL and PostgreSQL databases using Adminer, though not both at the same time. This application can be found on https://adminer.ulyssis.org. To login you need to use your MySQL or PostgreSQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your passwords you can get it from your websites configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. You can change your database passwords through our control panel [https://ucc.ulyssis.org/ UCC], but keep in mind to then also change the password in relevant configuration files, or you applications may stop working correctly. To use MySQL, please use the server mysql.ulyssis.org. In case of PostgreSQL, please use pgsql.ulyssis.org. == Basic Usage == When logging in using MySQL, you will see an overview of all your databases. When using PostgreSQL you will see all databases that have been created by all of our users (this is a known problem with Adminer), though you won't be able to view them. You can then view databases and tables. For each table you can view the records, view and change the structure, add records, take backups, etc. Sadly no official documentation is available, though Adminer has a [https://sourceforge.net/p/adminer/discussion/ forum] where you can ask for help. == Making Backups == Adminer has an export option which can be used to backup the structure and/or data of databases and tables. When no database or table has been selected, the export button in the sidebar allows to export all databases at the same time. When a specific database or table is selected, that database or table is exported. You can specify to save the file, in what format, and whether structures and data should be dropped, truncated or created. You can later restore backups by uploading the file through the form available through the import button in the sidebar. To make restoring easier, we suggest you backup individual databases or even individual tables and use the SQL format. [[Category:Databases]] c9af2dff0bbe013597bcc0bf3c08ca3bc84e17a7 0 3 790 690 2019-09-09T16:40:21Z Bert 8 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] * [[Secure file permissions]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Sending email from websites]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] * [[Claiming a port]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] * [[Using PHPPgAdmin]] * [[Using Adminer]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 40ad69341c921c345edf77fa37b84e000b286212 791 790 2019-09-09T16:55:40Z Bert 8 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] * [[Secure file permissions]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Sending email from websites]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] * [[Claiming a port]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up Wordpress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] * [[Using PHPPgAdmin]] * [[Using Adminer]] * [[Making Backups]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ b153d03b37bcab5ac761e81f80fd72b9ba2a277e 0 41 792 708 2019-09-09T16:55:50Z Bert 8 wikitext text/x-wiki ULYSSIS takes backups of all files, databases, settings and repositories 1-4 times a week. These backups can be restored in case of severe server failure or in case of an emergency (if for example a user by mistake deletes all of their site). It is, however, more convenient that users take their own backups when they do experimental things on their account. == A backup of your files == You can use the graphical methods described in [[Accessing your files]] to download a copy of all of your files. This copy, or certain files, can then easily be uploaded again using the same method to restore backups == A backup of your databases == To take a backup of your database you simple use the export function of PHPMyAdmin as described on [[Using PHPMyAdmin]]. [[Category:Files]] [[Category:Databases]] 8dc6ed374e96369b6a4b580aabc93f5e15adac9d 793 792 2019-09-09T16:56:26Z Bert 8 wikitext text/x-wiki ULYSSIS takes backups of all files, databases, settings and repositories 1-4 times a week. These backups can be restored in case of severe server failure or in case of an emergency (if for example a user by mistake deletes all of their site). It is, however, more convenient that users take their own backups when they do experimental things on their account. == A backup of your files == You can use the graphical methods described in [[Accessing your files]] to download a copy of all of your files. This copy, or certain files, can then easily be uploaded again using the same method to restore backups == A backup of your databases == To take a backup of your database you simple use the export function of PHPMyAdmin, PHPPgAdmin and/or Adminer as described on [[Using PHPMyAdmin]], [[Using PHPPgAdmin]] and [[Using Adminer]]. [[Category:Files]] [[Category:Databases]] fb7f6d436327d12d8d1715883c34a27fe98084bf 0 114 805 716 2019-09-21T21:20:20Z Vincenttc 21 /* Delay and limitations */ wikitext text/x-wiki Sending email is fairly similar on most hosting services. ULYSSIS hosting is not too different in that sense. We do use a queueing system to detect accounts that are being abused by malicious actors to send spam. == How? == In PHP and most other programming languages, content management systems (CMS), and frameworks, you can use the buildin email function. This may be referred to with names such as buildin, default, standard, local or sendmail. == Delay and limitations == Because of the large amount of users on our hosting services, security breaches and misconfigurations due to user mismanagement happen from time to time. As many malicious actors focus their efforts on abusing servers with a good reputation for the distribution of spam, it is not uncommon to find several thousands of emails being sent once a problem occurs. To combat this, ULYSSIS hosting delays sending of emails for up to 5 minutes and verifies a certain amount (50) of email is never surpassed. If at any point the level is surpassed, ULYSSIS is notified and can take action, while probable spam is stopped from being transmitted. Therefore it is important to keep a potential delay in time when expecting email from your website, but also not to send vast amount of email all at once. It is in general good practice to spread the transmission of for example an email list with several hundred participants. [[Category:Webserver]] a1dc2e5d63e0bf3f689fa0eb76bdc32e45127182 0 10 806 718 2019-09-28T13:58:47Z Yoa 30 /* Let's Encrypt */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, we have to prepare some folders in our '''home directory''' to store the certificates for '''mydomain.be''' in: mkdir letsencrypt mkdir letsencrypt/mydomain.be Now we download the <code>acme.sh</code> script and make it executable: wget -O https://raw.githubusercontent.com/Neilpang/acme.sh/master/acme.sh chmod +x acme.sh Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be We use the "email@example.com" email address to remind us to renew our certificates. <code>/home/user/myusername/path/to/webroot</code> is the path to the webroot of the domain name. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain -d mydomain.be ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ===Check certificate for common mistakes=== You can check if your certificate will likely be okay with a command-line tool on our shellservers: <kbd>ulyssis-certificate check interestingdomain.be</kbd>. If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] 5695e652054564d2c669b9b1823ac2ab4251eee9 807 806 2019-09-28T13:59:00Z Yoa 30 /* External certificates */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, we have to prepare some folders in our '''home directory''' to store the certificates for '''mydomain.be''' in: mkdir letsencrypt mkdir letsencrypt/mydomain.be Now we download the <code>acme.sh</code> script and make it executable: wget -O https://raw.githubusercontent.com/Neilpang/acme.sh/master/acme.sh chmod +x acme.sh Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be We use the "email@example.com" email address to remind us to renew our certificates. <code>/home/user/myusername/path/to/webroot</code> is the path to the webroot of the domain name. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain -d mydomain.be ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] beba579d09e1e192ed63dc67e0c919ff706076ad 808 807 2019-09-28T13:59:42Z Yoa 30 /* Generating the certificates */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, we download the <code>acme.sh</code> script and make it executable: wget -O https://raw.githubusercontent.com/Neilpang/acme.sh/master/acme.sh chmod +x acme.sh Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be We use the "email@example.com" email address to remind us to renew our certificates. <code>/home/user/myusername/path/to/webroot</code> is the path to the webroot of the domain name. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain -d mydomain.be ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] d0c814ff628f252f811a3d02569a3494acfd4327 810 808 2019-09-29T15:05:35Z Yoa 30 /* Generating the certificates */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, we download the <code>acme.sh</code> script and make it executable: wget https://raw.githubusercontent.com/Neilpang/acme.sh/master/acme.sh chmod +x acme.sh Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be We use the "email@example.com" email address to remind us to renew our certificates. <code>/home/user/myusername/path/to/webroot</code> is the path to the webroot of the domain name. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain -d mydomain.be ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] 8e6f40862637b0d0cab2f91ae96b939a75f78a92 811 810 2019-09-29T15:11:52Z Yoa 30 /* Renewing the certificates */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, we download the <code>acme.sh</code> script and make it executable: wget https://raw.githubusercontent.com/Neilpang/acme.sh/master/acme.sh chmod +x acme.sh Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be We use the "email@example.com" email address to remind us to renew our certificates. <code>/home/user/myusername/path/to/webroot</code> is the path to the webroot of the domain name. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain -d mydomain.be ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] 8b15b9c35f4e75c126f7a8ac962987c717b35c12 812 811 2019-09-30T10:46:02Z Yoa 30 /* Generating the certificates */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, we download the <code>acme.sh</code> script and make it executable: wget https://raw.githubusercontent.com/Neilpang/acme.sh/master/acme.sh chmod +x acme.sh Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be We use the "email@example.com" email address to remind us to renew our certificates. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain -d mydomain.be ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] 644f92f120f06ca4b45676200cb34e695398baa2 813 812 2019-10-01T12:46:19Z Yoa 30 /* Using acme.sh */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, we download the <code>acme.sh</code> script and make it executable: wget https://raw.githubusercontent.com/Neilpang/acme.sh/master/acme.sh chmod +x acme.sh Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be We use the "email@example.com" email address to remind us to renew our certificates. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain -d mydomain.be ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] f26fda3da911962d1b1d347c9053a990473e3aa3 0 72 809 728 2019-09-29T09:18:00Z Tim 25 wikitext text/x-wiki You may want to send e-mail from Hotmail using your @ulyssis.org address, or another domain name that you use for your account. Hotmail allows you to do this by configuring a few settings. Because you should only be able to send mails from an e-mail address you actually own, make sure that you configured receiving mails before starting this process. Hotmail will send a confirmation mail to the provided e-mail address to confirm that you own it. Note that Outlook's SMTP will still add your original address as "Sender" in the mail headers. Depending on the recipient's mail client, he might still see this. If you use a local mail client, you might be able to avoid this by using a custom SMTP server. #Click on the gear icon at the top right and search for '''Connected accounts''' (Dutch: '''Verbonden accounts'''). #On this page, you see the title '''Email aliases''' (Dutch: '''E-mailaliassen''') with a link '''Manage or choose a primary alias''' (Dutch: '''Primaire alias beheren of kiezen''') below. Click it. You will have to log in again to proceed. #Click on '''Add Email''' (Dutch: '''E-mailadres toevoegen''') and choose the second option: '''Add an existing email address as a Microsoft account alias''' (Dutch: '''Een bestaand e-mailadres als een Microsoft-accountalias toevoegen'''). Fill in the e-mail address you want to use to send mail from, and click '''Add alias''' (Dutch: '''Alias toevoegen''') #At this point, you should receive an e-mail on the address you just provided. It will contain a URL to confirm adding the alias. Click it. #At this point, you have confirmed that you are the owner of the e-mail address. Congratulations, you can now use it to send mail! [[Category:Mail]] 5cae8329617ad8d37340859b5912c8b6eb84370d 0 10 814 813 2019-10-01T12:46:32Z Yoa 30 /* Using acme.sh */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, we download the <code>acme.sh</code> script and make it executable: wget https://raw.githubusercontent.com/Neilpang/acme.sh/master/acme.sh chmod +x acme.sh Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be We use the "email@example.com" email address to remind us to renew our certificates. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain -d mydomain.be ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] 072efc95c582ab2ced656fd6330c1bc257f85fbe 815 814 2019-10-01T12:46:39Z Yoa 30 /* Using acme.sh */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, we download the <code>acme.sh</code> script and make it executable: wget https://raw.githubusercontent.com/Neilpang/acme.sh/master/acme.sh chmod +x acme.sh Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be We use the "email@example.com" email address to remind us to renew our certificates. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain -d mydomain.be ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] f26fda3da911962d1b1d347c9053a990473e3aa3 0 5 816 758 2019-10-25T11:42:29Z Bert 8 /* Non-graphical methods */ wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Connecting== ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. If your distribution does not contain an option to connect to a server, you can use [https://filezilla-project.org/ FileZilla], which is completely free. See the instructions under [[Accessing_your_files#Windows|Windows]]. [[File:UbuntuConnectToServer.png]] ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ===Mac=== ''[https://filezilla-project.org/ FileZilla], which was mentioned above, is also available for Mac. To use it, follow [[#Windows|the instructions for Windows]]. You can also opt for [http://cyberduck.io/ Cyberduck], though. In that case, follow the instructions below.'' Download the free and open source program [http://cyberduck.io/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> [[File:maccyberduck3.png]] Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. If you want to connect again later on, you can just click the Bookmarks icon on the top left. Next you click on History. And then you can double click to re-open the connection. ==Using FileZilla== When you connect to a server using FileZilla, the following layout will appear: [[File:Base_layout.png|700px|Right]] As you can see, the local files are located on the left-hand side, while the remote (server) files are located on the right-hand side. File navigation and paths are also present. [[File:Layout.png|700px|Right]] To transfer a file or folder, you can drag and drop it, either from the local side to the remote side, or from the remote side to the local side. These operations represent uploading and downloading respectively. [[File:Transfer.png|700px|Right]] You can also press enter while selecting a file, or double-click a file, to transfer it. [[File:Transfer2.png|700px|Right]] To open a folder, you can double-click it, or press enter while selecting it. [[File:Open.png|700px|Right]] You can delete files or folders by pressing the delete button while selecting them, or by right-clicking and clicking 'delete'. [[File:Delete.png|700px|Right]] To create files or folders remotely, you can right-click the remote window and click 'create directory' or 'create new file'. [[File:Create_directory.png|700px|Right]] [[File:Create_file.png|700px|Right]] As you can see, the menu has some more interesting options, for example 'rename' or 'view/edit'. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): scp file.txt username@ssh1.ulyssis.org:/home/user/username For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. [[Category:Files]] [[Category:Shell]] c2a8c5e2fed46677cafb4c1663f2206850e650e3 10 128 817 2019-10-25T19:52:29Z Bert 8 Created page with "<div class='mywarningbox'> <b>{{{1}}}</b><br /> {{{2}}} </div> <noinclude> == Usage == <nowiki>{{warning|title|text}}</nowiki> </noinclude>" wikitext text/x-wiki <div class='mywarningbox'> <b>{{{1}}}</b><br /> {{{2}}} </div> <noinclude> == Usage == <nowiki>{{warning|title|text}}</nowiki> </noinclude> 328fd59b97bf4c81c416c03e08ecb60e13feae37 819 817 2019-10-25T20:20:37Z Bert 8 wikitext text/x-wiki <languages/> <onlyinclude>{{#switch:<translate></translate> | = {{#if: {{{msg|{{{1|}}}}}}|<table cellspacing="0" cellpadding="0" border="0" style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6"><tr><td nowrap="nowrap" valign="top">}}<span style="position: relative; top: -2px;">[[File:OOjs_UI_icon_notice-destructive.svg|18px|<translate><!--T:1--> Warning</translate>|link=]]</span> '''<translate><!--T:2--> Warning:</translate>''' {{#if: {{{msg|{{{1|}}}}}}|</td><td valign="top" style="padding-{{dir|{{pagelang}}|right|left}}:0.5em;">{{{msg|{{{1|}}}}}}</td></tr></table>}} | #default= {{#invoke:Template translation|renderTranslatedTemplate|template=Template:Warning|noshift=1}} }}</onlyinclude> {{Documentation|content= <translate> == Usage == <!--T:3--> <!--T:4--> This template has two possible usages: <!--T:5--> # Will have the text flow below when the warning text is too long</translate> <translate> <!--T:6--> # Uses a table to indent the text. === Method 1 === <!--T:7--> <!--T:8--> The following displays the warning icon and the word "Warning:".</translate> <translate> <!--T:17--> You can follow this with whatever text/images/markup you like. <!--T:9--> Wiki Code: </translate> <nowiki>{{warning}}</nowiki> <translate><!--T:10--> Don't do that!</translate> {{warning}} <translate><!--T:11--> Don't do that!</translate> <translate> === Method 2 === <!--T:12--> <!--T:13--> The following includes the text passed to the template, and uses a table to stop the text flowing round the icon. <!--T:14--> Wiki Code: </translate> <nowiki>{{warning|1=</nowiki><translate><!--T:15--> Here is a long warning, which is sufficiently wordy to run onto a second line (unless you have a really large screen!), which would normally cause it to wrap round the icon, but because we passed it as a parameter it keeps its left alignment straight.</translate><nowiki>}}</nowiki> {{warning|1=<translate><!--T:16--> Here is a long warning, which is sufficiently wordy to run onto a second line (unless you have a really large screen!), which would normally cause it to wrap round the icon, but because we passed it as a parameter it keeps its left alignment straight.</translate>}} }} [[Category:Warning templates{{#translation:}}|{{PAGENAME}}]] 4dc1467a2ab812ebf97f604fff0f1a7805b53deb 820 819 2019-10-25T20:21:46Z Bert 8 wikitext text/x-wiki <onlyinclude>{{#switch:<translate></translate> | = {{#if: {{{msg|{{{1|}}}}}}|<table cellspacing="0" cellpadding="0" border="0" style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6"><tr><td nowrap="nowrap" valign="top">}}<span style="position: relative; top: -2px;">[[File:OOjs_UI_icon_notice-destructive.svg|18px|<translate><!--T:1--> Warning</translate>|link=]]</span> '''<translate><!--T:2--> Warning:</translate>''' {{#if: {{{msg|{{{1|}}}}}}|</td><td valign="top" style="padding-{{dir|{{pagelang}}|right|left}}:0.5em;">{{{msg|{{{1|}}}}}}</td></tr></table>}} | #default= {{#invoke:Template translation|renderTranslatedTemplate|template=Template:Warning|noshift=1}} }}</onlyinclude> 0901328547379039e4237e895bd0afd512b76914 821 820 2019-10-25T20:22:30Z Bert 8 wikitext text/x-wiki {{#switch:<translate></translate> | = {{#if: {{{msg|{{{1|}}}}}}|<table cellspacing="0" cellpadding="0" border="0" style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6"><tr><td nowrap="nowrap" valign="top">}}<span style="position: relative; top: -2px;">[[File:OOjs_UI_icon_notice-destructive.svg|18px|<translate><!--T:1--> Warning</translate>|link=]]</span> '''<translate><!--T:2--> Warning:</translate>''' {{#if: {{{msg|{{{1|}}}}}}|</td><td valign="top" style="padding-{{dir|{{pagelang}}|right|left}}:0.5em;">{{{msg|{{{1|}}}}}}</td></tr></table>}} | #default= {{#invoke:Template translation|renderTranslatedTemplate|template=Template:Warning|noshift=1}} }} ee2cfa709b8510688661018d4d0b32b4539f1bdd 822 821 2019-10-25T20:22:55Z Bert 8 wikitext text/x-wiki {{{msg|{{{1|}}}}}}|<table cellspacing="0" cellpadding="0" border="0" style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6"><tr><td nowrap="nowrap" valign="top">}}<span style="position: relative; top: -2px;">[[File:OOjs_UI_icon_notice-destructive.svg|18px|<translate><!--T:1--> Warning</translate>|link=]]</span> '''<translate><!--T:2--> Warning:</translate>''' {{#if: {{{msg|{{{1|}}}}}}|</td><td valign="top" style="padding-{{dir|{{pagelang}}|right|left}}:0.5em;">{{{msg|{{{1|}}}}}}</td></tr></table>}} 3ade37cda3b2caaff6d2fadfeb04640c0ca26eba 823 822 2019-10-25T20:23:34Z Bert 8 wikitext text/x-wiki <table cellspacing="0" cellpadding="0" border="0" style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6"><tr><td nowrap="nowrap" valign="top">}}<span style="position: relative; top: -2px;">[[File:OOjs_UI_icon_notice-destructive.svg|18px|<translate><!--T:1--> Warning</translate>|link=]]</span> '''<translate><!--T:2--> Warning:</translate>''' {{#if: {{{msg|{{{1|}}}}}}|</td><td valign="top" style="padding-{{dir|{{pagelang}}|right|left}}:0.5em;">{{{msg|{{{1|}}}}}}</td></tr></table>}} 3a2e4dc44ea3e4f4ecbeeca0f60a17fa75722faf 824 823 2019-10-25T20:24:28Z Bert 8 wikitext text/x-wiki <table cellspacing="0" cellpadding="0" border="0" style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6"><tr><td nowrap="nowrap" valign="top">}}<span style="position: relative; top: -2px;">[[File:OOjs_UI_icon_notice-destructive.svg|18px|Warning|link=]]</span> '''<translate><!--T:2--> Warning:</translate>''' {{#if: {{{msg|{{{1|}}}}}}|</td><td valign="top" style="padding-{{dir|{{pagelang}}|right|left}}:0.5em;">{{{msg|{{{1|}}}}}}</td></tr></table> 6ceb1d67d4b7d60d5f7ef2b8da32f94f11dc90fb 825 824 2019-10-25T20:24:44Z Bert 8 wikitext text/x-wiki <table cellspacing="0" cellpadding="0" border="0" style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6"><tr><td nowrap="nowrap" valign="top">}}<span style="position: relative; top: -2px;">[[File:OOjs_UI_icon_notice-destructive.svg|18px|Warning|link=]]</span> '''<!--T:2--> Warning:''' {{#if: {{{msg|{{{1|}}}}}}|</td><td valign="top" style="padding-{{dir|{{pagelang}}|right|left}}:0.5em;">{{{msg|{{{1|}}}}}}</td></tr></table> 53cbc2d96e01ae9509e9d4e31522b9a31a4d48ed 826 825 2019-10-25T20:25:44Z Bert 8 wikitext text/x-wiki <table cellspacing="0" cellpadding="0" border="0" style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6"><tr><td nowrap="nowrap" valign="top"><span style="position: relative; top: -2px;">[[File:OOjs_UI_icon_notice-destructive.svg|18px|Warning|link=]]</span> </td><td valign="top">{{{1}}}</td></tr></table> 25d75172c5491e98d4410a69e199e2bf7a92e00f 827 826 2019-10-25T20:26:10Z Bert 8 wikitext text/x-wiki <table cellspacing="0" cellpadding="0" border="0" style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6"><tr><td nowrap="nowrap" valign="top"><span style="position: relative; top: -2px;">[[File:OOjs_UI_icon_notice-destructive.svg|18px|Warning|link=]]</span>{{{1}}}</td><td valign="top">{{{2}}}</td></tr></table> 8f7278d1ea339f557b3297eab48f68b33ee85696 828 827 2019-10-25T20:26:26Z Bert 8 wikitext text/x-wiki <table cellspacing="0" cellpadding="0" border="0" style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6"><tr><td nowrap="nowrap" valign="top"><span style="position: relative; top: -2px;">[[File:OOjs_UI_icon_notice-destructive.svg|18px|Warning|link=]]</span>{{{1}}}</td><td>{{{2}}}</td></tr></table> <noinclude> b9f0759d923863521f515bd6633e1711674ef8b3 829 828 2019-10-25T20:26:54Z Bert 8 wikitext text/x-wiki <table cellspacing="0" cellpadding="0" border="0" style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6"><tr><td nowrap="nowrap" valign="top"><span style="position: relative; top: -2px;">[[File:OOjs_UI_icon_notice-destructive.svg|18px|Warning|link=]]</span>{{{1}}}</td><td>{{{2}}}</td></tr></table> <noinclude> {{warning|testtitle|dit is tekst}} 43dbbac85591f0f95073847191664fc7e833f8a1 830 829 2019-10-25T20:54:03Z Bert 8 wikitext text/x-wiki <table cellspacing="0" cellpadding="0" border="0" style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6"> <tr> <td nowrap="nowrap" valign="top"><span style="position: relative; top: -2px;">[[File:OOjs_UI_icon_notice-destructive.svg|18px|Warning|link=]]</span>{{{1}}}</td> <td>{{{2}}}</td> </tr> </table> <noinclude> {{warning|testtitle|dit is tekst}} 0b3b2ccf474f4b04fbabdfaf4eb2989e39ca5ae1 831 830 2019-10-25T20:54:19Z Bert 8 wikitext text/x-wiki <table cellspacing="0" cellpadding="0" border="0" style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6"> <tr> <td nowrap="nowrap"><span style="position: relative; top: -2px;">[[File:OOjs_UI_icon_notice-destructive.svg|18px|Warning|link=]]</span>{{{1}}}</td> <td>{{{2}}}</td> </tr> </table> <noinclude> {{warning|testtitle|dit is tekst}} 59eca0373560eb20be7c241bad05e62382be6cad 832 831 2019-10-25T20:54:46Z Bert 8 wikitext text/x-wiki <table cellspacing="0" cellpadding="0" border="0" style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6"> <tr> <td><span style="position: relative; top: -2px;">[[File:OOjs_UI_icon_notice-destructive.svg|18px|Warning|link=]]</span>{{{1}}}</td> <td>{{{2}}}</td> </tr> </table> <noinclude> {{warning|testtitle|dit is tekst}} ad3dd59a64e7623890a81131cfbbe48bc05be044 833 832 2019-10-25T20:55:17Z Bert 8 wikitext text/x-wiki <table cellspacing="0" cellpadding="0" border="0" style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6"> <tr> <td><span style="position: relative; top: -2px;">[[File:OOjs_UI_icon_notice-destructive.svg|18px|Warning|link=]]</span></td> <td>{{{1}}}</td> <td>{{{2}}}</td> </tr> </table> <noinclude> {{warning|testtitle|dit is tekst}} 7d8bf1f24252bb8f8ccb8fb84de1a8f127fcc087 834 833 2019-10-25T20:55:41Z Bert 8 wikitext text/x-wiki <table cellspacing="0" cellpadding="0" border="0" style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6"> <tr> <td><span>[[File:OOjs_UI_icon_notice-destructive.svg|18px|Warning|link=]]</span></td> <td>{{{1}}}</td> <td>{{{2}}}</td> </tr> </table> <noinclude> {{warning|testtitle|dit is tekst}} 3db1e9ed6f9b8bd6cde52715a0c358d7f7ab72d8 835 834 2019-10-25T20:59:51Z Bert 8 wikitext text/x-wiki <table cellspacing="0" cellpadding="0" border="0" style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6"> <tr> <td><span>[[File:OOjs_UI_icon_notice-destructive.svg|18px|Warning|link=]]</span></td> <td><b>{{{1}}}<b></td> </tr> <tr> <td colspan="2">{{{2}}}</td> </tr> </table> <noinclude> {{warning|testtitle|dit is tekst}} 676db8cd0006f02965b22c78cddeb75d652313d7 836 835 2019-10-25T21:00:17Z Bert 8 wikitext text/x-wiki <table cellspacing="0" cellpadding="0" border="0" style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6"> <tr> <td><span>[[File:OOjs_UI_icon_notice-destructive.svg|18px|Warning|link=]]</span></td> <td style="margin-left: 1em"><b>{{{1}}}<b></td> </tr> <tr> <td colspan="2">{{{2}}}</td> </tr> </table> <noinclude> {{warning|testtitle|dit is tekst}} 292fd430e6a9cac0cc81fc673565fc7ef473c331 837 836 2019-10-25T21:00:32Z Bert 8 wikitext text/x-wiki <table cellspacing="0" cellpadding="0" border="0" style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6"> <tr> <td><span>[[File:OOjs_UI_icon_notice-destructive.svg|18px|Warning|link=]]</span></td> <td style="padding-left: 1em"><b>{{{1}}}<b></td> </tr> <tr> <td colspan="2">{{{2}}}</td> </tr> </table> <noinclude> {{warning|testtitle|dit is tekst}} 0824ca1c51ceb1c071b476ee306374c1b4594dc1 838 837 2019-10-25T21:01:01Z Bert 8 wikitext text/x-wiki <table cellspacing="0" cellpadding="0" border="0" style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6"> <tr> <td><span>[[File:OOjs_UI_icon_notice-destructive.svg|18px|Warning|link=]]</span></td> <td style="padding-left: 0.7em"><b>{{{1}}}<b></td> </tr> <tr> <td colspan="2">{{{2}}}</td> </tr> </table> <noinclude> {{warning|testtitle|dit is tekst}} d374090d9c5a5b042202ad5c8504838279232ca6 839 838 2019-10-25T21:01:52Z Bert 8 wikitext text/x-wiki <table cellspacing="0" cellpadding="0" border="0" style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6"> <tr> <td><span>[[File:OOjs_UI_icon_notice-destructive.svg|18px|Warning|link=]]</span></td> <td style="padding-left: 0.7em"><b>{{{1}}}<b></td> </tr> <tr> <td colspan="2">{{{2}}}</td> </tr> </table> <noinclude> {{warning|Warning!|Don't use this warning too often, otherwise it might just miss its effect and that's no use!}} 03fcbf5c911cdca5dfc7037c1083c053f7271919 840 839 2019-10-25T21:03:24Z Bert 8 wikitext text/x-wiki <table cellspacing="0" cellpadding="0" border="0" style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6"> <tr> <td><span>[[File:OOjs_UI_icon_notice-destructive.svg|18px|Warning|link=]]</span><p style="padding-left: 0.7em"><b>{{{1}}}<b></p></td> </tr> <tr> <td>{{{2}}}</td> </tr> </table> <noinclude> {{warning|Warning!|Don't use this warning too often, otherwise it might just miss its effect and that's no use!}} de24656a8dee2767c7adf23011c8bddc4d6b0f32 841 840 2019-10-25T21:04:33Z Bert 8 wikitext text/x-wiki <div style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6"> <p><span>[[File:OOjs_UI_icon_notice-destructive.svg|18px|Warning|link=]]</span><span style="padding-left: 0.7em"><b>{{{1}}}<b></span></p> <p>{{{2}}}</p> </div> <noinclude> {{warning|Warning!|Don't use this warning too often, otherwise it might just miss its effect and that's no use!}} a614816f6f64e12babb3279eba0d5ea5f0537b4b 842 841 2019-10-25T21:05:16Z Bert 8 wikitext text/x-wiki <div style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6"> <p><span>[[File:OOjs_UI_icon_notice-destructive.svg|18px|Warning|link=]]</span><span style="padding-left: 0.7em"><b>{{{1}}}</b></span></p> <p>{{{2}}}</p> </div> <noinclude> {{warning|Warning!|Don't use this warning too often, otherwise it might just miss its effect and that's no use!}} 52150d9ddee195fc7dc22aafcb63beea692e8bf5 843 842 2019-10-25T21:06:07Z Bert 8 wikitext text/x-wiki <div style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6"> <p style="margin-bottom: 0;"><span>[[File:OOjs_UI_icon_notice-destructive.svg|18px|Warning|link=]]</span><span style="padding-left: 0.7em"><b>{{{1}}}</b></span></p> <p>{{{2}}}</p> </div> <noinclude> {{warning|Warning!|Don't use this warning too often, otherwise it might just miss its effect and that's no use!}} 323be1241926bb1235f5375674e79d2134e24af0 844 843 2019-10-25T21:06:25Z Bert 8 wikitext text/x-wiki <div style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6"> <p style="margin-bottom: 0;"><span>[[File:OOjs_UI_icon_notice-destructive.svg|18px|Warning|link=]]</span><span style="padding-left: 0.7em"><b>{{{1}}}</b></span></p> <p style="margin-bottom: 0;">{{{2}}}</p> </div> <noinclude> {{warning|Warning!|Don't use this warning too often, otherwise it might just miss its effect and that's no use!}} 0278c525c376ee3e518978ad50faf7e35533a2b7 845 844 2019-10-25T21:07:27Z Bert 8 wikitext text/x-wiki <div style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6; border: 1px solid #fb9995;"> <p style="margin-bottom: 0;"><span>[[File:OOjs_UI_icon_notice-destructive.svg|18px|Warning|link=]]</span><span style="padding-left: 0.7em"><b>{{{1}}}</b></span></p> <p style="margin-bottom: 0;">{{{2}}}</p> </div> <noinclude> {{warning|Warning!|Don't use this warning too often, otherwise it might just miss its effect and that's no use!}} a3f729545af1499237c394295ab75b5cffab4a3b 846 845 2019-10-25T21:07:56Z Bert 8 wikitext text/x-wiki <div style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6; border: 1px solid #fb9995;"> <p style="margin-bottom: 0;"><span>[[File:OOjs_UI_icon_notice-destructive.svg|18px|Warning|link=]]</span><span style="padding-left: 0.7em"><b>{{{1}}}</b></span></p> <p style="margin-bottom: 0;">{{{2}}}</p> </div> <noinclude> == Usage == <nowiki>{{warning|Warning!|Don't use this warning too often, otherwise it might just miss its effect and that's no use!}}</nowiki> {{warning|Warning!|Don't use this warning too often, otherwise it might just miss its effect and that's no use!}} 9117b038eb5642dba2b16ba54f0de3fa0dc48535 854 846 2019-10-26T00:30:12Z Bert 8 wikitext text/x-wiki <div style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6; border: 1px solid #fb9995; margin-bottom: 0;"> <p style="margin-bottom: 0;"><span>[[File:OOjs_UI_icon_notice-destructive.svg|18px|Warning|link=]]</span><span style="padding-left: 0.7em"><b>{{{1}}}</b></span></p> <p style="margin-bottom: 0;">{{{2}}}</p> </div> <noinclude> == Usage == <nowiki>{{warning|Warning!|Don't use this warning too often, otherwise it might just miss its effect and that's no use!}}</nowiki> {{warning|Warning!|Don't use this warning too often, otherwise it might just miss its effect and that's no use!}} 48ba75a726f38a4dc269ffccafdb9ae4334a4407 855 854 2019-10-26T00:30:51Z Bert 8 wikitext text/x-wiki <div style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6; border: 1px solid #fb9995;"> <p style="margin-bottom: 0;"><span>[[File:OOjs_UI_icon_notice-destructive.svg|18px|Warning|link=]]</span><span style="padding-left: 0.7em"><b>{{{1}}}</b></span></p> <p style="margin-bottom: 0;">{{{2}}}</p> </div> <noinclude> == Usage == <nowiki>{{warning|Warning!|Don't use this warning too often, otherwise it might just miss its effect and that's no use!}}</nowiki> {{warning|Warning!|Don't use this warning too often, otherwise it might just miss its effect and that's no use!}} 9117b038eb5642dba2b16ba54f0de3fa0dc48535 857 855 2019-10-26T00:31:57Z Bert 8 wikitext text/x-wiki <div style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6; border: 1px solid #fb9995;"> <p style="margin-bottom: 0;"><span>[[File:OOjs_UI_icon_notice-destructive.svg|20px|Warning|link=]]</span><span style="padding-left: 0.7em"><b>{{{1}}}</b></span></p> <p style="margin-bottom: 0;">{{{2}}}</p> </div> <noinclude> == Usage == <nowiki>{{warning|Warning!|Don't use this warning too often, otherwise it might just miss its effect and that's no use!}}</nowiki> {{warning|Warning!|Don't use this warning too often, otherwise it might just miss its effect and that's no use!}} 24f6cad69a629a5b5660c090639c0ffc55a2a420 858 857 2019-10-26T00:32:13Z Bert 8 wikitext text/x-wiki <div style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6; border: 1px solid #fb9995;"> <p style="margin-bottom: 0;"><span>[[File:OOjs_UI_icon_notice-destructive.svg||Warning|link=]]</span><span style="padding-left: 0.7em"><b>{{{1}}}</b></span></p> <p style="margin-bottom: 0;">{{{2}}}</p> </div> <noinclude> == Usage == <nowiki>{{warning|Warning!|Don't use this warning too often, otherwise it might just miss its effect and that's no use!}}</nowiki> {{warning|Warning!|Don't use this warning too often, otherwise it might just miss its effect and that's no use!}} 454e36051d829f12b3e8b967f04f4d696cf5cc13 860 858 2019-10-26T00:35:29Z Bert 8 wikitext text/x-wiki <div style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6; border: 1px solid #fb9995;"> <p style="margin-bottom: 0;"><span>[[File:OOjs_UI_icon_notice-destructive.svg|18px|Warning|link=]]</span><span style="padding-left: 0.7em"><b>{{{1}}}</b></span></p> <p style="margin-bottom: 0;">{{{2}}}</p> </div> <noinclude> == Usage == <nowiki>{{warning|Warning!|Don't use this warning too often, otherwise it might just miss its effect and that's no use!}}</nowiki> {{warning|Warning!|Don't use this warning too often, otherwise it might just miss its effect and that's no use!}} 9117b038eb5642dba2b16ba54f0de3fa0dc48535 6 129 818 2019-10-25T20:19:48Z Bert 8 Copyright © 2011–2019 OOjs UI Team and other contributors Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction... wikitext text/x-wiki == Summary == Copyright © 2011–2019 OOjs UI Team and other contributors Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. The Software is provided "as is", without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and noninfringement. In no event shall the authors or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the Software or the use or other dealings in the Software. 0f2760bc033726dff025ae610bd6534ffd4e0541 859 818 2019-10-26T00:35:07Z Bert 8 Bert uploaded a new version of [[File:OOjs UI icon notice-destructive.svg]] wikitext text/x-wiki == Summary == Copyright © 2011–2019 OOjs UI Team and other contributors Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. The Software is provided "as is", without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and noninfringement. In no event shall the authors or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the Software or the use or other dealings in the Software. 0f2760bc033726dff025ae610bd6534ffd4e0541 10 130 847 2019-10-25T21:10:59Z Bert 8 Created page with "<div style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6; border: 1px solid #fb9995;"> <p style="margin-bottom: 0;"><span>File:OOjs_UI..." wikitext text/x-wiki <div style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6; border: 1px solid #fb9995;"> <p style="margin-bottom: 0;"><span>[[File:OOjs_UI_icon_notice-destructive.svg|18px|Warning|link=]]</span><span style="padding-left: 0.7em"><b>{{{1}}}</b></span></p> <p style="margin-bottom: 0;">{{{2}}}</p> </div> <noinclude> == Usage == <nowiki>{{notice|Caution!|Don't use this warning too often, otherwise it might just miss its effect and that's no use!}}</nowiki> {{notice|Caution!|Don't use this warning too often, otherwise it might just miss its effect and that's no use!}} aed835687b1d3bd4ece5264393614cb3df435f43 849 847 2019-10-25T21:33:08Z Bert 8 wikitext text/x-wiki <div style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6; border: 1px solid #fb9995;"> <p style="margin-bottom: 0;"><span>[[File:Ambox warning yellow.svg |18px|Notice|link=]]</span><span style="padding-left: 0.7em"><b>{{{1}}}</b></span></p> <p style="margin-bottom: 0;">{{{2}}}</p> </div> <noinclude> == Usage == <nowiki>{{notice|Caution!|Don't use this warning too often, otherwise it might just miss its effect and that's no use!}}</nowiki> {{notice|Caution!|Don't use this warning too often, otherwise it might just miss its effect and that's no use!}} adb6d139dc095b3437981f4d8c5fec21449e3752 850 849 2019-10-25T21:33:23Z Bert 8 wikitext text/x-wiki <div style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #fee7e6; border: 1px solid #fb9995;"> <p style="margin-bottom: 0;"><span>[[File:Ambox_warning_yellow.svg|18px|Notice|link=]]</span><span style="padding-left: 0.7em"><b>{{{1}}}</b></span></p> <p style="margin-bottom: 0;">{{{2}}}</p> </div> <noinclude> == Usage == <nowiki>{{notice|Caution!|Don't use this warning too often, otherwise it might just miss its effect and that's no use!}}</nowiki> {{notice|Caution!|Don't use this warning too often, otherwise it might just miss its effect and that's no use!}} bfd6375cf224ddf9bd0d9baad8b5e0388f48ae23 851 850 2019-10-25T21:40:36Z Bert 8 wikitext text/x-wiki <div style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #ffffdd; border: 1px solid #f7df92;"> <p style="margin-bottom: 0;"><span>[[File:Ambox_warning_yellow.svg|18px|Notice|link=]]</span><span style="padding-left: 0.7em"><b>{{{1}}}</b></span></p> <p style="margin-bottom: 0;">{{{2}}}</p> </div> <noinclude> == Usage == <nowiki>{{notice|Caution!|Don't use this warning too often, otherwise it might just miss its effect and that's no use!}}</nowiki> {{notice|Caution!|Don't use this warning too often, otherwise it might just miss its effect and that's no use!}} c49582938cf057554835f2a51a6bce62826c5d1b 6 131 848 2019-10-25T21:32:48Z Bert 8 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 37 852 712 2019-10-26T00:29:16Z Bert 8 /* FastCGI */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <syntaxhighlight lang="apache">Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</syntaxhighlight> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' Do not place sensitive files inside the web accessible folder.Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.</div> {{warning|Warning!|Do not place sensitive files inside the web accessible folder.Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.}} It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [[Managing_Cron_jobs | cronjob]] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than were it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> Or, for Python 3: <pre>virtualenv ~/.venv --python=python3</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <syntaxhighlight lang="python">#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </syntaxhighlight> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [http://flask.pocoo.org/docs/0.10/deploying/fastcgi/ Flask documentation for FastCGI] [[Category:Webserver]] 57d2e034c8bcc006179503d1d3fc73d98ce645a4 853 852 2019-10-26T00:29:42Z Bert 8 wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <syntaxhighlight lang="apache">Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</syntaxhighlight> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. {{warning|Warning!|Do not place sensitive files inside the web accessible folder.Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.}} It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [[Managing_Cron_jobs | cronjob]] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than were it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> Or, for Python 3: <pre>virtualenv ~/.venv --python=python3</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <syntaxhighlight lang="python">#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </syntaxhighlight> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [http://flask.pocoo.org/docs/0.10/deploying/fastcgi/ Flask documentation for FastCGI] [[Category:Webserver]] ab804e73672dfe3590e6780bdc5958fd6fea3ecc 856 853 2019-10-26T00:31:19Z Bert 8 /* FastCGI */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <syntaxhighlight lang="apache">Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</syntaxhighlight> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. {{warning|Warning!|Do not place sensitive files inside the web accessible folder.Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.}} It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [[Managing_Cron_jobs | cronjob]] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than were it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> Or, for Python 3: <pre>virtualenv ~/.venv --python=python3</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <syntaxhighlight lang="python">#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </syntaxhighlight> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [http://flask.pocoo.org/docs/0.10/deploying/fastcgi/ Flask documentation for FastCGI] [[Category:Webserver]] dc8f59f5321e1e0c80ec09073ab49b2575a4f934 0 36 861 757 2019-10-26T00:37:08Z Bert 8 /* Non-graphical methods */ wikitext text/x-wiki ULYSSIS doesn't support ftp, because it is insecure. However, we support sftp (ftp over ssh). This works similar as ssh. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Non-graphical methods== The most common way to transfer files is with a terminal by using the <code>scp</code> command. Copying file to host: scp SourceFile user@host:directory/TargetFile Copying file from host: scp user@host:directory/SourceFile TargetFile scp -r user@host:directory/SourceFolder TargetFolder You don't need to use the full path to your file. You may you the relative path, starting from your home directory. For example: scp index.html user@ssh1.ulyssis.org:www/index.html ==Graphical methods== The graphical methods are explained in [[Accessing your files]]. [[Category:Files]] [[Category:Shell]] 021084c3d0b44582dffa7a2bdd4ec7fbf22af98f 0 46 863 703 2019-10-26T00:38:32Z Bert 8 wikitext text/x-wiki If you stumbled upon this question, don't worry! You don't have to (and can't) make an empty transfer. [[Category:Account]] e46694ebbf29ba3c63ec170c74d0eab51414ff4f 0 44 864 711 2019-10-26T00:39:01Z Bert 8 /* Troubleshooting */ wikitext text/x-wiki = Location of your files = All the files you want to provide via the web browser must reside in a directory named "www" in your homefolder. Within that folder you can organise your data in sub directories. For more information about accessing your files is available [https://docs.ulyssis.org/Accessing_your_files here]. = Accessing your website = Your webspace is accessible on following url's (with username your username): * http://username.studentenweb.org * http://username.ulyssis.be If you have a domainname like yourname.be, you can link it with our webserver. For more information on this subject, see the [https://docs.ulyssis.org/Adding_domain_names domainnames documentation]. = Troubleshooting = I keep getting an "HTTP Error 403: permission denied" when accessing my website. Try changing the permissions of your www-directory. Log in to a ULYSSIS shell machine and type: chmod o+x ~ chmod o+rx ~/www [[Category:Webserver]] 9f4cd91c6fa22125d13a28d2d4b3a6328aa6c792 0 11 865 717 2019-10-26T00:41:58Z Bert 8 wikitext text/x-wiki By default, your website is accessible at the following URLs: * http://''username''.ulyssis.be * http://''username''.studentenweb.org Where ''username'' is your ULYSSIS user name. If you wish, you can also register another domain name. ULYSSIS isn't a domain name registrar, so you'll have to use an external registrar. For example, you can find a list of all registrars for .be at [http://dns.be dns.be]. {{notice|Caution!|Please don't configure your domain to use ns4.ulyssis.student.kuleuven.be, not only will it not work, it may result in unpredictable behaviour.}} If you have registered your own domain and you want to use it with your ULYSSIS account, you need to: # Point your domain name to the following ULYSSIS nameservers: ## ns.ulyssis.student.kuleuven.be ## ns3.ulyssis.student.kuleuven.be ## Optionally: ns2.ulyssis.student.kuleuven.be # Mail us at ulyssis@ulyssis.org, with the following details: ## Your ULYSSIS username ## The domain name you registered ## The directory that you want the domain to point at. This could be your <code>www</code> folder, but any other folder within your home directory is possible. ## Whether you want to receive e-mail at that domain name via ULYSSIS. Note that we need to request this with ICTS, so this will take a while. Please do keep in mind that, just like any change to an account, this can only be requested by the account holder. You can find more information about DNS at http://en.wikipedia.org/wiki/Domain_Name_System. [[Category:Webserver]] c0cb2cffb7c2554765b9c0299aca0fb7b3f560da 866 865 2019-10-26T00:42:08Z Bert 8 wikitext text/x-wiki By default, your website is accessible at the following URLs: * http://''username''.ulyssis.be * http://''username''.studentenweb.org Where ''username'' is your ULYSSIS user name. If you wish, you can also register another domain name. ULYSSIS isn't a domain name registrar, so you'll have to use an external registrar. For example, you can find a list of all registrars for .be at [http://dns.be dns.be]. {{notice|Caution!|Please don't configure your domain to use ns4.ulyssis.student.kuleuven.be, not only will it not work, it may result in unpredictable behaviour.}} If you have registered your own domain and you want to use it with your ULYSSIS account, you need to: # Point your domain name to the following ULYSSIS nameservers: ## ns.ulyssis.student.kuleuven.be ## ns3.ulyssis.student.kuleuven.be ## Optionally: ns2.ulyssis.student.kuleuven.be # Mail us at ulyssis@ulyssis.org, with the following details: ## Your ULYSSIS username ## The domain name you registered ## The directory that you want the domain to point at. This could be your <code>www</code> folder, but any other folder within your home directory is possible. ## Whether you want to receive e-mail at that domain name via ULYSSIS. Note that we need to request this with ICTS, so this will take a while. Please do keep in mind that, just like any change to an account, this can only be requested by the account holder. You can find more information about DNS at http://en.wikipedia.org/wiki/Domain_Name_System. [[Category:Webserver]] 8b98d633037cde805460d392327868d385e997fc 0 10 867 815 2019-10-26T00:43:08Z Bert 8 wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. =Requesting SSL from the KU Leuven= The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, we download the <code>acme.sh</code> script and make it executable: wget https://raw.githubusercontent.com/Neilpang/acme.sh/master/acme.sh chmod +x acme.sh Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be We use the "email@example.com" email address to remind us to renew our certificates. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain -d mydomain.be ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] e9696a07558888c7667082226d25f5c16c751618 868 867 2019-10-26T00:43:19Z Bert 8 wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, we download the <code>acme.sh</code> script and make it executable: wget https://raw.githubusercontent.com/Neilpang/acme.sh/master/acme.sh chmod +x acme.sh Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be We use the "email@example.com" email address to remind us to renew our certificates. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain -d mydomain.be ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] f26fda3da911962d1b1d347c9053a990473e3aa3 0 17 869 730 2019-10-26T00:45:30Z Bert 8 wikitext text/x-wiki <p>You can use our shell-servers to forward mails from your KULeuven mailbox to an email provider of your choice (e.g. GMail).</p> {{warning|Warning!|DOING THIS IS ENTIRELY ON YOUR OWN RISK. ULYSSIS CANNOT BE HELD RESPONSIBLE FOR LOST/DELAY MAILS. BY HAVING OUR SERVERS FORWARD YOUR KULEUVEN MAIL, YOU TAKE FULL RESPONSIBILITY.}} <p>This tutorial is based on http://ronin.ulyssis.be/files/kulmail_gmail2.txt</p> <p>We wrote a script that configures everything automatically. To use it, log in on one of our shell servers and execute the following commands:</p> <ul> <li>wget ftp://ftp.ulyssis.org/kulforward/kulforwardsetup.sh</li> <li>chmod u+x kulforwardsetup.sh</li> <li>./kulforwardsetup.sh</li> <li>Follow the instructions on the screen.</li> </ul> <p>Alternatively, you can configure everything yourself. Below we briefly explain how to do this.</p> <ul> <li>Create a directory to save the SSL certificates:<br />mkdir .certs</li> <li>Put the necessary certificates in the .certs directory:<br />cd .certs<br />wget ftp://ftp.ulyssis.org/kulforward/imapkul.pem<br />wget ftp://ftp.ulyssis.org/kulforward/usertrust.pem<br />cp /etc/ssl/certs/AddTrust_External_Root.pem .<br />cd </li> <li>Rehash them:<br />c_rehash ~/.certs/</li> <li>Create the fetchmail configuration file with your favourite text editor and enter the confiration details:<br /> $login = your KULeuven login (e.g. s0123456)<br /> $pass = your KULeuven password<br /> $mail = the email address to forward your KULeuven mail to (TRIPLECHECK IT!!)<br /> keep = "" (delete forwarded mails from your KULeuven mailbox) or "keep" (keep forwarded emails)<br /> set daemon 600 # Check every 10 minutes<br /> poll imaps.student.kuleuven.be port 993 protocol imap username "$login" password "$pass" smtpname "$mail" ssl sslcertck $keep sslcertpath .certs/</li> <li>Add it to your crontab<br /> crontab -e<br /> @reboot fetchmail </li> <li>Because of our setup fetchmail cannot be started automatically when the shell server is restarted. But you if you add it to your crontab, you'll get email that it failed. You can then manually login on our shell servers to start fetchmail again.</li> <li>Start fetchmail:<br /> fetchmail</li> </ul> [[Category:Mail]] b6a75ba3bb91a32eb3d95d771cac4afffa3b3945 870 869 2019-10-26T00:46:24Z Bert 8 wikitext text/x-wiki <p>You can use our shell-servers to forward mails from your KULeuven mailbox to an email provider of your choice (e.g. GMail).</p> {{warning|Warning!|DOING THIS IS ENTIRELY ON YOUR OWN RISK. ULYSSIS CANNOT BE HELD RESPONSIBLE FOR LOST/DELAY MAILS. BY HAVING OUR SERVERS FORWARD YOUR KULEUVEN MAIL, YOU TAKE FULL RESPONSIBILITY.}} This tutorial is based on http://ronin.ulyssis.be/files/kulmail_gmail2.txt We wrote a script that configures everything automatically. To use it, log in on one of our shell servers and execute the following commands: # wget ftp://ftp.ulyssis.org/kulforward/kulforwardsetup.sh # chmod u+x kulforwardsetup.sh # ./kulforwardsetup.sh # Follow the instructions on the screen. <p>Alternatively, you can configure everything yourself. Below we briefly explain how to do this.</p> <ul> <li>Create a directory to save the SSL certificates:<br />mkdir .certs</li> <li>Put the necessary certificates in the .certs directory:<br />cd .certs<br />wget ftp://ftp.ulyssis.org/kulforward/imapkul.pem<br />wget ftp://ftp.ulyssis.org/kulforward/usertrust.pem<br />cp /etc/ssl/certs/AddTrust_External_Root.pem .<br />cd </li> <li>Rehash them:<br />c_rehash ~/.certs/</li> <li>Create the fetchmail configuration file with your favourite text editor and enter the confiration details:<br /> $login = your KULeuven login (e.g. s0123456)<br /> $pass = your KULeuven password<br /> $mail = the email address to forward your KULeuven mail to (TRIPLECHECK IT!!)<br /> keep = "" (delete forwarded mails from your KULeuven mailbox) or "keep" (keep forwarded emails)<br /> set daemon 600 # Check every 10 minutes<br /> poll imaps.student.kuleuven.be port 993 protocol imap username "$login" password "$pass" smtpname "$mail" ssl sslcertck $keep sslcertpath .certs/</li> <li>Add it to your crontab<br /> crontab -e<br /> @reboot fetchmail </li> <li>Because of our setup fetchmail cannot be started automatically when the shell server is restarted. But you if you add it to your crontab, you'll get email that it failed. You can then manually login on our shell servers to start fetchmail again.</li> <li>Start fetchmail:<br /> fetchmail</li> </ul> [[Category:Mail]] ca115439392d1f52014dd3cc1ebb901b402f33ce 0 55 871 743 2019-10-26T00:49:38Z Bert 8 wikitext text/x-wiki ==Google's recaptcha== ===What is recaptcha and how/will it help prevent spam?=== For answers to those questions you can look at google's page about recaptcha (https://google.com/recaptcha) ===Installation=== This installation guide requires Wordpress '''3.8''' or higher * Go to the Wordpress recaptcha plugin site (https://wordpress.org/plugins/google-captcha/) and download the latest version on our site in to the Wordpress installation folder * Extract the contents of the archive in to '''./wp-content/plugins/ ''' * Navigate to the Wordpress admin dashbord and select the plugin link (on the left side of the dashboard) * Activate the google recaptcha plugin * This will give you a link to the configuration page of the plugin or you can select the settings link located below the plugin * Follow the instructions on the page and depending on your configuration recaptcha will start ===Video instructions=== The makers of the Wordpress recaptcha have a video tutorial. This will supplement the above instructions, particularly the last step. (https://youtu.be/RUJ9VwZLFSY) [[Category:Security & anti-spam]] 09afacd277182f9a4a1f5a3b4f933fb09b249df7 0 57 872 742 2019-10-26T00:49:50Z Bert 8 /* What is recaptcha and how does/will it help prevent spam ? */ wikitext text/x-wiki ==Google's recaptcha== ===What is recaptcha and how does/will it help prevent spam ?=== For answers to those questions you can look at google's page about recaptcha (https://google.com/recaptcha) ===Installation=== This installation guide requires joomla '''3.4''' (or higher). * Go to google's recaptcha administrator page(https://www.google.com/recaptcha/admin) and register your site **example of public and private key (https://i.imgur.com/vGJKEXx.png) * Navigate to the admin panel of your joomla instalation ** Select plugins from the extentions panel in the top menu. * Search for recaptcha in the search box ** Enable recaptcha by clicking on the status icon next to recaptcha * One complete it is '''critical''' that you configure your recaptcha properly ** Go to recaptcha's configuration page by selecting recaptcha in the above mentioned panel ** '''make sure you select version 2 (default is version 1)''' ** Fill in the required keys you got on google's recaptcha's administrator page * Once done joomla will begin to require recaptcha's [[Category:Security & anti-spam]] a91467ad331da8c744f90c9217f5daa0c29e1c45 0 56 873 741 2019-10-26T00:50:00Z Bert 8 /* What is recaptcha and how/will it help prevent spam ? */ wikitext text/x-wiki ==Google's recaptcha== ===What is recaptcha and how/will it help prevent spam ?=== For answers to those questions you can look at google's page about recaptcha (https://google.com/recaptcha) ===Installation=== This installation guide requires drupal '''6,7 or preferably 8''' (or higher). '''Note this installation requires captcha and recaptcha, these are different plugins and not a type error.''' * Go to drupal's captcha page and download the appropriate version at the bottom of the page (https://www.drupal.org/project/captcha) * Go to drupal's recaptcha page and download the appropriate version at the bottom of the page (https://www.drupal.org/project/recaptcha) ** Extract the archives into '''sites/all/modules/[recaptcha/captcha]'''respectively and relative to your own drupal installation '''(this folder may need to be created manually)''' * Now navigate to your drupal administration page in your browser (/admin/modules) ** Search for captcha and enable it ** Search for recaptcha and enable it * Once complete it is '''critical''' to configure your captcha setting in the web interface (/admin/config/people/captcha) '''and do not forget to enable the captcha-points (/admin/config/people/captcha/captcha-points). [[Category:Security & anti-spam]] 1712db8c440971530a07b0fd22c85bdf6c339a28 0 12 874 746 2019-10-26T00:52:02Z Bert 8 wikitext text/x-wiki == Creating a database == You can create one or more PostgreSQL databases in [https://ucc.ulyssis.org UCC]. The first database you create will have the same name as your username. Subsequent databases will be prefixed with "''username''_". == Managing your database == * The easiest way to manage your database is using [https://phppgadmin.ulyssis.org phpPgAdmin]. * You can also access it via the [[Accessing shell servers over SSH|command line]] with: psql -h pgsql.ulyssis.org == Connecting to the database == You can connect to the database with the following details: * Host: <code>pgsql.ulyssis.org</code> * Login: your ULYSSIS username * Password: the PostgreSQL password you chose in UCC * Database: the database you created in UCC Note that some CMSs will assume that you use "localhost" as the host, and will hide the host option under advanced settings in the installation process. If you can't find anywhere to enter the hostname, look under advanced settings. === Connection string === If you are programming your application yourself, PostgreSQL often uses the following connection format: host=$host user=$username password=$password db=$dbname Where you replace the parts starting with <code>$</code> with the above connection details. === pg_connect === If you are using PHP's [http://www.php.net/manual/en/function.pg-connect.php pg_connect] to connect to the database, and your username is "foo", your password is "password" and your database name is "foo": <syntaxhighlight lang="php"> $connection = pg_connect("host=pgsql.ulyssis.org user=foo password=password db=foo"); </syntaxhighlight> === PDO === If you want to connect using [http://be2.php.net/manual/en/intro.pdo.php PDO], your username is "foo", your password is "password" and your database is "foo": <syntaxhighlight lang="php"> $pdo = new PDO('pgsql:host=pgsql.ulyssis.org;dbname=foo', 'foo', 'password'); </syntaxhighlight> ==Accessing PostgreSQL from outside of our network== To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH-tunnel. On Linux, Mac OSX and other Unix-like Operating Systems it is easily possible to use the following command to create a tunnel to a local port (in this case 5400): ssh username@ssh2.ulyssis.org -L 5400:pgsql.ulyssis.org:5432 -N You can use "ssh -f username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N": the f-argument will put the command in the background. == PostGIS == If necessary for an application or website you wish to use on ULYSSIS, we can always enable PostGIS for the specific database you wish to use it on. Contact us at ulyssis@ulyssis.org and let us know you would like to get PostGIS enabled and on which specific database. [[Category:Databases]] ab4512d6ab49658ab2e2d4bbcc9977e0aaa0ff49 0 4 875 756 2019-10-26T00:53:10Z Bert 8 /* Linux */ wikitext text/x-wiki Users can access the ULYSSIS servers through two machines: <code>ssh1.ulyssis.org</code> and <code>ssh2.ulyssis.org</code>. Both of them run Linux. You can run commands on these servers or use them to access the files on your ULYSSIS account. The servers can only be accessed trough SSH, not through FTP or any other protocol. =Running commands= To run a command on the shell servers, you will need to connect to them using a terminal. Our servers do not support a full graphical interface. ==Linux== On Linux, you can just open a terminal and connect to the servers by using one of the following commands (with <code>username</code> your username): ssh username@ssh1.ulyssis.org ssh username@ssh2.ulyssis.org Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. ==Windows== Windows doesn't support native terminals, so you will have to download a program first. A good option is [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty], which is completely free and doesn't require any installation. Just download it and run the .exe file. The parameters: *Host name: ssh1.ulyssis.org or ssh2.ulyssis.org *Protocol: SSH *Port: 22 (should be set automatically) You can save these options for later on. Next, you will be asked to give your password. Doing all this will open a terminal to the remote server which can be used the same way as a Linux terminal. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. More information about Putty can be found at http://the.earth.li/~sgtatham/putty/0.60/htmldoc/. ==Mac== On Mac, you can just open Terminal. This application can be found in the Utilities folder within your Application folder. If you don't find it there, you can use Spotlight to find it. You can now connect to the servers by using one of the following commands (with <code>username</code> your username): <code>ssh username@ssh1.ulyssis.org</code><br /> <code>ssh username@ssh2.ulyssis.org</code> Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use ctrl+D. ==Useful ideas== Here are some useful ideas about what you could do with your shell server access: *[[Accessing your files]] *[[Fetch your KU Leuven email into another email address]] *[[ULYSSIS public IRC]] ==Useful commands== Some useful commands can be found [[Useful Linux Commands|here]]. [[Category:Shell]] 9e42c0fe076aaee9f417ae6dafac0880a3693f18 876 875 2019-10-26T00:53:25Z Bert 8 /* Linux */ wikitext text/x-wiki Users can access the ULYSSIS servers through two machines: <code>ssh1.ulyssis.org</code> and <code>ssh2.ulyssis.org</code>. Both of them run Linux. You can run commands on these servers or use them to access the files on your ULYSSIS account. The servers can only be accessed trough SSH, not through FTP or any other protocol. =Running commands= To run a command on the shell servers, you will need to connect to them using a terminal. Our servers do not support a full graphical interface. ==Linux== On Linux, you can just open a terminal and connect to the servers by using one of the following commands (with <code>username</code> your username): ssh username@ssh1.ulyssis.org ssh username@ssh2.ulyssis.org Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. ==Windows== Windows doesn't support native terminals, so you will have to download a program first. A good option is [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty], which is completely free and doesn't require any installation. Just download it and run the .exe file. The parameters: *Host name: ssh1.ulyssis.org or ssh2.ulyssis.org *Protocol: SSH *Port: 22 (should be set automatically) You can save these options for later on. Next, you will be asked to give your password. Doing all this will open a terminal to the remote server which can be used the same way as a Linux terminal. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. More information about Putty can be found at http://the.earth.li/~sgtatham/putty/0.60/htmldoc/. ==Mac== On Mac, you can just open Terminal. This application can be found in the Utilities folder within your Application folder. If you don't find it there, you can use Spotlight to find it. You can now connect to the servers by using one of the following commands (with <code>username</code> your username): <code>ssh username@ssh1.ulyssis.org</code><br /> <code>ssh username@ssh2.ulyssis.org</code> Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use ctrl+D. ==Useful ideas== Here are some useful ideas about what you could do with your shell server access: *[[Accessing your files]] *[[Fetch your KU Leuven email into another email address]] *[[ULYSSIS public IRC]] ==Useful commands== Some useful commands can be found [[Useful Linux Commands|here]]. [[Category:Shell]] d1f28398d236873135e8058a08c5224d072b372e 877 876 2019-10-26T00:53:39Z Bert 8 /* Mac */ wikitext text/x-wiki Users can access the ULYSSIS servers through two machines: <code>ssh1.ulyssis.org</code> and <code>ssh2.ulyssis.org</code>. Both of them run Linux. You can run commands on these servers or use them to access the files on your ULYSSIS account. The servers can only be accessed trough SSH, not through FTP or any other protocol. =Running commands= To run a command on the shell servers, you will need to connect to them using a terminal. Our servers do not support a full graphical interface. ==Linux== On Linux, you can just open a terminal and connect to the servers by using one of the following commands (with <code>username</code> your username): ssh username@ssh1.ulyssis.org ssh username@ssh2.ulyssis.org Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. ==Windows== Windows doesn't support native terminals, so you will have to download a program first. A good option is [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty], which is completely free and doesn't require any installation. Just download it and run the .exe file. The parameters: *Host name: ssh1.ulyssis.org or ssh2.ulyssis.org *Protocol: SSH *Port: 22 (should be set automatically) You can save these options for later on. Next, you will be asked to give your password. Doing all this will open a terminal to the remote server which can be used the same way as a Linux terminal. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. More information about Putty can be found at http://the.earth.li/~sgtatham/putty/0.60/htmldoc/. ==Mac== On Mac, you can just open Terminal. This application can be found in the Utilities folder within your Application folder. If you don't find it there, you can use Spotlight to find it. You can now connect to the servers by using one of the following commands (with <code>username</code> your username): ssh username@ssh1.ulyssis.org ssh username@ssh2.ulyssis.org Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use ctrl+D. ==Useful ideas== Here are some useful ideas about what you could do with your shell server access: *[[Accessing your files]] *[[Fetch your KU Leuven email into another email address]] *[[ULYSSIS public IRC]] ==Useful commands== Some useful commands can be found [[Useful Linux Commands|here]]. [[Category:Shell]] 5fc45c8a62f0784169fefeb528d7610ceab02a4b 0 16 878 754 2019-10-26T00:54:40Z Bert 8 /* Basic file managment */ wikitext text/x-wiki Once you've connected, you can use these commands to use the ULYSSIS shell. First of all, whenever you need to type a longer command or filename, try the <code>TAB</code> key as it will try to complete the name of the command or file you are typing. Pressing <code>TAB</code> twice will show a list of possible completions. A more extensive document on this can be found at http://info.ee.surrey.ac.uk/Teaching/Unix/. ==Basic file managment== cd directoryname Change directory. Works the same as under MS-DOS. cd without argument changes to your home directory (like My Documents in windows). Go to the parent directory with <code>cd ..</code> ls List the contents of the current directory. Many different formats are available, a common one is <code>ls -al</code>. To accomodate MS-DOS/Windows users, <code>dir</code> is an alias (synonym) for <code>ls -alF</code>, which gives output similar to the <code>dir</code> command in MS-DOS/Windows. cp inputfile targetfile Copy inputfile to targetfile. Additional arguments (e.g. -r or -v are explained in the man-page.) mv inputfile targetfile Move inputfile to targetfile. Additional arguments (e.g. -i or -v are explained in the man-page.) This is the way to rename a file. Note that you cannot use a construction like mv *.htm *.html to add an ``l'' to a bunch of files. A small shell script can provide a way to do this: <code>for i in *.htm; do mv i; done</code> rm filename Remove filename. Additional arguments (e.g. -r or -v are explained in the man-page.) Note: there is no undelete-alike function in most unices. mkdir dirname Creates a directory called dirname. rmdir dirname Removes an empty directory. Use rm -r to delete a directory and recursively everything in it. Add -f to disable any prompts (dangerous!). ==Getting help== <code>man command-name</code> Displays manual pages, if available. E.g. man ls. Use 'q' to exit. Relatives: apropos, help. <code>apropos word</code> Searches through headers of all man pages. <code>help command-name</code> Displays help about command-name. Only for internal bash-functions. <code>bash</code> The Bourne Again SHell. Widely used successor of sh, the Bourne shell. This is the program you're working under after you open a ssh-session (you don't have to start it to use it). Bash interprets your commands, and executes them. Tab-completion, * and ? expansions, etc are all bash functions. man bash will give you tons of info about it. Alternatives : tcsh, zsh, rc ==Text editors== It's easier to use a text editor on a server, than editing your file locally and uploading that file. <code>pico</code> or <code>nano</code> Probably the easiest text editor. Should be self-explanatory. <code>joe</code> Another easy text editor. Press Ctrl+C to quit. <code>vim</code> Probably the best text editor. Start editing by pressing <code>i</code>. Stop editing by pressing the <code>escape</code> key. Save and quit with <code>:wq</code>. Quit without saving with <code>:q!</code>. ==Utilities== <code>df</code> Displays info about the free diskspace on the system. df . will give info about the filesystem where the current directory resides. The output becomes a bit more readable with the -h switch. <code>du</code> Displays info about the diskusage in the current directory (and its subdirectories. A common parameter is -s , equivalent to -summarize , to summarize the disk-usage (without the per-subdir totals). <code>quota</code> Displays info about your diskusage, and your disk quota. Quota are limits on diskusage, imposed by the system administrator. The system will warn you if you exceed these limits. <code>ps</code> Displays info about processes. Various options possible, for example ps auxf gives info on all processes, including process owner, memory usage, and parent-child indication. <code>htop</code> Displays top CPU processes. Use it to see what gets most cpu power at the moment. Don't leave top open for a long time, since it eats cpu time itself. (quit with 'q'). [[Category:Shell]] 23dd7f29bd2f3d914bf1d07474d7a0df0a42b3b1 879 878 2019-10-26T00:55:21Z Bert 8 /* Getting help */ wikitext text/x-wiki Once you've connected, you can use these commands to use the ULYSSIS shell. First of all, whenever you need to type a longer command or filename, try the <code>TAB</code> key as it will try to complete the name of the command or file you are typing. Pressing <code>TAB</code> twice will show a list of possible completions. A more extensive document on this can be found at http://info.ee.surrey.ac.uk/Teaching/Unix/. ==Basic file managment== cd directoryname Change directory. Works the same as under MS-DOS. cd without argument changes to your home directory (like My Documents in windows). Go to the parent directory with <code>cd ..</code> ls List the contents of the current directory. Many different formats are available, a common one is <code>ls -al</code>. To accomodate MS-DOS/Windows users, <code>dir</code> is an alias (synonym) for <code>ls -alF</code>, which gives output similar to the <code>dir</code> command in MS-DOS/Windows. cp inputfile targetfile Copy inputfile to targetfile. Additional arguments (e.g. -r or -v are explained in the man-page.) mv inputfile targetfile Move inputfile to targetfile. Additional arguments (e.g. -i or -v are explained in the man-page.) This is the way to rename a file. Note that you cannot use a construction like mv *.htm *.html to add an ``l'' to a bunch of files. A small shell script can provide a way to do this: <code>for i in *.htm; do mv i; done</code> rm filename Remove filename. Additional arguments (e.g. -r or -v are explained in the man-page.) Note: there is no undelete-alike function in most unices. mkdir dirname Creates a directory called dirname. rmdir dirname Removes an empty directory. Use rm -r to delete a directory and recursively everything in it. Add -f to disable any prompts (dangerous!). ==Getting help== man command-name Displays manual pages, if available. E.g. man ls. Use 'q' to exit. Relatives: apropos, help. apropos word Searches through headers of all man pages. help command-name Displays help about command-name. Only for internal bash-functions. bash The Bourne Again SHell. Widely used successor of sh, the Bourne shell. This is the program you're working under after you open a ssh-session (you don't have to start it to use it). Bash interprets your commands, and executes them. Tab-completion, * and ? expansions, etc are all bash functions. man bash will give you tons of info about it. Alternatives : tcsh, zsh, rc ==Text editors== It's easier to use a text editor on a server, than editing your file locally and uploading that file. <code>pico</code> or <code>nano</code> Probably the easiest text editor. Should be self-explanatory. <code>joe</code> Another easy text editor. Press Ctrl+C to quit. <code>vim</code> Probably the best text editor. Start editing by pressing <code>i</code>. Stop editing by pressing the <code>escape</code> key. Save and quit with <code>:wq</code>. Quit without saving with <code>:q!</code>. ==Utilities== <code>df</code> Displays info about the free diskspace on the system. df . will give info about the filesystem where the current directory resides. The output becomes a bit more readable with the -h switch. <code>du</code> Displays info about the diskusage in the current directory (and its subdirectories. A common parameter is -s , equivalent to -summarize , to summarize the disk-usage (without the per-subdir totals). <code>quota</code> Displays info about your diskusage, and your disk quota. Quota are limits on diskusage, imposed by the system administrator. The system will warn you if you exceed these limits. <code>ps</code> Displays info about processes. Various options possible, for example ps auxf gives info on all processes, including process owner, memory usage, and parent-child indication. <code>htop</code> Displays top CPU processes. Use it to see what gets most cpu power at the moment. Don't leave top open for a long time, since it eats cpu time itself. (quit with 'q'). [[Category:Shell]] b5ec726f2674bbc5c083039114ce8585dd79b816 880 879 2019-10-26T00:55:45Z Bert 8 /* Text editors */ wikitext text/x-wiki Once you've connected, you can use these commands to use the ULYSSIS shell. First of all, whenever you need to type a longer command or filename, try the <code>TAB</code> key as it will try to complete the name of the command or file you are typing. Pressing <code>TAB</code> twice will show a list of possible completions. A more extensive document on this can be found at http://info.ee.surrey.ac.uk/Teaching/Unix/. ==Basic file managment== cd directoryname Change directory. Works the same as under MS-DOS. cd without argument changes to your home directory (like My Documents in windows). Go to the parent directory with <code>cd ..</code> ls List the contents of the current directory. Many different formats are available, a common one is <code>ls -al</code>. To accomodate MS-DOS/Windows users, <code>dir</code> is an alias (synonym) for <code>ls -alF</code>, which gives output similar to the <code>dir</code> command in MS-DOS/Windows. cp inputfile targetfile Copy inputfile to targetfile. Additional arguments (e.g. -r or -v are explained in the man-page.) mv inputfile targetfile Move inputfile to targetfile. Additional arguments (e.g. -i or -v are explained in the man-page.) This is the way to rename a file. Note that you cannot use a construction like mv *.htm *.html to add an ``l'' to a bunch of files. A small shell script can provide a way to do this: <code>for i in *.htm; do mv i; done</code> rm filename Remove filename. Additional arguments (e.g. -r or -v are explained in the man-page.) Note: there is no undelete-alike function in most unices. mkdir dirname Creates a directory called dirname. rmdir dirname Removes an empty directory. Use rm -r to delete a directory and recursively everything in it. Add -f to disable any prompts (dangerous!). ==Getting help== man command-name Displays manual pages, if available. E.g. man ls. Use 'q' to exit. Relatives: apropos, help. apropos word Searches through headers of all man pages. help command-name Displays help about command-name. Only for internal bash-functions. bash The Bourne Again SHell. Widely used successor of sh, the Bourne shell. This is the program you're working under after you open a ssh-session (you don't have to start it to use it). Bash interprets your commands, and executes them. Tab-completion, * and ? expansions, etc are all bash functions. man bash will give you tons of info about it. Alternatives : tcsh, zsh, rc ==Text editors== It's easier to use a text editor on a server, than editing your file locally and uploading that file. nano Probably the easiest text editor. Should be self-explanatory. joe Another easy text editor. Press Ctrl+C to quit. vim Probably the best text editor. Start editing by pressing i. Stop editing by pressing the escape key. Save and quit with :wq. Quit without saving with :q!. ==Utilities== <code>df</code> Displays info about the free diskspace on the system. df . will give info about the filesystem where the current directory resides. The output becomes a bit more readable with the -h switch. <code>du</code> Displays info about the diskusage in the current directory (and its subdirectories. A common parameter is -s , equivalent to -summarize , to summarize the disk-usage (without the per-subdir totals). <code>quota</code> Displays info about your diskusage, and your disk quota. Quota are limits on diskusage, imposed by the system administrator. The system will warn you if you exceed these limits. <code>ps</code> Displays info about processes. Various options possible, for example ps auxf gives info on all processes, including process owner, memory usage, and parent-child indication. <code>htop</code> Displays top CPU processes. Use it to see what gets most cpu power at the moment. Don't leave top open for a long time, since it eats cpu time itself. (quit with 'q'). [[Category:Shell]] 95fd25958479f013b9088965e195d567576e2549 881 880 2019-10-26T00:56:14Z Bert 8 /* Utilities */ wikitext text/x-wiki Once you've connected, you can use these commands to use the ULYSSIS shell. First of all, whenever you need to type a longer command or filename, try the <code>TAB</code> key as it will try to complete the name of the command or file you are typing. Pressing <code>TAB</code> twice will show a list of possible completions. A more extensive document on this can be found at http://info.ee.surrey.ac.uk/Teaching/Unix/. ==Basic file managment== cd directoryname Change directory. Works the same as under MS-DOS. cd without argument changes to your home directory (like My Documents in windows). Go to the parent directory with <code>cd ..</code> ls List the contents of the current directory. Many different formats are available, a common one is <code>ls -al</code>. To accomodate MS-DOS/Windows users, <code>dir</code> is an alias (synonym) for <code>ls -alF</code>, which gives output similar to the <code>dir</code> command in MS-DOS/Windows. cp inputfile targetfile Copy inputfile to targetfile. Additional arguments (e.g. -r or -v are explained in the man-page.) mv inputfile targetfile Move inputfile to targetfile. Additional arguments (e.g. -i or -v are explained in the man-page.) This is the way to rename a file. Note that you cannot use a construction like mv *.htm *.html to add an ``l'' to a bunch of files. A small shell script can provide a way to do this: <code>for i in *.htm; do mv i; done</code> rm filename Remove filename. Additional arguments (e.g. -r or -v are explained in the man-page.) Note: there is no undelete-alike function in most unices. mkdir dirname Creates a directory called dirname. rmdir dirname Removes an empty directory. Use rm -r to delete a directory and recursively everything in it. Add -f to disable any prompts (dangerous!). ==Getting help== man command-name Displays manual pages, if available. E.g. man ls. Use 'q' to exit. Relatives: apropos, help. apropos word Searches through headers of all man pages. help command-name Displays help about command-name. Only for internal bash-functions. bash The Bourne Again SHell. Widely used successor of sh, the Bourne shell. This is the program you're working under after you open a ssh-session (you don't have to start it to use it). Bash interprets your commands, and executes them. Tab-completion, * and ? expansions, etc are all bash functions. man bash will give you tons of info about it. Alternatives : tcsh, zsh, rc ==Text editors== It's easier to use a text editor on a server, than editing your file locally and uploading that file. nano Probably the easiest text editor. Should be self-explanatory. joe Another easy text editor. Press Ctrl+C to quit. vim Probably the best text editor. Start editing by pressing i. Stop editing by pressing the escape key. Save and quit with :wq. Quit without saving with :q!. ==Utilities== df Displays info about the free diskspace on the system. df . will give info about the filesystem where the current directory resides. The output becomes a bit more readable with the -h switch. du Displays info about the diskusage in the current directory (and its subdirectories. A common parameter is -s , equivalent to -summarize , to summarize the disk-usage (without the per-subdir totals). quota Displays info about your diskusage, and your disk quota. Quota are limits on diskusage, imposed by the system administrator. The system will warn you if you exceed these limits. ps Displays info about processes. Various options possible, for example ps auxf gives info on all processes, including process owner, memory usage, and parent-child indication. htop Displays top CPU processes. Use it to see what gets most cpu power at the moment. Don't leave top open for a long time, since it eats cpu time itself. (quit with 'q'). [[Category:Shell]] 8c0f86b5128d46f7445bec1f9b3305baff280cb3 0 13 883 759 2019-10-26T00:58:12Z Bert 8 wikitext text/x-wiki If you want to use [http://git-scm.com/ git] for version control to work privately on personal projects, or collaborate with others on projects, you can use GitLab for central repositories, and for tracking bugs. == Accessing GitLab == You can access our GitLab server at https://gitlab.ulyssis.org. You can log in with your standard ULYSSIS username and password. == Getting started with Git == If you want to get acquainted with git, these are good free resources: * [https://try.github.io Try Git]: an interactive introduction to git * [http://git-scm.com/book Pro Git]: a book that you can read for free online * [http://git-scm.com/docs The official Git reference documentation] == Guest users == Sadly, we do not provide automated guest user support for GitLab yet, as we do for Subversion. If not everyone who works on your project has their own ULYSSIS account, you can request a Gitlab guest account via email. You simply send an email with the guest account's username (which will be prefixed with an underscore), full name, KU Leuven uid (m/s/r/u number) and email address to ulyssis@ulyssis.org and we will create it. Do keep in mind you bear full responsibility for all guests created for your account. [[Category:Versioning]] 3ea4b24ab336fcd27a565aeb035f982bbdbce802 0 78 884 766 2019-10-26T00:58:29Z Bert 8 wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. # Set up agenda sync on KU Loket ## Visit [http://kuloket.be/ KU Loket] ## Go to the '''Education & Students''' (Onderwijs & studenten) tab [[File:KULoket-Agenda-Step1.png|thumb|200px]] ## Click '''Agenda sync''' ## Click '''Configure agenda''' (Agenda instellen) [[File:KULoket-Agenda-Step2.png|thumb|200px]] ## Change the switch '''Show schedule in my agenda''' (Toon uurrooster in mijn agenda) to '''On'''. [[File:KULoket-Agenda-Step3.png|thumb|200px]] You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (Agenda) # On the top right (below the menu bar), click the '''Share''' (Delen) button. A side-panel appears. # Enter a non-KU Leuven email address in the '''Share with''' (Delen met) textfield. After filling the email address, press the enter key. # Make sure '''Full details''' (Volledige informatie) is selected in the dropdown next to your email address # Click the '''Send''' (Verzenden) button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> [[Category:Tutorials]] 8e0b4b9e03050e728d560702ce0cbcab64cdd33d 887 884 2019-10-28T16:20:37Z Alexander 38 wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. # Set up agenda sync on KU Loket ## Visit [http://kuloket.be/ KU Loket] ## Go to the '''Education & Students''' (Onderwijs & studenten) tab [[File:KULoket-Agenda-Step1.png|thumb|200px]] ## Click '''Agenda sync''' ## Click '''Configure agenda''' (Agenda instellen) [[File:Capturee.PNG|thumb|200px]] ## Change the switch '''Show schedule in my agenda''' (Toon uurrooster in mijn agenda) to '''On'''. [[File:KULoket-Agenda-Step3.png|thumb|200px]] You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (Agenda) # On the top right (below the menu bar), click the '''Share''' (Delen) button. A side-panel appears. # Enter a non-KU Leuven email address in the '''Share with''' (Delen met) textfield. After filling the email address, press the enter key. # Make sure '''Full details''' (Volledige informatie) is selected in the dropdown next to your email address # Click the '''Send''' (Verzenden) button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> [[Category:Tutorials]] 1c28c2558e02b41df6b62903feaf5c3ac1795048 889 887 2019-10-28T16:21:57Z Alexander 38 wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. # Set up agenda sync on KU Loket ## Visit [http://kuloket.be/ KU Loket] ## Go to the '''Education & Students''' (Onderwijs & studenten) tab [[File:KULoket-Agenda-Step1.png|thumb|200px]] ## Click '''Agenda sync''' ## Click '''Configure agenda''' (Agenda instellen) [[File:KULoket-Agenda-Step2.png|thumb|200px]] ## Change the switch '''Show schedule in my agenda''' (Toon uurrooster in mijn agenda) to '''On'''. [[File:KULoket-Agenda-Step3.png|thumb|200px]] You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (Agenda) # On the top right (below the menu bar), click the '''Share''' (Delen) button. A side-panel appears. # Enter a non-KU Leuven email address in the '''Share with''' (Delen met) textfield. After filling the email address, press the enter key. # Make sure '''Full details''' (Volledige informatie) is selected in the dropdown next to your email address # Click the '''Send''' (Verzenden) button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> [[Category:Tutorials]] 8e0b4b9e03050e728d560702ce0cbcab64cdd33d 890 889 2019-10-28T16:22:45Z Alexander 38 wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. # Set up agenda sync on KU Loket ## Visit [http://kuloket.be/ KU Loket] ## Go to the '''Education & Students''' (Onderwijs & studenten) tab [[File:Captureep.png|thumb|200px]] ## Click '''Agenda sync''' ## Click '''Configure agenda''' (Agenda instellen) [[File:KULoket-Agenda-Step2.png|thumb|200px]] ## Change the switch '''Show schedule in my agenda''' (Toon uurrooster in mijn agenda) to '''On'''. [[File:KULoket-Agenda-Step3.png|thumb|200px]] You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (Agenda) # On the top right (below the menu bar), click the '''Share''' (Delen) button. A side-panel appears. # Enter a non-KU Leuven email address in the '''Share with''' (Delen met) textfield. After filling the email address, press the enter key. # Make sure '''Full details''' (Volledige informatie) is selected in the dropdown next to your email address # Click the '''Send''' (Verzenden) button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> [[Category:Tutorials]] 2441b0a3bb347e1d54b90f622cf408a44aa31d0d 891 890 2019-10-28T16:23:33Z Alexander 38 Undo revision 890 by [[Special:Contributions/Alexander|Alexander]] ([[User talk:Alexander|talk]]) wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. # Set up agenda sync on KU Loket ## Visit [http://kuloket.be/ KU Loket] ## Go to the '''Education & Students''' (Onderwijs & studenten) tab [[File:KULoket-Agenda-Step1.png|thumb|200px]] ## Click '''Agenda sync''' ## Click '''Configure agenda''' (Agenda instellen) [[File:KULoket-Agenda-Step2.png|thumb|200px]] ## Change the switch '''Show schedule in my agenda''' (Toon uurrooster in mijn agenda) to '''On'''. [[File:KULoket-Agenda-Step3.png|thumb|200px]] You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (Agenda) # On the top right (below the menu bar), click the '''Share''' (Delen) button. A side-panel appears. # Enter a non-KU Leuven email address in the '''Share with''' (Delen met) textfield. After filling the email address, press the enter key. # Make sure '''Full details''' (Volledige informatie) is selected in the dropdown next to your email address # Click the '''Send''' (Verzenden) button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> [[Category:Tutorials]] 8e0b4b9e03050e728d560702ce0cbcab64cdd33d 892 891 2019-10-28T16:23:49Z Alexander 38 Undo revision 889 by [[Special:Contributions/Alexander|Alexander]] ([[User talk:Alexander|talk]]) wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. # Set up agenda sync on KU Loket ## Visit [http://kuloket.be/ KU Loket] ## Go to the '''Education & Students''' (Onderwijs & studenten) tab [[File:KULoket-Agenda-Step1.png|thumb|200px]] ## Click '''Agenda sync''' ## Click '''Configure agenda''' (Agenda instellen) [[File:Capturee.PNG|thumb|200px]] ## Change the switch '''Show schedule in my agenda''' (Toon uurrooster in mijn agenda) to '''On'''. [[File:KULoket-Agenda-Step3.png|thumb|200px]] You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (Agenda) # On the top right (below the menu bar), click the '''Share''' (Delen) button. A side-panel appears. # Enter a non-KU Leuven email address in the '''Share with''' (Delen met) textfield. After filling the email address, press the enter key. # Make sure '''Full details''' (Volledige informatie) is selected in the dropdown next to your email address # Click the '''Send''' (Verzenden) button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> [[Category:Tutorials]] 1c28c2558e02b41df6b62903feaf5c3ac1795048 893 892 2019-10-28T16:24:18Z Alexander 38 Undo revision 887 by [[Special:Contributions/Alexander|Alexander]] ([[User talk:Alexander|talk]]) wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. # Set up agenda sync on KU Loket ## Visit [http://kuloket.be/ KU Loket] ## Go to the '''Education & Students''' (Onderwijs & studenten) tab [[File:KULoket-Agenda-Step1.png|thumb|200px]] ## Click '''Agenda sync''' ## Click '''Configure agenda''' (Agenda instellen) [[File:KULoket-Agenda-Step2.png|thumb|200px]] ## Change the switch '''Show schedule in my agenda''' (Toon uurrooster in mijn agenda) to '''On'''. [[File:KULoket-Agenda-Step3.png|thumb|200px]] You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (Agenda) # On the top right (below the menu bar), click the '''Share''' (Delen) button. A side-panel appears. # Enter a non-KU Leuven email address in the '''Share with''' (Delen met) textfield. After filling the email address, press the enter key. # Make sure '''Full details''' (Volledige informatie) is selected in the dropdown next to your email address # Click the '''Send''' (Verzenden) button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> [[Category:Tutorials]] 8e0b4b9e03050e728d560702ce0cbcab64cdd33d 895 893 2019-10-28T16:25:36Z Alexander 38 wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. # Set up agenda sync on KU Loket ## Visit [http://kuloket.be/ KU Loket] ## Go to the '''Education & Students''' (Onderwijs & studenten) tab [[File:KUL_Agenda_Step1.png|thumb|200px]] ## Click '''Agenda sync''' ## Click '''Configure agenda''' (Agenda instellen) [[File:KULoket-Agenda-Step2.png|thumb|200px]] ## Change the switch '''Show schedule in my agenda''' (Toon uurrooster in mijn agenda) to '''On'''. [[File:KULoket-Agenda-Step3.png|thumb|200px]] You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (Agenda) # On the top right (below the menu bar), click the '''Share''' (Delen) button. A side-panel appears. # Enter a non-KU Leuven email address in the '''Share with''' (Delen met) textfield. After filling the email address, press the enter key. # Make sure '''Full details''' (Volledige informatie) is selected in the dropdown next to your email address # Click the '''Send''' (Verzenden) button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> [[Category:Tutorials]] 20d55cb6250de254b285ce0fb729fca6a2c3383b 897 895 2019-10-28T16:27:42Z Alexander 38 wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. # Set up agenda sync on KU Loket ## Visit [http://kuloket.be/ KU Loket] ## Go to the '''Education & Students''' (Onderwijs & studenten) tab [[File:KUL-Agenda-Step1.png|thumb|200px]] ## Click '''Agenda sync''' ## Click '''Configure agenda''' (Agenda instellen) [[File:KULoket-Agenda-Step2.png|thumb|200px]] ## Change the switch '''Show schedule in my agenda''' (Toon uurrooster in mijn agenda) to '''On'''. [[File:KULoket-Agenda-Step3.png|thumb|200px]] You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (Agenda) # On the top right (below the menu bar), click the '''Share''' (Delen) button. A side-panel appears. # Enter a non-KU Leuven email address in the '''Share with''' (Delen met) textfield. After filling the email address, press the enter key. # Make sure '''Full details''' (Volledige informatie) is selected in the dropdown next to your email address # Click the '''Send''' (Verzenden) button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> [[Category:Tutorials]] 8ba3b62afb133c92dedea1507a879a1a0256a8fb 902 897 2019-10-28T16:42:12Z Alexander 38 wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. # Set up agenda sync on KU Loket ## Visit [http://kuloket.be/ KU Loket] ## Go to the '''Education & Students''' (Onderwijs & studenten) tab [[File:KUL-Agenda-Step1.PNG|thumb|200px]] ## Click '''Agenda sync''' ## Click '''Configure agenda''' (Agenda instellen) [[File:KULoket-Agenda-Step2.png|thumb|200px]] ## Change the switch '''Show schedule in my agenda''' (Toon uurrooster in mijn agenda) to '''On'''. [[File:KULoket-Agenda-Step3.png|thumb|200px]] You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (Agenda) # On the top right (below the menu bar), click the '''Share''' (Delen) button. A side-panel appears. # Enter a non-KU Leuven email address in the '''Share with''' (Delen met) textfield. After filling the email address, press the enter key. # Make sure '''Full details''' (Volledige informatie) is selected in the dropdown next to your email address # Click the '''Send''' (Verzenden) button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> [[Category:Tutorials]] 95fbd4d4a51570da91943d6405d536e6b7691dfc 903 902 2019-10-28T16:42:52Z Alexander 38 wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. # Set up agenda sync on KU Loket ## Visit [http://kuloket.be/ KU Loket] ## Go to the '''Education & Students''' (Onderwijs & studenten) tab [[File:KUL-Agenda-Step1.PNG|thumb|200px]] ## Click '''Agenda sync''' ## Click '''Configure agenda''' (Agenda instellen) [[File:KUL_Agenda-Step2.PNG.png|thumb|200px]] ## Change the switch '''Show schedule in my agenda''' (Toon uurrooster in mijn agenda) to '''On'''. [[File:KUL-Agenda-Step3.PNG|thumb|200px]] You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (Agenda) # On the top right (below the menu bar), click the '''Share''' (Delen) button. A side-panel appears. # Enter a non-KU Leuven email address in the '''Share with''' (Delen met) textfield. After filling the email address, press the enter key. # Make sure '''Full details''' (Volledige informatie) is selected in the dropdown next to your email address # Click the '''Send''' (Verzenden) button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> [[Category:Tutorials]] c83eb322d7ca96be2e38aaa9580490bff46a3f97 904 903 2019-10-28T16:43:09Z Alexander 38 wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. # Set up agenda sync on KU Loket ## Visit [http://kuloket.be/ KU Loket] ## Go to the '''Education & Students''' (Onderwijs & studenten) tab [[File:KUL-Agenda-Step1.PNG|thumb|200px]] ## Click '''Agenda sync''' ## Click '''Configure agenda''' (Agenda instellen) [[File:KUL_Agenda-Step2.PNG|thumb|200px]] ## Change the switch '''Show schedule in my agenda''' (Toon uurrooster in mijn agenda) to '''On'''. [[File:KUL-Agenda-Step3.PNG|thumb|200px]] You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (Agenda) # On the top right (below the menu bar), click the '''Share''' (Delen) button. A side-panel appears. # Enter a non-KU Leuven email address in the '''Share with''' (Delen met) textfield. After filling the email address, press the enter key. # Make sure '''Full details''' (Volledige informatie) is selected in the dropdown next to your email address # Click the '''Send''' (Verzenden) button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> [[Category:Tutorials]] 4388a44fb21eb4a926e04740d33c68e65c303ac7 905 904 2019-10-28T16:43:21Z Alexander 38 wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. # Set up agenda sync on KU Loket ## Visit [http://kuloket.be/ KU Loket] ## Go to the '''Education & Students''' (Onderwijs & studenten) tab [[File:KUL-Agenda-Step1.PNG|thumb|200px]] ## Click '''Agenda sync''' ## Click '''Configure agenda''' (Agenda instellen) [[File:KUL-Agenda-Step2.PNG|thumb|200px]] ## Change the switch '''Show schedule in my agenda''' (Toon uurrooster in mijn agenda) to '''On'''. [[File:KUL-Agenda-Step3.PNG|thumb|200px]] You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (Agenda) # On the top right (below the menu bar), click the '''Share''' (Delen) button. A side-panel appears. # Enter a non-KU Leuven email address in the '''Share with''' (Delen met) textfield. After filling the email address, press the enter key. # Make sure '''Full details''' (Volledige informatie) is selected in the dropdown next to your email address # Click the '''Send''' (Verzenden) button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> [[Category:Tutorials]] 09bb98bd162b9593f6535706153b48750286c10d 906 905 2019-10-28T16:43:56Z Alexander 38 wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. # Set up agenda sync on KU Loket ## Visit [http://kuloket.be/ KU Loket] ## Go to the '''Education & Students''' (Onderwijs & studenten) tab [[File:KUL-Agenda-Step1.PNG|thumb|200px]] ## Click '''Agenda sync''' ## Click '''Configure agenda''' (Agenda instellen) [[File:KUL-Agenda-Step2.PNG|thumb|200px]] ## Change the switch '''Show schedule in my agenda''' (Toon uurrooster in mijn agenda) to '''On'''. [[File:KUL-Agenda-Step3.png|thumb|200px]] You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (Agenda) # On the top right (below the menu bar), click the '''Share''' (Delen) button. A side-panel appears. # Enter a non-KU Leuven email address in the '''Share with''' (Delen met) textfield. After filling the email address, press the enter key. # Make sure '''Full details''' (Volledige informatie) is selected in the dropdown next to your email address # Click the '''Send''' (Verzenden) button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> [[Category:Tutorials]] 809b362524eafd999655ea9f2f758d4c4df0d97e 908 906 2019-10-28T16:44:36Z Alexander 38 wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. # Set up agenda sync on KU Loket ## Visit [http://kuloket.be/ KU Loket] ## Go to the '''Education & Students''' (Onderwijs & studenten) tab [[File:KUL-Agenda-Step1.PNG|thumb|200px]] ## Click '''Agenda sync''' ## Click '''Configure agenda''' (Agenda instellen) [[File:KUL-Agenda-Step2.PNG|thumb|200px]] ## Change the switch '''Show schedule in my agenda''' (Toon uurrooster in mijn agenda) to '''On'''. [[File:KUL-Agenda-Step3.PNG|thumb|200px]] You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (Agenda) # On the top right (below the menu bar), click the '''Share''' (Delen) button. A side-panel appears. # Enter a non-KU Leuven email address in the '''Share with''' (Delen met) textfield. After filling the email address, press the enter key. # Make sure '''Full details''' (Volledige informatie) is selected in the dropdown next to your email address # Click the '''Send''' (Verzenden) button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> [[Category:Tutorials]] 09bb98bd162b9593f6535706153b48750286c10d 909 908 2019-10-28T16:45:52Z Alexander 38 wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. # Set up agenda sync on KU Loket ## Visit [http://kuloket.be/ KU Loket] ## Go to the '''Agenda Sync''' tab [[File:KUL-Agenda-Step1.PNG|thumb|200px]] ## Click '''Agenda sync''' ## Click '''Configure agenda''' (Agenda instellen) [[File:KUL-Agenda-Step2.PNG|thumb|200px]] ## Change the switch '''Show schedule in my agenda''' (Toon uurrooster in mijn agenda) to '''On'''. [[File:KUL-Agenda-Step3.PNG|thumb|200px]] You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (Agenda) # On the top right (below the menu bar), click the '''Share''' (Delen) button. A side-panel appears. # Enter a non-KU Leuven email address in the '''Share with''' (Delen met) textfield. After filling the email address, press the enter key. # Make sure '''Full details''' (Volledige informatie) is selected in the dropdown next to your email address # Click the '''Send''' (Verzenden) button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> [[Category:Tutorials]] 65f9866c12f8a6410212ec132c98ae06690bd351 910 909 2019-10-28T16:46:13Z Alexander 38 wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. # Set up agenda sync on KU Loket ## Visit [http://kuloket.be/ KU Loket] ## Go to the '''Agenda''' tab [[File:KUL-Agenda-Step1.PNG|thumb|200px]] ## Click '''Agenda sync''' ## Click '''Configure agenda''' (Agenda instellen) [[File:KUL-Agenda-Step2.PNG|thumb|200px]] ## Change the switch '''Show schedule in my agenda''' (Toon uurrooster in mijn agenda) to '''On'''. [[File:KUL-Agenda-Step3.PNG|thumb|200px]] You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (Agenda) # On the top right (below the menu bar), click the '''Share''' (Delen) button. A side-panel appears. # Enter a non-KU Leuven email address in the '''Share with''' (Delen met) textfield. After filling the email address, press the enter key. # Make sure '''Full details''' (Volledige informatie) is selected in the dropdown next to your email address # Click the '''Send''' (Verzenden) button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> [[Category:Tutorials]] 2ea7fde7937f32b65206e385bf27e242f08c4dcc 6 136 896 2019-10-28T16:27:08Z Alexander 38 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 137 901 2019-10-28T16:41:17Z Alexander 38 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 138 907 2019-10-28T16:44:14Z Alexander 38 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 20 911 735 2019-10-28T20:27:13Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you will need to download Wordpress from their own website, https://wordpress.org/download/. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. You will now have a folder named 'wordpress'. The folder 'wordpress', that you've just extracted, will need to be moved to your 'www' directory on our server. This can be accessed via SFTP. The best way to do this, is by using FileZilla (https://filezilla-project.org/). After installing this, you will have to move the 'wordpress' folder to our server. You can do this by entering '<code>sftp://ssh1.ulyssis.org</code>' or '<code>sftp://ssh2.ulyssis.org</code>' as host, with your username and password. You can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you have moved the 'wordpress' folder to in the 'www' directory, you have to go to your account <br> on *your username here*.ulyssis.be. There you will see the wordpress folder. After opening this you'll receive a message telling you to create a <code>wp-config.php</code> file. The easiest way to do this is by following the wizard. Go through to the wizard until it asks you for your database configuration: / *'''Database Name/Databasenaam:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll have to create by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is <code>mysql.ulyssis.org</code> or <code>postgresql.ulyssis.org</code>. It depends on whether you used a MySQL or PostgreSQL database. * You do not have to change the last field. After that you can proceed the wizard. When you wreceive a notification to log in, you have succesfully installed your own wordpress site. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you will need to create a new folder in your 'www' directory on your shell account. Then you'll need a virtual host for this folder, herefor you will have to send us an email asking for this. After your new virtual host has been configured, you will need to do the same steps that you would need to do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about it [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] c5230aa6f081521a1b02b997873c24d6247ff885 912 911 2019-10-29T14:27:53Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you will need to download Wordpress from their own website, https://wordpress.org/download/. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. You will now have a folder named 'wordpress'. Now you will have to be move the contents of the 'wordpress' folder to your 'www' directory on our server. This can be accessed via SFTP. The best way to do this, is by using FileZilla (https://filezilla-project.org/). Our server is located on these addresses: '<code>sftp://ssh1.ulyssis.org</code>' or '<code>sftp://ssh2.ulyssis.org</code>'. If you have any more questions, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you have moved the contents of the 'wordpress' folder in the 'www' directory, you have to go to your account <br> on *your username here*.ulyssis.be. There you will see the wordpress folder. After opening this you'll receive a message telling you to create a <code>wp-config.php</code> file. The easiest way to do this is by following the wizard. Go through to the wizard until it asks you for your database configuration: / *'''Database Name/Databasenaam:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll have to create by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is <code>mysql.ulyssis.org</code> or <code>postgresql.ulyssis.org</code>. It depends on whether you used a MySQL or PostgreSQL database. * You do not have to change the last field. After that you can proceed the wizard. When you wreceive a notification to log in, you have succesfully installed your own wordpress site. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you will need to create a new folder in your 'www' directory on your shell account. Then you'll need a virtual host for this folder, herefor you will have to send us an email asking for this. After your new virtual host has been configured, you will need to do the same steps that you would need to do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about it [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] c92c7a80b16f9d0ad1b95ba64eb6e08a15f4e5a5 913 912 2019-10-29T20:02:56Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you will need to download Wordpress from their own website, https://wordpress.org/download/. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. You will now have a folder named 'wordpress'. Now you will have to be move the contents of the 'wordpress' folder to your 'www' directory on our server. This can be accessed via SFTP. The best way to do this, is by using FileZilla (https://filezilla-project.org/). Our server is located on these addresses: '<code>sftp://ssh1.ulyssis.org</code>' or '<code>sftp://ssh2.ulyssis.org</code>'. If you have any more questions, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you have moved the contents of the 'wordpress' folder in the 'www' directory, you have to go to your account <br> on *your username here*.ulyssis.be. There you will see the wordpress folder. After opening this you'll receive a message telling you to create a <code>wp-config.php</code> file. The easiest way to do this is by following the wizard. Go through to the wizard until it asks you for your database configuration: / *'''Database Name/Databasenaam:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll have to create by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is <code>mysql.ulyssis.org</code> or <code>postgresql.ulyssis.org</code>. It depends on whether you used a MySQL or PostgreSQL database. * You do not have to change the last field. So it will look something like this: After that you can proceed the wizard. When you wreceive a notification to log in, you have succesfully installed your own wordpress site. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you will need to create a new folder in your 'www' directory on your shell account. Then you'll need a virtual host for this folder, herefor you will have to send us an email asking for this. After your new virtual host has been configured, you will need to do the same steps that you would need to do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about it [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 386a99dab9184ec0496e020765a5cb5578db6476 915 913 2019-10-29T20:06:45Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you will need to download Wordpress from their own website, https://wordpress.org/download/. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. You will now have a folder named 'wordpress'. Now you will have to be move the contents of the 'wordpress' folder to your 'www' directory on our server. This can be accessed via SFTP. The best way to do this, is by using FileZilla (https://filezilla-project.org/). Our server is located on these addresses: '<code>sftp://ssh1.ulyssis.org</code>' or '<code>sftp://ssh2.ulyssis.org</code>'. If you have any more questions, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you have moved the contents of the 'wordpress' folder in the 'www' directory, you have to go to your account <br> on *your username here*.ulyssis.be. There you will see the wordpress folder. After opening this you'll receive a message telling you to create a <code>wp-config.php</code> file. The easiest way to do this is by following the wizard. Go through to the wizard until it asks you for your database configuration: / *'''Database Name/Databasenaam:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll have to create by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is <code>mysql.ulyssis.org</code> or <code>postgresql.ulyssis.org</code>. It depends on whether you used a MySQL or PostgreSQL database. * You do not have to change the last field.<br> So it will look something like this:<br> [[File:Wordpress server.png|thumb|left]]<br> After that you can proceed the wizard. When you wreceive a notification to log in, you have succesfully installed your own wordpress site. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you will need to create a new folder in your 'www' directory on your shell account. Then you'll need a virtual host for this folder, herefor you will have to send us an email asking for this. After your new virtual host has been configured, you will need to do the same steps that you would need to do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about it [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 1245d36a59ef7c43a2508a4e78ed665e780d3db1 916 915 2019-10-29T20:08:34Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you will need to download Wordpress from their own website, https://wordpress.org/download/. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. You will now have a folder named 'wordpress'. Now you will have to be move the contents of the 'wordpress' folder to your 'www' directory on our server. This can be accessed via SFTP. The best way to do this, is by using FileZilla (https://filezilla-project.org/). Our server is located on these addresses: '<code>sftp://ssh1.ulyssis.org</code>' or '<code>sftp://ssh2.ulyssis.org</code>'. If you have any more questions, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you have moved the contents of the 'wordpress' folder in the 'www' directory, you have to go to your account <br> on *your username here*.ulyssis.be. There you will see the wordpress folder. After opening this you'll receive a message telling you to create a <code>wp-config.php</code> file. The easiest way to do this is by following the wizard. Go through to the wizard until it asks you for your database configuration: / *'''Database Name/Databasenaam:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll have to create by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is <code>mysql.ulyssis.org</code> or <code>postgresql.ulyssis.org</code>. It depends on whether you used a MySQL or PostgreSQL database. * You do not have to change the last field.<br> So it will look something like this (click to enhance picture):<br> [[File:Wordpress server.png|thumb|left]]<br> After that you can proceed the wizard. When you wreceive a notification to log in, you have succesfully installed your own wordpress site. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you will need to create a new folder in your 'www' directory on your shell account. Then you'll need a virtual host for this folder, herefor you will have to send us an email asking for this. After your new virtual host has been configured, you will need to do the same steps that you would need to do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about it [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] ec72e66a07613ad6c95ff4418b16cf01a1588c7b 917 916 2019-10-29T20:12:39Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you will need to download Wordpress from their own website, https://wordpress.org/download/. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. You will now have a folder named 'wordpress'. Now you will have to be move the contents of the 'wordpress' folder to your 'www' directory on our server. This can be accessed via SFTP. The best way to do this, is by using FileZilla (https://filezilla-project.org/). Our server is located on these addresses: '<code>sftp://ssh1.ulyssis.org</code>' or '<code>sftp://ssh2.ulyssis.org</code>'. If you have any more questions, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you have moved the contents of the 'wordpress' folder in the 'www' directory, you have to go to your account <br> on *your username here*.ulyssis.be. There you will see the wordpress folder. After opening this you'll receive a message telling you to create a <code>wp-config.php</code> file. The easiest way to do this is by following the wizard. Go through to the wizard until it asks you for your database configuration: / *'''Database Name/Databasenaam:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll have to create by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is <code>mysql.ulyssis.org</code> or <code>postgresql.ulyssis.org</code>. It depends on whether you used a MySQL or PostgreSQL database. * You do not have to change the last field.<br> So it will look something like this (click to enhance picture):<br> [[File:Wordpress server.png|thumb|left|600px]]<br> After that you can proceed the wizard. When you wreceive a notification to log in, you have succesfully installed your own wordpress site. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you will need to create a new folder in your 'www' directory on your shell account. Then you'll need a virtual host for this folder, herefor you will have to send us an email asking for this. After your new virtual host has been configured, you will need to do the same steps that you would need to do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about it [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 8f8a5bc486eb70ea36d5a75b44830f821c76951b 918 917 2019-10-29T20:12:52Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you will need to download Wordpress from their website, https://wordpress.org/download/. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. You will now have a folder named 'wordpress'. Now you will have to be move the contents of the 'wordpress' folder to your 'www' directory on our server. This can be accessed via SFTP. The best way to do this, is by using FileZilla (https://filezilla-project.org/). Our server is located on these addresses: '<code>sftp://ssh1.ulyssis.org</code>' or '<code>sftp://ssh2.ulyssis.org</code>'. If you have any more questions, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you have moved the contents of the 'wordpress' folder in the 'www' directory, you have to go to your account <br> on *your username here*.ulyssis.be. There you will see the wordpress folder. After opening this you'll receive a message telling you to create a <code>wp-config.php</code> file. The easiest way to do this is by following the wizard. Go through to the wizard until it asks you for your database configuration: / *'''Database Name/Databasenaam:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll have to create by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is <code>mysql.ulyssis.org</code> or <code>postgresql.ulyssis.org</code>. It depends on whether you used a MySQL or PostgreSQL database. * You do not have to change the last field.<br> So it will look something like this (click to enhance picture):<br> [[File:Wordpress server.png|thumb|left|600px]]<br> After that you can proceed the wizard. When you wreceive a notification to log in, you have succesfully installed your own wordpress site. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you will need to create a new folder in your 'www' directory on your shell account. Then you'll need a virtual host for this folder, herefor you will have to send us an email asking for this. After your new virtual host has been configured, you will need to do the same steps that you would need to do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about it [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] ca92d99be1e70a73c9f79fab69af29b9db73bdc1 919 918 2019-10-29T20:15:02Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you will need to download Wordpress from their website, https://wordpress.org/download/. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. You will now have a folder named 'wordpress'. Now you will have to be move the contents of the 'wordpress' folder to your 'www' directory on our server. This can be accessed via SFTP. The best way to do this, is by using FileZilla (https://filezilla-project.org/). Our server is located on these addresses: '<code>sftp://ssh1.ulyssis.org</code>' or '<code>sftp://ssh2.ulyssis.org</code>'. If you have any more questions, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you have moved the contents of the 'wordpress' folder in the 'www' directory, you have to go to your account <br> on *your username here*.ulyssis.be. There you will see the wordpress folder. After opening this you'll receive a message telling you to create a <code>wp-config.php</code> file. The easiest way to do this is by following the wizard. Go through to the wizard until it asks you for your database configuration: / *'''Database Name/Databasenaam:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll have to create by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is <code>mysql.ulyssis.org</code> or <code>postgresql.ulyssis.org</code>. It depends on whether you used a MySQL or PostgreSQL database. *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this (click to enhance picture):<br> [[File:Wordpress server.png|thumb|left|600px]]<br> After that you can proceed the wizard. When you wreceive a notification to log in, you have succesfully installed your own wordpress site. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you will need to create a new folder in your 'www' directory on your shell account. Then you'll need a virtual host for this folder, herefor you will have to send us an email asking for this. After your new virtual host has been configured, you will need to do the same steps that you would need to do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about it [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 009799b389c4cdcdfe12e6e802480d209fcfe8bf 920 919 2019-10-29T20:19:55Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you will need to download Wordpress from their website, https://wordpress.org/download/. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. You will now have a folder named 'wordpress'. Now you will have to be move the contents of the 'wordpress' folder to your 'www' directory on our server. This can be accessed via SFTP. The best way to do this, is by using FileZilla (https://filezilla-project.org/). Our server is located on these addresses: '<code>sftp://ssh1.ulyssis.org</code>' or '<code>sftp://ssh2.ulyssis.org</code>'. If you have any more questions, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you have moved the contents of the 'wordpress' folder in the 'www' directory, you have to go to your account <br> on *your username here*.ulyssis.be. There you will see the wordpress folder. After opening this you'll receive a message telling you to create a <code>wp-config.php</code> file. The easiest way to do this is by following the wizard. Go through to the wizard until it asks you for your database configuration: *'''Database Name/Databasenaam:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll have to create by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is <code>mysql.ulyssis.org</code> or <code>postgresql.ulyssis.org</code>. It depends on whether you used a MySQL or PostgreSQL database. *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this (click to enhance picture):<br> [[File:Wordpress server.png|thumb|left|600px]]<br> After that you can proceed the wizard. When you wreceive a notification to log in, you have succesfully installed your own wordpress site. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you will need to create a new folder in your 'www' directory on your shell account. Then you'll need a virtual host for this folder, herefor you will have to send us an email asking for this. After your new virtual host has been configured, you will need to do the same steps that you would need to do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about it [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] df3e8c0b228c6bb87ee471d9ffd58a5bf6532a30 921 920 2019-10-29T20:20:38Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you will need to download Wordpress from their website, https://wordpress.org/download/. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. You will now have a folder named 'wordpress'. Now you will have to be move the contents of the 'wordpress' folder to your 'www' directory on our server. This can be accessed via SFTP. The best way to do this, is by using FileZilla (https://filezilla-project.org/). Our server is located on these addresses: '<code>sftp://ssh1.ulyssis.org</code>' or '<code>sftp://ssh2.ulyssis.org</code>'. If you have any more questions, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you have moved the contents of the 'wordpress' folder in the 'www' directory, you have to go to your account <br> on *your username here*.ulyssis.be. There you will see the wordpress folder. After opening this you'll receive a message telling you to create a <code>wp-config.php</code> file. The easiest way to do this is by following the wizard. Continue the wizard until it asks you for your database configuration: *'''Database Name/Databasenaam:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll have to create by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is <code>mysql.ulyssis.org</code> or <code>postgresql.ulyssis.org</code>. It depends on whether you used a MySQL or PostgreSQL database. *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this (click to enhance picture):<br> [[File:Wordpress server.png|thumb|left|600px]]<br> After that you can proceed the wizard. When you wreceive a notification to log in, you have succesfully installed your own wordpress site. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you will need to create a new folder in your 'www' directory on your shell account. Then you'll need a virtual host for this folder, herefor you will have to send us an email asking for this. After your new virtual host has been configured, you will need to do the same steps that you would need to do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about it [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] e191ac25203a61dfdf89f8a1867776bd2671cab7 922 921 2019-10-29T20:21:16Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you will need to download Wordpress from their website, https://wordpress.org/download/. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. You will now have a folder named 'wordpress'. Now you will have to be move the contents of the 'wordpress' folder to your 'www' directory on our server. This can be accessed via SFTP. The best way to do this, is by using FileZilla (https://filezilla-project.org/). Our server is located on these addresses: '<code>sftp://ssh1.ulyssis.org</code>' or '<code>sftp://ssh2.ulyssis.org</code>'. If you have any more questions, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you have moved the contents of the 'wordpress' folder in the 'www' directory, you have to go to your account <br> on *your username here*.ulyssis.be. There you will see the wordpress folder. After opening this you'll receive a message telling you to create a <code>wp-config.php</code> file. The easiest way to do this is by following the wizard. Continue the wizard until it asks you for your database configuration: *'''Database Name/Databasenaam:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll have to create by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is <code>mysql.ulyssis.org</code> or <code>postgresql.ulyssis.org</code>. It depends on whether you used a MySQL or PostgreSQL database. *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:Wordpress server.png|thumb|left|600px]]<br> After that you can proceed the wizard. When you wreceive a notification to log in, you have succesfully installed your own wordpress site. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you will need to create a new folder in your 'www' directory on your shell account. Then you'll need a virtual host for this folder, herefor you will have to send us an email asking for this. After your new virtual host has been configured, you will need to do the same steps that you would need to do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about it [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 3be13f4db6bce9a777b7cd24e2fcb8faddb4ac1f 6 139 914 2019-10-29T20:03:21Z Casper 39 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 20 923 922 2019-10-29T20:22:10Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you will need to download Wordpress from their website, https://wordpress.org/download/. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. You will now have a folder named 'wordpress'. Now you will have to be move the contents of the 'wordpress' folder to your 'www' directory on our server. This can be accessed via SFTP. The best way to do this, is by using FileZilla (https://filezilla-project.org/). Our server is located on these addresses: '<code>sftp://ssh1.ulyssis.org</code>' or '<code>sftp://ssh2.ulyssis.org</code>'. If you have any more questions, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you have moved the contents of the 'wordpress' folder in the 'www' directory, you have to go to your account <br> on *your username here*.ulyssis.be. There you will see the wordpress folder. After opening this you'll receive a message telling you to create a <code>wp-config.php</code> file. The easiest way to do this is by following the wizard. Continue the wizard until it asks you for your database configuration: *'''Database Name/Databasenaam:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll have to create by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is <code>mysql.ulyssis.org</code> or <code>postgresql.ulyssis.org</code>. It depends on whether you used a MySQL or PostgreSQL database. *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:Wordpress server.png|thumb|left|600px]]<br> After that you can proceed the wizard. When you receive a notification to log in, you have succesfully installed your own wordpress site. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you will need to create a new folder in your 'www' directory on your shell account. Then you'll need a virtual host for this folder, herefor you will have to send us an email asking for this. After your new virtual host has been configured, you will need to do the same steps that you would need to do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about it [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] e1d5f8468d768e77d750872618a742c8815491c9 924 923 2019-10-29T20:22:34Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you will need to download Wordpress from their website, https://wordpress.org/download/. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. You will now have a folder named 'wordpress'. Now you will have to move the contents of the 'wordpress' folder to your 'www' directory on our server. This can be accessed via SFTP. The best way to do this, is by using FileZilla (https://filezilla-project.org/). Our server is located on these addresses: '<code>sftp://ssh1.ulyssis.org</code>' or '<code>sftp://ssh2.ulyssis.org</code>'. If you have any more questions, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you have moved the contents of the 'wordpress' folder in the 'www' directory, you have to go to your account <br> on *your username here*.ulyssis.be. There you will see the wordpress folder. After opening this you'll receive a message telling you to create a <code>wp-config.php</code> file. The easiest way to do this is by following the wizard. Continue the wizard until it asks you for your database configuration: *'''Database Name/Databasenaam:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll have to create by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is <code>mysql.ulyssis.org</code> or <code>postgresql.ulyssis.org</code>. It depends on whether you used a MySQL or PostgreSQL database. *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:Wordpress server.png|thumb|left|600px]]<br> After that you can proceed the wizard. When you receive a notification to log in, you have succesfully installed your own wordpress site. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you will need to create a new folder in your 'www' directory on your shell account. Then you'll need a virtual host for this folder, herefor you will have to send us an email asking for this. After your new virtual host has been configured, you will need to do the same steps that you would need to do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about it [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] d3c4e498f6d2534de21a94d9dac35c74a4be2e75 925 924 2019-10-29T20:23:13Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you will need to download Wordpress from their website, https://wordpress.org/download/. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. You will now have a folder named 'wordpress'. Now you will have to move the contents of the 'wordpress' directory to your 'www' directory on our server. This can be accessed via SFTP. The best way to do this, is by using FileZilla (https://filezilla-project.org/). Our server is located on these addresses: '<code>sftp://ssh1.ulyssis.org</code>' or '<code>sftp://ssh2.ulyssis.org</code>'. If you have any more questions, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you have moved the contents of the 'wordpress' folder in the 'www' directory, you have to go to your account <br> on *your username here*.ulyssis.be. There you will see the wordpress folder. After opening this you'll receive a message telling you to create a <code>wp-config.php</code> file. The easiest way to do this is by following the wizard. Continue the wizard until it asks you for your database configuration: *'''Database Name/Databasenaam:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll have to create by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is <code>mysql.ulyssis.org</code> or <code>postgresql.ulyssis.org</code>. It depends on whether you used a MySQL or PostgreSQL database. *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:Wordpress server.png|thumb|left|600px]]<br> After that you can proceed the wizard. When you receive a notification to log in, you have succesfully installed your own wordpress site. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you will need to create a new folder in your 'www' directory on your shell account. Then you'll need a virtual host for this folder, herefor you will have to send us an email asking for this. After your new virtual host has been configured, you will need to do the same steps that you would need to do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about it [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] f8fd45b357d5db84d5994950bc0a02e3c9e44016 926 925 2019-10-29T20:44:13Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you will need to download Wordpress from their website, https://wordpress.org/download/. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. You will now have a folder named 'wordpress'. Now you will have to move the contents of the 'wordpress' directory to your 'www' directory on our server. This can be accessed via SFTP. The best way to do this, is by using FileZilla (https://filezilla-project.org/). Our server is located on these addresses: '<code>sftp://ssh1.ulyssis.org</code>' or '<code>sftp://ssh2.ulyssis.org</code>'. If you have any more questions, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you have moved the contents of the 'wordpress' folder in the 'www' directory, you have to go to your account <br> on *your username here*.ulyssis.be. There you will see the wordpress folder. After opening this you'll receive a message telling you to create a <code>wp-config.php</code> file. The easiest way to do this is by following the wizard. Continue the wizard until it asks you for your database configuration: *'''Database Name/Databasenaam:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll have to create by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code>. *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:Wordpress server.png|thumb|left|600px]]<br> After that you can proceed the wizard. When you receive a notification to log in, you have succesfully installed your own wordpress site. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you will need to create a new folder in your 'www' directory on your shell account. Then you'll need a virtual host for this folder, herefor you will have to send us an email asking for this. After your new virtual host has been configured, you will need to do the same steps that you would need to do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about it [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 42f4d3f22da6c9906d691e0dec7ebd941f5fad2c 927 926 2019-10-29T20:44:50Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you will need to download Wordpress from their website, https://wordpress.org/download/. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. You will now have a folder named 'wordpress'. Now you will have to move the contents of the 'wordpress' directory to your 'www' directory on our server. This can be accessed via SFTP. The best way to do this, is by using FileZilla (https://filezilla-project.org/). Our server is located on these addresses: '<code>sftp://ssh1.ulyssis.org</code>' or '<code>sftp://ssh2.ulyssis.org</code>'. If you have any more questions, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you have moved the contents of the 'wordpress' folder in the 'www' directory, you have to go to your account <br> on *your username here*.ulyssis.be. There you will see the wordpress folder. After opening this you'll receive a message telling you to create a <code>wp-config.php</code> file. The easiest way to do this is by following the wizard. Continue the wizard until it asks you for your database configuration: *'''Database Name/Databasenaam:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll have to create by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:Wordpress server.png|thumb|left|600px]]<br> After that you can proceed the wizard. When you receive a notification to log in, you have succesfully installed your own wordpress site. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you will need to create a new folder in your 'www' directory on your shell account. Then you'll need a virtual host for this folder, herefor you will have to send us an email asking for this. After your new virtual host has been configured, you will need to do the same steps that you would need to do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about it [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 972ba9c73149f3d1f08ff5a4125f023e435868a4 929 927 2019-10-30T07:06:43Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you will need to download Wordpress from their website, https://wordpress.org/download/. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. You will now have a folder named 'wordpress'. Now you will have to move the contents of the 'wordpress' directory to your 'www' directory on our server. This can be accessed via SFTP. The best way to do this, is by using FileZilla (https://filezilla-project.org/). Our server is located on these addresses: '<code>sftp://ssh1.ulyssis.org</code>' or '<code>sftp://ssh2.ulyssis.org</code>'. If you have any more questions, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you have moved the contents of the 'wordpress' folder in the 'www' directory, you have to go to your account <br> on *your username here*.ulyssis.be. There you will see the wordpress folder. After opening this you'll receive a message telling you to create a <code>wp-config.php</code> file. The easiest way to do this is by following the wizard. Continue the wizard until it asks you for your database configuration: *'''Database Name/Databasenaam:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll have to create by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> After that you can proceed the wizard. When you receive a notification to log in, you have succesfully installed your own wordpress site. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you will need to create a new folder in your 'www' directory on your shell account. Then you'll need a virtual host for this folder, herefor you will have to send us an email asking for this. After your new virtual host has been configured, you will need to do the same steps that you would need to do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about it [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 39d34656412f499a705c4e7145d4328dafd1fe6d 930 929 2019-10-30T07:07:48Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you will need to download Wordpress from their website, https://wordpress.org/download/. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. You will now have a folder named 'wordpress'. Now you will have to move the contents of the 'wordpress' directory to your 'www' directory on our server. This can be accessed via SFTP. The best way to do this, is by using FileZilla (https://filezilla-project.org/). Our server is located on these addresses: '<code>sftp://ssh1.ulyssis.org</code>' or '<code>sftp://ssh2.ulyssis.org</code>'. If you have any more questions, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you have moved the contents of the 'wordpress' folder in the 'www' directory, you have to go to your account <br> on *your username here*.ulyssis.be. There you will see the wordpress folder. After opening this you'll receive a message telling you to create a <code>wp-config.php</code> file. The easiest way to do this is by following the wizard. Continue the wizard until it asks you for your database configuration: *'''Database Name/Databasenaam:''' If you haven't created a MySQL database/user on UCC, then you'll have to create by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> After that you can proceed the wizard. When you receive a notification to log in, you have succesfully installed your own wordpress site. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you will need to create a new folder in your 'www' directory on your shell account. Then you'll need a virtual host for this folder, herefor you will have to send us an email asking for this. After your new virtual host has been configured, you will need to do the same steps that you would need to do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about it [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] b909bc99d1511c431d0c64722b014dbe9fa5f492 931 930 2019-10-30T09:19:39Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you will need to download Wordpress from their website, https://wordpress.org/download/. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. Now you will have a folder named 'wordpress'. Now you will have to move the contents of the 'wordpress' directory to your 'www' directory on our server. This can be accessed via SFTP. The best way to do this, is by using FileZilla (https://filezilla-project.org/). Our server is located on these addresses: '<code>sftp://ssh1.ulyssis.org</code>' or '<code>sftp://ssh2.ulyssis.org</code>'. If you have any more questions about this, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you have moved the contents of the 'wordpress' folder in the 'www' directory, you have to go to your account <br> on *your username here*.ulyssis.be. Here you will need to setup your website. You'll receive a message telling you to create a <code>wp-config.php</code> file. The easiest way to do this is by following the wizard. Continue the wizard until it asks you for your database configuration: *'''Database Name/Databasenaam:''' If you haven't created a MySQL database/user on UCC, then you'll have to create by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> After that you can proceed the wizard. When you receive a notification to log in, you have succesfully installed your own wordpress site. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you will need to create a new folder in your 'www' directory on your shell account. Then you'll need a virtual host for this folder, herefor you will have to send us an email asking for this. After your new virtual host has been configured, you will need to do the same steps that you would need to do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about it [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 9e1f546d5fc162450aa6f9826441e9f9de40e055 932 931 2019-10-30T09:23:23Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you will need to download Wordpress from their website, https://wordpress.org/download/. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. Now you will have a directory named 'wordpress'. Now you will have to move the contents of the 'wordpress' directory to your 'www' directory on our server. This can be accessed via SFTP. The best way to do this, is by using FileZilla (https://filezilla-project.org/). Our server is located on these addresses: '<code>sftp://ssh1.ulyssis.org</code>' or '<code>sftp://ssh2.ulyssis.org</code>'. If you have any more questions about this, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you have moved the contents of the 'wordpress' folder in the 'www' directory, you have to go to your account <br> on *your username here*.ulyssis.be. Here you will need to setup your website. You'll receive a message telling you to create a <code>wp-config.php</code> file. The easiest way to do this is by following the wizard. Continue the wizard until it asks you for your database configuration: *'''Database Name/Databasenaam:''' If you haven't created a MySQL database/user on UCC, then you'll have to create by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> After that you can proceed the wizard. When you receive a notification to log in, you have succesfully installed your own wordpress site. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you will need to create a new folder in your 'www' directory on your shell account. Then you'll need a virtual host for this folder, herefor you will have to send us an email asking for this. After your new virtual host has been configured, you will need to do the same steps that you would need to do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about it [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 711bb6625f991239ef81bff942b7c9a35fb3877e 933 932 2019-10-30T09:25:02Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you will need to download Wordpress from their website, https://wordpress.org/download/. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. Now you will have a directory named 'wordpress'. Now you will have to move the contents of the 'wordpress' directory to your 'www' directory on our server. This can be accessed via SFTP. The best way to do this, is by using FileZilla (https://filezilla-project.org/). Our server is located on these addresses: '<code>sftp://ssh1.ulyssis.org</code>' or '<code>sftp://ssh2.ulyssis.org</code>'. If you have any more questions about this, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you have moved the contents of the 'wordpress' folder in the 'www' directory, you have to go to your account <br> on *your username here*.ulyssis.be. Here you will need to setup your website. The easiest way to do this, is by following the wizard. Continue the wizard until it asks you for your database configuration: *'''Database Name/Databasenaam:''' If you haven't created a MySQL database/user on UCC, then you'll have to create by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> After that you can proceed the wizard. When you receive a notification to log in, you have succesfully installed your own wordpress site. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you will need to create a new folder in your 'www' directory on your shell account. Then you'll need a virtual host for this folder, herefor you will have to send us an email asking for this. After your new virtual host has been configured, you will need to do the same steps that you would need to do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about it [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 507f2ee40182d22c3001aa16178cfad83150d281 934 933 2019-10-30T09:25:43Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you will need to download Wordpress from their website, https://wordpress.org/download/. You will receive a compressed file (.tar.gz or .zip) that you'll have to extract. Now you will have a directory named 'wordpress'. Now you will have to move the contents of the 'wordpress' directory to your 'www' directory on our server. This can be accessed via SFTP. The best way to do this, is by using FileZilla (https://filezilla-project.org/). Our server is located on these addresses: '<code>sftp://ssh1.ulyssis.org</code>' or '<code>sftp://ssh2.ulyssis.org</code>'. If you have any more questions about this, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you have moved the contents of the 'wordpress' folder in the 'www' directory, you have to go to your account <br> on *your username here*.ulyssis.be. Here you will need to setup your website. The easiest way to do this, is by following the wizard. Continue until the wizard asks you for your database configuration: *'''Database Name/Databasenaam:''' If you haven't created a MySQL database/user on UCC, then you'll have to create by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> After that you can proceed the wizard. When you receive a notification to log in, you have succesfully installed your own wordpress site. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you will need to create a new folder in your 'www' directory on your shell account. Then you'll need a virtual host for this folder, herefor you will have to send us an email asking for this. After your new virtual host has been configured, you will need to do the same steps that you would need to do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. You can find more help about it [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] c98bfa3eabcc40d2d792fc10dc79982f0140f8ee 935 934 2019-10-30T10:33:24Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you will have to download Wordpress from their website, https://wordpress.org/download/. Now you receive a compressed file (.tar.gz or .zip) that you need to extract. This will give you a directory named 'wordpress'. Now you have to move the contents of the 'wordpress' directory to your 'www' directory on our server, which can be accessed via SFTP. The best way to do this, is by using FileZilla (https://filezilla-project.org/). Our server is located on these addresses: '<code>sftp://ssh1.ulyssis.org</code>' or '<code>sftp://ssh2.ulyssis.org</code>'. If you have any more questions about this, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you moved the contents of the 'wordpress' folder in the 'www' directory, you need to go to your account <br> on *your username here*.ulyssis.be. Here you have to setup your website. The easiest way to do this, is by following the wizard. Continue until the wizard asks you for your database configuration: *'''Database Name/Databasenaam:''' If you haven't created a MySQL database/user on UCC, then you'll have to create one by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> After this, you can proceed the wizard. When you receive a notification to log in, you succesfully installed your own wordpress site. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you need to create a new folder in your 'www' directory on your shell account. Then you need a virtual host for this folder, herefor you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 8b96eaf19b02e892fc9be1a1ce9d90c1506e7768 936 935 2019-10-30T11:14:37Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you will have to download Wordpress from their website, https://wordpress.org/download/. You now receive a compressed file (.tar.gz or .zip) that you need to extract. This will give you a directory named 'wordpress'. Next, you have to move the contents of the 'wordpress' directory to your 'www' directory on our server, which can be accessed via SFTP. If you would have any more questions about this, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you moved the contents of the 'wordpress' folder in the 'www' directory, you need to go to your account <br> on *your username here*.ulyssis.be. This is where you have to setup your website. The easiest way to do this, is by following the wizard. Continue until the wizard asks you for your database configuration: *'''Database Name/Databasenaam:''' If you haven't created a MySQL database/user on UCC, then you'll have to create one by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> Afterwards, you can proceed the wizard. At a certain point, you receive a notification to log in on wordpress. This means you have succesfully installed your own wordpress site. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you need to create a new folder in your 'www' directory on your shell account. Then you need a virtual host for this folder, herefor you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 2a993ff9e22f405129f3ef18b5a3cac3419b0408 937 936 2019-10-30T11:40:04Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you will have to download Wordpress from their website, https://wordpress.org/download/. You now receive a compressed file (.tar.gz or .zip) that you need to extract, it will give you a directory named 'wordpress'. Next, you have to move the contents of the 'wordpress' directory to your 'www' directory on our server, which can be accessed via SFTP. If you would have any more questions about this, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you moved the contents of the 'wordpress' folder in the 'www' directory, you need to go to your account <br> on *your username here*.ulyssis.be. This is where you have to setup your website. The easiest way to do this, is by following the wizard. Continue until the wizard asks you for your database configuration: *'''Database Name/Databasenaam:''' If you haven't created a MySQL database/user on UCC, then you'll have to create one by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> Afterwards, you can proceed the wizard. At a certain point, you receive a notification to log in on wordpress. This means you have succesfully installed your own wordpress site. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you need to create a new folder in your 'www' directory on your shell account. Then you need a virtual host for this folder, herefor you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 990b1e3a5b7d972d60b8b9837a10cd760195ea0c 938 937 2019-10-30T11:40:34Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you will have to download Wordpress from their website, https://wordpress.org/download/. You now receive a compressed file (.tar.gz or .zip) that you need to extract, it will give you a directory named 'wordpress'. Next, you have to move the contents of the 'wordpress' directory to your 'www' directory on our server, which can be accessed via SFTP. If you would have any more questions about this, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you moved the contents of the 'wordpress' folder into the 'www' directory, you need to go to your account <br> on *your username here*.ulyssis.be. This is where you have to setup your website. The easiest way to do this, is by following the wizard. Continue until the wizard asks you for your database configuration: *'''Database Name/Databasenaam:''' If you haven't created a MySQL database/user on UCC, then you'll have to create one by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> Afterwards, you can proceed the wizard. At a certain point, you receive a notification to log in on wordpress. This means you have succesfully installed your own wordpress site. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you need to create a new folder in your 'www' directory on your shell account. Then you need a virtual host for this folder, herefor you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 4db2d9ada720370fa43da9efd8c44fd2ce615172 951 938 2019-11-02T21:11:00Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you will have to download Wordpress from their website, https://wordpress.org/download/. You now receive a compressed file (.tar.gz or .zip) that you need to extract, it will give you a directory named 'wordpress'. Next, you have to move the contents of the 'wordpress' directory to your 'www' directory on our server, which can be accessed via SFTP. If you would have any more questions about this, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you moved the contents of the 'wordpress' folder into the 'www' directory, you need to go to your account <br> on *your username here*.ulyssis.be. This is where you have to set up your website. The easiest way to do this, is by following the wizard. Continue until the wizard asks you for your database configuration: *'''Database Name/Databasenaam:''' If you haven't created a MySQL database/user on UCC, then you'll have to create one by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> Afterwards, you can proceed the installation. At a certain point, you receive a notification to log in on wordpress. This means you have succesfully installed your own wordpress website. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you need to create a new folder in your 'www' directory on your shell account. Then you need a virtual host for this folder, herefor you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 46dc3c12f6632b1a62889a0123b9eec8ee1197bb 953 951 2019-11-03T16:42:42Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you need to download Wordpress from their website, https://wordpress.org/download/. You now receive a compressed file zip file that you have to extract (Windows: use right-click and extract zip file; OSX: double-click the zip file, it automatically extracts; Linux: right-click the file, and select 'extract here'), this gives you a directory named 'wordpress'. Next, you have to move the contents of the 'wordpress' directory to your 'www' directory on our server, which can be accessed via SFTP. If you would have any more questions about this, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you moved the contents of the 'wordpress' folder into the 'www' directory, you need to go to your account <br> on *your username here*.ulyssis.be. This is where you have to set up your website. The easiest way to do this, is by following the wizard. Continue until the wizard asks you for your database configuration: *'''Database Name/Databasenaam:''' If you haven't created a MySQL database/user on UCC, then you'll have to create one by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> Afterwards, you can proceed the installation. At a certain point, you receive a notification to log in on wordpress. This means you have succesfully installed your own wordpress website. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you need to create a new folder in your 'www' directory on your shell account. Then you need a virtual host for this folder, herefor you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 5f0580bf7980665cb9f17faa07de6069c1a35de0 954 953 2019-11-03T16:48:12Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you need to download Wordpress from their website, https://wordpress.org/download/. You now receive a compressed file zip file that you have to extract (Windows: use right-click and select "extract all"; OSX: double-click the zip file, it automatically extracts; Linux: right-click the file, and select "extract here"), this gives you a directory named 'wordpress'. Next, you have to move the contents of the 'wordpress' directory to your 'www' directory on our server, which can be accessed via SFTP. If you would have any more questions about this, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you moved the contents of the 'wordpress' folder into the 'www' directory, you need to go to your account <br> on *your username here*.ulyssis.be. This is where you have to set up your website. The easiest way to do this, is by following the wizard. Continue until the wizard asks you for your database configuration: *'''Database Name/Databasenaam:''' If you haven't created a MySQL database/user on UCC, then you'll have to create one by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> Afterwards, you can proceed the installation. At a certain point, you receive a notification to log in on wordpress. This means you have succesfully installed your own wordpress website. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you need to create a new folder in your 'www' directory on your shell account. Then you need a virtual host for this folder, herefor you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 9d0bdcbc91018aa1d32263e3debb785997f747b1 955 954 2019-11-03T16:59:22Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you need to download Wordpress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip file, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named 'wordpress'. Next, you have to move the ''contents'' of the 'wordpress' directory to your 'www' directory on our server, which can be accessed via SFTP. If you would have any more questions about this, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you moved the contents of the 'wordpress' folder into the 'www' directory, you need to go to your account <br> on *your username here*.ulyssis.be. This is where you have to set up your website. The easiest way to do this, is by following the wizard. Continue until the wizard asks you for your database configuration: *'''Database Name/Databasenaam:''' If you haven't created a MySQL database/user on UCC, then you'll have to create one by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> Afterwards, you can proceed the installation. At a certain point, you receive a notification to log in on wordpress. This means you have succesfully installed your own wordpress website. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you need to create a new folder in your 'www' directory on your shell account. Then you need a virtual host for this folder, herefor you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 3958d74a5c20810c0392ad2001e844b6583b6410 956 955 2019-11-03T17:00:07Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you need to download Wordpress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip file, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named 'wordpress'. Next, you have to move the '''contents''' of the 'wordpress' directory to your 'www' directory on our server, which can be accessed via SFTP. If you would have any more questions about this, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you moved the contents of the 'wordpress' folder into the 'www' directory, you need to go to your account <br> on *your username here*.ulyssis.be. This is where you have to set up your website. The easiest way to do this, is by following the wizard. Continue until the wizard asks you for your database configuration: *'''Database Name/Databasenaam:''' If you haven't created a MySQL database/user on UCC, then you'll have to create one by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> Afterwards, you can proceed the installation. At a certain point, you receive a notification to log in on wordpress. This means you have succesfully installed your own wordpress website. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you need to create a new folder in your 'www' directory on your shell account. Then you need a virtual host for this folder, herefor you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 60ba48a2bbf39050e7d88d7a662db041412ad003 957 956 2019-11-03T17:12:56Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you need to download Wordpress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named 'wordpress'. Next, you have to move the '''contents''' of the 'wordpress' directory to your 'www' directory on our server, which can be accessed via SFTP. If you would have any more questions about this, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you moved the contents of the 'wordpress' folder into the 'www' directory, you need to go to your account <br> on *your username here*.ulyssis.be. This is where you have to set up your website. The easiest way to do this, is by following the wizard. Continue until the wizard asks you for your database configuration: *'''Database Name/Databasenaam:''' If you haven't created a MySQL database/user on UCC, then you'll have to create one by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> Afterwards, you can proceed the installation. At a certain point, you receive a notification to log in on wordpress. This means you have succesfully installed your own wordpress website. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you need to create a new folder in your 'www' directory on your shell account. Then you need a virtual host for this folder, herefor you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 252c7eeb5c2e474f180e67ace57e50f194b5e90f 958 957 2019-11-03T17:14:52Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you need to download Wordpress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named 'wordpress'. Next, you have to move the '''contents''' of the 'wordpress' directory to your 'www' directory on our server, which can be accessed via SFTP. If you would have any more questions about this, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you moved the contents of the 'wordpress' folder into the 'www' directory, you need to go to your account <br> on <code>*your username here*.ulyssis.be</code>. This is where you have to set up your website. The easiest way to do this, is by following the wizard. Continue until the wizard asks you for your database configuration: *'''Database Name/Databasenaam:''' If you haven't created a MySQL database/user on UCC, then you'll have to create one by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> Afterwards, you can proceed the installation. At a certain point, you receive a notification to log in on wordpress. This means you have succesfully installed your own wordpress website. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you need to create a new folder in your 'www' directory on your shell account. Then you need a virtual host for this folder, herefor you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] fad3f6fb2b1b29f7f31ec7a62a89fdeb598b1c0a 959 958 2019-11-03T17:15:27Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you need to download Wordpress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named 'wordpress'. Next, you have to move the '''contents''' of the 'wordpress' directory to your 'www' directory on our server, which can be accessed via SFTP. If you would have any more questions about this, you can always follow our other guide here: https://docs.ulyssis.org/Accessing_your_files. After you moved the contents of the 'wordpress' folder into the 'www' directory, you need to go to your account <br> on <code>*your username here*.ulyssis.be</code>. This is where you have to set up your website. The easiest way to do this, is by following the wizard. Continue until it asks you for your database configuration: *'''Database Name/Databasenaam:''' If you haven't created a MySQL database/user on UCC, then you'll have to create one by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> Afterwards, you can proceed the installation. At a certain point, you receive a notification to log in on wordpress. This means you have succesfully installed your own wordpress website. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you need to create a new folder in your 'www' directory on your shell account. Then you need a virtual host for this folder, herefor you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 7dc3fd47a704ffc6bd4940f51dc91c04a54ca469 960 959 2019-11-03T17:30:06Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you need to download Wordpress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your <code>www</code> directory on our servers, which can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: https://docs.ulyssis.org/Accessing_your_files. After you moved the contents of the <code>wordpress</code> folder into the <code>www</code> directory, you need to go to your account <br> on <code>*your username here*.ulyssis.be</code>. This is where you have to set up your website. The easiest way to do this, is by following the wizard. Continue until it asks you for your database configuration: *'''Database Name/Databasenaam:''' If you haven't created a MySQL database/user on UCC, then you'll have to create one by following our guide here: https://docs.ulyssis.org/Using_MySQL. And choose what database you want to use for your wordpress site. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> Afterwards, you can proceed the installation. At a certain point, you receive a notification to log in on wordpress. This means you have succesfully installed your own wordpress website. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 7ee95ea20a9175af4a77d5d7963febdee48381fe 961 960 2019-11-03T17:47:45Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you need to download Wordpress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your <code>www</code> directory on our servers, which can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Wordpress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. After you moved the contents of the <code>wordpress</code> folder into the <code>www</code> directory, you need to go to your account <br> on <code>*your username here*.ulyssis.be</code>. This is where you have to set up your website. The easiest way to do this, is by following the wizard. Continue until it asks you for your database configuration: *'''Database Name/Databasenaam:''' This is the name of the MySQL database you just created. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> Afterwards, you can proceed the installation. At a certain point, you receive a notification to log in on Wordpress. This means you have successfully installed your own Wordpress website. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] c9891a06c16d05a7447c2b6486834226728e8436 962 961 2019-11-03T18:44:14Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you need to download Wordpress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your <code>www</code> directory on our servers, which can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Wordpress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. Now we are ready to install wordpress. To do this, you need to go to your account <br> on <code>*your username here*.ulyssis.be</code>. This is where you have to set up your website. The easiest way to do this, is by following the wizard. Continue until it asks you for your database configuration: *'''Database Name/Databasenaam:''' This is the name of the MySQL database you just created. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> Afterwards, you can proceed the installation. At a certain point, you receive a notification to log in on Wordpress. This means you have successfully installed your own Wordpress website. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] f84dc218bf116a17cf1f37a2876d4a2f84432a31 963 962 2019-11-03T19:16:08Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you need to download Wordpress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your <code>www</code> directory on our servers, which can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Wordpress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. Now we are ready to install wordpress. To do this, you need to go to your account. <br> If you have bought a custom domain using this guide: [[Adding domain names]], your account will be located on your domain. If you did not buy such a domain, your account can be found on *username here*.studentenweb.org or<br> *username here*.ulyssis.be. This is where you have to set up your website. The easiest way to do this, is by following the wizard. Continue until it asks you for your database configuration: *'''Database Name/Databasenaam:''' This is the name of the MySQL database you just created. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> Afterwards, you can proceed the installation. At a certain point, you receive a notification to log in on Wordpress. This means you have successfully installed your own Wordpress website. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] e56f2fe1b9e48fe582c2d79805c638cf8843a3e7 964 963 2019-11-03T19:17:05Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you need to download Wordpress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your <code>www</code> directory on our servers, which can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Wordpress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. Now we are ready to install wordpress. To do this, you need to go to your account. <br> If you have bought a custom domain using this guide: [[Adding domain names]], your account will be located on your domain. If you did not buy such a domain, your account can be found on *username here*.studentenweb.org or<br> *username here*.ulyssis.be.<br> This is where you have to set up your website. The easiest way to do this, is by following the wizard. Continue until it asks you for your database configuration: *'''Database Name/Databasenaam:''' This is the name of the MySQL database you just created. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> Afterwards, you can proceed the installation. At a certain point, you receive a notification to log in on Wordpress. This means you have successfully installed your own Wordpress website. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 8afc073766291e55f894d1482aa55936a0ccece1 965 964 2019-11-03T19:50:05Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you need to download Wordpress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your <code>www</code> directory on our servers, which can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Wordpress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. Now we are ready to install wordpress, so we need to visit the web installer. <br> If you've bought a custom domain using this guide: [[Adding domain names]], the installer will be located on your domain. If you did not buy such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code>. (Replace username with your actual username)<br> This is where you have to set up your website. The easiest way to do this, is by following the wizard. Continue until it asks you for your database configuration: *'''Database Name/Databasenaam:''' This is the name of the MySQL database you just created. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> Afterwards, you can proceed the installation. At a certain point, you receive a notification to log in on Wordpress. This means you have successfully installed your own Wordpress website. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 066216b1563efabf4809ac2ec1087107f4f68fdb 966 965 2019-11-03T20:02:25Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you need to download Wordpress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your <code>www</code> directory on our servers, which can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Wordpress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. Now we are ready to install wordpress, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]]. You can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace username with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. Continue until it asks you for your database configuration: *'''Database Name/Databasenaam:''' This is the name of the MySQL database you just created. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> Afterwards, you can proceed the installation. At a certain point, you receive a notification to log in on Wordpress. This means you have successfully installed your own Wordpress website. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] de4210d402ed4a50e610eff6ab623f2f1a5c135f 967 966 2019-11-03T20:04:26Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you need to download Wordpress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your <code>www</code> directory on our servers, which can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Wordpress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. Now we are ready to install wordpress, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace username with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. Continue until it asks you for your database configuration: *'''Database Name/Databasenaam:''' This is the name of the MySQL database you just created. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> Afterwards, you can proceed the installation. At a certain point, you receive a notification to log in on Wordpress. This means you have successfully installed your own Wordpress website. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 99170ec3c9e12afb28319af521510926687208bd 968 967 2019-11-03T21:45:58Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you need to download Wordpress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your <code>www</code> directory on our servers, which can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Wordpress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. Now we are ready to install wordpress, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace username with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. The setup will ask you for your database configuration: *'''Database Name/Databasenaam:''' This is the name of the MySQL database you just created. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> Afterwards, you can proceed the installation. At a certain point, you receive a notification to log in on Wordpress. This means you have successfully installed your own Wordpress website. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 3bd34ad396daed0d18549fdaa02655378d393667 969 968 2019-11-03T21:47:10Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you need to download Wordpress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your <code>www</code> directory on our servers, which can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Wordpress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. Now we are ready to install Wordpress, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace username with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. The setup will ask you for your database configuration: *'''Database Name/Databasenaam:''' This is the name of the MySQL database you just created. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> Afterwards, you can proceed the installation. At a certain point, you receive a notification to log in on Wordpress. This means you have successfully installed your own Wordpress website. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] ee89e48d96b1274a05394e33af3e08413361acee 6 140 928 2019-10-30T07:05:30Z Casper 39 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 41 939 793 2019-10-31T18:54:54Z Bert 8 /* A backup of your databases */ wikitext text/x-wiki ULYSSIS takes backups of all files, databases, settings and repositories 1-4 times a week. These backups can be restored in case of severe server failure or in case of an emergency (if for example a user by mistake deletes all of their site). It is, however, more convenient that users take their own backups when they do experimental things on their account. == A backup of your files == You can use the graphical methods described in [[Accessing your files]] to download a copy of all of your files. This copy, or certain files, can then easily be uploaded again using the same method to restore backups == A backup of your databases == To take a backup of your database you simple use the export function of PHPMyAdmin, PHPPgAdmin and/or Adminer as described on [[Using PHPMyAdmin]], [[Using PHPPgAdmin]] and [[Using Adminer]]. If you are backing up and/or restoring a larger database, it's advised to use command line tools since they are more performant than webtools and don't have any timeouts that could interrupt your backup/restore. In case of MySQL, you can use mysqdump to take a backup: mysqldump -h mysql.ulyssis.org -p username_database > backup.sql This will prompt you for your database password (please refer to [Using MySQL] if you don't know your password) and then dump the entire database to backup.sql. To restore your backup you can use the mysql command: mysql -h mysql.ulyssis.org -p username_database < backup.sql Please keep in mind that by default mysqldump includes statements in the SQL file that will delete all tables that will be restored. [[Category:Files]] [[Category:Databases]] 9e09ab3100e645f5918efd3f1bab0cd16b8e6e7d 940 939 2019-11-01T00:01:29Z Bert 8 wikitext text/x-wiki ULYSSIS takes backups of all files, databases, settings and repositories 1-4 times a week. These backups can be restored in case of severe server failure or in case of an emergency (if for example a user by mistake deletes all of their site). It is, however, more convenient that users take their own backups when they do experimental things on their account. == A backup of your files == You can use the graphical methods described in [[Accessing your files]] to download a copy of all of your files. This copy, or certain files, can then easily be uploaded again using the same method to restore backups == A backup of your databases == To take a backup of your database you simple use the export function of PHPMyAdmin, PHPPgAdmin and/or Adminer as described on [[Using PHPMyAdmin]], [[Using PHPPgAdmin]] and [[Using Adminer]]. If you are backing up and/or restoring a larger database, it's advised to use command line tools since they are more performant than webtools and don't have any timeouts that could interrupt your backup/restore. === MySQL command line === To take a backup, execute the following command on one of our shellservers (with the right database name filled in): mysqldump -h mysql.ulyssis.org -p username_database > backup.sql This will prompt you for your database password (please refer to [[Using MySQL]] if you don't know your password) and then dump the entire database to backup.sql. To restore your backup you can use the mysql command: mysql -h mysql.ulyssis.org -p username_database < backup.sql Please keep in mind that by default mysqldump includes statements in the SQL file that will delete all tables that will be restored. === PostgreSQL command line === [[Category:Files]] [[Category:Databases]] 3caceb36fea1d354027a1f44a9228eabc9622965 941 940 2019-11-01T00:03:20Z Bert 8 /* MySQL command line */ wikitext text/x-wiki ULYSSIS takes backups of all files, databases, settings and repositories 1-4 times a week. These backups can be restored in case of severe server failure or in case of an emergency (if for example a user by mistake deletes all of their site). It is, however, more convenient that users take their own backups when they do experimental things on their account. == A backup of your files == You can use the graphical methods described in [[Accessing your files]] to download a copy of all of your files. This copy, or certain files, can then easily be uploaded again using the same method to restore backups == A backup of your databases == To take a backup of your database you simple use the export function of PHPMyAdmin, PHPPgAdmin and/or Adminer as described on [[Using PHPMyAdmin]], [[Using PHPPgAdmin]] and [[Using Adminer]]. If you are backing up and/or restoring a larger database, it's advised to use command line tools since they are more performant than webtools and don't have any timeouts that could interrupt your backup/restore. === MySQL command line === To take a backup, execute the following command on one of our shellservers (with the right database name filled in): mysqldump -h mysql.ulyssis.org -p username_database > backup.sql This will prompt you for your database password (please refer to [[Using MySQL]] if you don't know your password) and then dump the entire database to backup.sql file as SQL. To restore your backup you can use the mysql command on one of our shellservers (with the right database name filled in), whatever SQL file you specify will be executed: mysql -h mysql.ulyssis.org -p username_database < backup.sql Please keep in mind that by default mysqldump includes statements in the SQL file that will delete all tables that will be restored. === PostgreSQL command line === [[Category:Files]] [[Category:Databases]] dd86aaa1237b3752fc13091224f1e6c501eaee36 942 941 2019-11-01T00:18:40Z Bert 8 /* MySQL command line */ wikitext text/x-wiki ULYSSIS takes backups of all files, databases, settings and repositories 1-4 times a week. These backups can be restored in case of severe server failure or in case of an emergency (if for example a user by mistake deletes all of their site). It is, however, more convenient that users take their own backups when they do experimental things on their account. == A backup of your files == You can use the graphical methods described in [[Accessing your files]] to download a copy of all of your files. This copy, or certain files, can then easily be uploaded again using the same method to restore backups == A backup of your databases == To take a backup of your database you simple use the export function of PHPMyAdmin, PHPPgAdmin and/or Adminer as described on [[Using PHPMyAdmin]], [[Using PHPPgAdmin]] and [[Using Adminer]]. If you are backing up and/or restoring a larger database, it's advised to use command line tools since they are more performant than webtools and don't have any timeouts that could interrupt your backup/restore. === MySQL command line === To take a backup, execute the following command on one of our shellservers (with the right database name filled in): mysqldump -h mysql.ulyssis.org -p username_database > backup.sql This will prompt you for your database password (please refer to [[Using MySQL]] if you don't know your password) and then dump the entire database to backup.sql file as SQL. To restore your backup you can use the mysql command on one of our shellservers (with the right database name filled in), whatever SQL file you specify will be executed: mysql -h mysql.ulyssis.org -p username_database < backup.sql Please keep in mind that by default mysqldump includes statements in the SQL file that will delete all tables that will be restored. If you wish to have more control over different settings when taking or restoring please, you can refer to the respective man pages of mysqldump and mysql using <code>man mysqldump</code> and <code>man mysql</code> === PostgreSQL command line === [[Category:Files]] [[Category:Databases]] 8c2bbd4f8fc33e241a75506bf87006f8abc90bc4 943 942 2019-11-01T00:34:26Z Bert 8 /* PostgreSQL command line */ wikitext text/x-wiki ULYSSIS takes backups of all files, databases, settings and repositories 1-4 times a week. These backups can be restored in case of severe server failure or in case of an emergency (if for example a user by mistake deletes all of their site). It is, however, more convenient that users take their own backups when they do experimental things on their account. == A backup of your files == You can use the graphical methods described in [[Accessing your files]] to download a copy of all of your files. This copy, or certain files, can then easily be uploaded again using the same method to restore backups == A backup of your databases == To take a backup of your database you simple use the export function of PHPMyAdmin, PHPPgAdmin and/or Adminer as described on [[Using PHPMyAdmin]], [[Using PHPPgAdmin]] and [[Using Adminer]]. If you are backing up and/or restoring a larger database, it's advised to use command line tools since they are more performant than webtools and don't have any timeouts that could interrupt your backup/restore. === MySQL command line === To take a backup, execute the following command on one of our shellservers (with the right database name filled in): mysqldump -h mysql.ulyssis.org -p username_database > backup.sql This will prompt you for your database password (please refer to [[Using MySQL]] if you don't know your password) and then dump the entire database to backup.sql file as SQL. To restore your backup you can use the mysql command on one of our shellservers (with the right database name filled in), whatever SQL file you specify will be executed: mysql -h mysql.ulyssis.org -p username_database < backup.sql Please keep in mind that by default mysqldump includes statements in the SQL file that will delete all tables that will be restored. If you wish to have more control over different settings when taking or restoring please, you can refer to the respective man pages of mysqldump and mysql using <code>man mysqldump</code> and <code>man mysql</code> === PostgreSQL command line === To take a backup, execute the following command on one of our shellservers (with the right database name filled in): pg_dump -h pgsql.ulyssis.org -W --clean username_database > backup.sql This will prompt you for your database password (please refer to [[Using PostgreSQL]] if you don't know your password) and then dump the entire database to backup.sql file as SQL with COPY statements. If you prefer INSERT instead of COPY statements, you can add <code>--inserts</code> to your command. To restore your backup you can use the pg_restore command on one of our shellservers (with the right database name filled in), whatever SQL file you specify will be executed: psql -h pgsql.ulyssis.org -W username_database < backup.sql Please keep in mind that because we specified <code>--clean</code> earlier, our SQL file includes statements that will delete all tables, sequences, functions and schemas that will be restored. If you wish to have more control over different settings when taking or restoring please, you can refer to the respective man pages of pg_dump and psql using <code>man pg_dump</code> and <code>man psql</code> [[Category:Files]] [[Category:Databases]] 62757da7c39056cb7b45064c1d215a4f5985b2e5 952 943 2019-11-03T11:36:19Z Bert 8 /* A backup of your files */ wikitext text/x-wiki ULYSSIS takes backups of all files, databases, settings and repositories 1-4 times a week. These backups can be restored in case of severe server failure or in case of an emergency (if for example a user by mistake deletes all of their site). It is, however, more convenient that users take their own backups when they do experimental things on their account. == A backup of your files == You can use the methods described in [[Accessing your files]] to download a copy of all of your files or specific folders you will be working on. If something goes wrong, you can easily restore files to a previous state by re-uploading those you have downloaded and saved. == A backup of your databases == To take a backup of your database you simple use the export function of PHPMyAdmin, PHPPgAdmin and/or Adminer as described on [[Using PHPMyAdmin]], [[Using PHPPgAdmin]] and [[Using Adminer]]. If you are backing up and/or restoring a larger database, it's advised to use command line tools since they are more performant than webtools and don't have any timeouts that could interrupt your backup/restore. === MySQL command line === To take a backup, execute the following command on one of our shellservers (with the right database name filled in): mysqldump -h mysql.ulyssis.org -p username_database > backup.sql This will prompt you for your database password (please refer to [[Using MySQL]] if you don't know your password) and then dump the entire database to backup.sql file as SQL. To restore your backup you can use the mysql command on one of our shellservers (with the right database name filled in), whatever SQL file you specify will be executed: mysql -h mysql.ulyssis.org -p username_database < backup.sql Please keep in mind that by default mysqldump includes statements in the SQL file that will delete all tables that will be restored. If you wish to have more control over different settings when taking or restoring please, you can refer to the respective man pages of mysqldump and mysql using <code>man mysqldump</code> and <code>man mysql</code> === PostgreSQL command line === To take a backup, execute the following command on one of our shellservers (with the right database name filled in): pg_dump -h pgsql.ulyssis.org -W --clean username_database > backup.sql This will prompt you for your database password (please refer to [[Using PostgreSQL]] if you don't know your password) and then dump the entire database to backup.sql file as SQL with COPY statements. If you prefer INSERT instead of COPY statements, you can add <code>--inserts</code> to your command. To restore your backup you can use the pg_restore command on one of our shellservers (with the right database name filled in), whatever SQL file you specify will be executed: psql -h pgsql.ulyssis.org -W username_database < backup.sql Please keep in mind that because we specified <code>--clean</code> earlier, our SQL file includes statements that will delete all tables, sequences, functions and schemas that will be restored. If you wish to have more control over different settings when taking or restoring please, you can refer to the respective man pages of pg_dump and psql using <code>man pg_dump</code> and <code>man psql</code> [[Category:Files]] [[Category:Databases]] 30b472aafadc89231216c01883914b25a6417eb7 0 40 944 802 2019-11-01T00:39:22Z Bert 8 /* Making Backups */ wikitext text/x-wiki You can access your MySQL databases using PHPMyAdmin. This application can be found on https://phpmyadmin.ulyssis.org. To login you need to use your MySQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your MySQL password you can get it from your websites configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. You can change your database passwords through our control panel [https://ucc.ulyssis.org/ UCC], but keep in mind to then also change the password in relevant configuration files, or you applications may stop working correctly. == Basic Usage == Once you've logged in, you will see your username on the left, you can click the plus sign to reveal all your databases. You can then view databases and tables. For each table you can view the records, view and change the structure, add records, take backups, etc. Detailed documentation is available on the PHPMyAdmin [https://www.phpmyadmin.net/docs/ official documentation website] == Making Backups == {{notice|Keep in mind|If you are backing up and/or restoring a larger database, it's advised to use command line tools since they are more performant than webtools and don't have any timeouts that could interrupt your backup/restore. Please refer to [[Making Backups]] for more details}} PHPMyAdmin has an export option which can be used to backup the structure and/or data of databases and tables. When no database or table has been selected, the export tab in the top menu allows to export all databases at the same time. When a specific database or table is selected, that database or table is exported. You can either accept the default settings, or ask for more settings, to specificy whether any checks, DROPs or time settings are required, as well as to specify if you wish to export the structure, the data or both. You can later restore backups by uploading the file through the form on the import tab. To make restoring easier, we suggest you backup individual databases or even individual tables. [[Category:Databases]] b3c47d16fd5154245c93df12273653219174647f 945 944 2019-11-01T00:39:30Z Bert 8 wikitext text/x-wiki You can access your MySQL databases using PHPMyAdmin. This application can be found on https://phpmyadmin.ulyssis.org. To login you need to use your MySQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your MySQL password you can get it from your websites configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. You can change your database passwords through our control panel [https://ucc.ulyssis.org/ UCC], but keep in mind to then also change the password in relevant configuration files, or you applications may stop working correctly. == Basic Usage == Once you've logged in, you will see your username on the left, you can click the plus sign to reveal all your databases. You can then view databases and tables. For each table you can view the records, view and change the structure, add records, take backups, etc. Detailed documentation is available on the PHPMyAdmin [https://www.phpmyadmin.net/docs/ official documentation website] == Making Backups == {{notice|Keep in mind|If you are backing up and/or restoring a larger database, it's advised to use command line tools since they are more performant than webtools and don't have any timeouts that could interrupt your backup/restore. Please refer to [[Making Backups]] for more details}} PHPMyAdmin has an export option which can be used to backup the structure and/or data of databases and tables. When no database or table has been selected, the export tab in the top menu allows to export all databases at the same time. When a specific database or table is selected, that database or table is exported. You can either accept the default settings, or ask for more settings, to specificy whether any checks, DROPs or time settings are required, as well as to specify if you wish to export the structure, the data or both. You can later restore backups by uploading the file through the form on the import tab. To make restoring easier, we suggest you backup individual databases or even individual tables. [[Category:Databases]] 321d756893855e35322ffa75d066f5480d10d53b 950 945 2019-11-01T00:49:52Z Bert 8 wikitext text/x-wiki You can access your MySQL databases using PHPMyAdmin. This application can be found on https://phpmyadmin.ulyssis.org. To login you need to use your MySQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your MySQL password you can get it from your websites configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. You can change your database passwords through our control panel [https://ucc.ulyssis.org/ UCC], but keep in mind to then also change the password in relevant configuration files, or you applications may stop working correctly. == Basic Usage == Once you've logged in, you will see your username on the left, you can click the plus sign to reveal all your databases. You can then view databases and tables. For each table you can view the records, view and change the structure, add records, take backups, etc. Detailed documentation is available on the PHPMyAdmin [https://www.phpmyadmin.net/docs/ official documentation website] == Making Backups == {{notice|Keep in mind|If you are backing up and/or restoring a larger database, it's advised to use command line tools since they are more performant than webtools and don't have any timeouts that could interrupt your backup/restore. Please refer to [[Making Backups]] for more details.}} PHPMyAdmin has an export option which can be used to backup the structure and/or data of databases and tables. When no database or table has been selected, the export tab in the top menu allows to export all databases at the same time. When a specific database or table is selected, that database or table is exported. You can either accept the default settings, or ask for more settings, to specificy whether any checks, DROPs or time settings are required, as well as to specify if you wish to export the structure, the data or both. You can later restore backups by uploading the file through the form on the import tab. To make restoring easier, we suggest you backup individual databases or even individual tables. [[Category:Databases]] 2284efaa84c420431b048e39ef09373d22ceb698 0 126 946 803 2019-11-01T00:49:03Z Bert 8 /* Making Backups */ wikitext text/x-wiki You can access your PostgreSQL databases using PHPPgAdmin. This application can be found on https://phppgadmin.ulyssis.org. To login you need to use your PostgreSQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your PostgreSQL password you can get it from your websites configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. You can change your database passwords through our control panel [https://ucc.ulyssis.org/ UCC], but keep in mind to then also change the password in relevant configuration files, or you applications may stop working correctly. == Basic Usage == You can login by clicking on the only server in the left sidebar ''PostgreSQL voor gebruikers, kringen en organisaties''. Once you've logged in, you will see an overview of all your databases. You can then view databases, schemas and tables by clicking on them or navigating through the sidebar. For each table you can view the records, view and change the structure, add records, take backups, etc. Official documentation of all functionality is sadly lacking, but you can still refer to [http://phppgadmin.sourceforge.net/doku.php?id=faq_docs the official documentation] == Making Backups == {{notice|Keep in mind|If you are backing up and/or restoring a larger database, it's advised to use command line tools since they are more performant than webtools and don't have any timeouts that could interrupt your backup/restore. Please refer to [[Making Backups]] for more details}} PHPPgAdmin has an export option which can be used to backup the structure and/or data of databases, schemas and tables, as well as more advanced features such as sequences and functions. When no database, schema or table has been selected, the export tab in the top menu allows to export all databases at the same time. When a specific database or table is selected, that database or table is exported. You can decide whether you wish to export the structure, the data or both, as well as the format and if DROPs need to be included. You can later restore backups by uploading the file through the form on the SQL page (top right corner). To make restoring easier, we suggest you backup individual databases or even individual tables and use the SQL format instead of COPY. [[Category:Databases]] 68832a00d1f98b421d12f7af24af216f8fedf599 949 946 2019-11-01T00:49:44Z Bert 8 /* Making Backups */ wikitext text/x-wiki You can access your PostgreSQL databases using PHPPgAdmin. This application can be found on https://phppgadmin.ulyssis.org. To login you need to use your PostgreSQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your PostgreSQL password you can get it from your websites configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. You can change your database passwords through our control panel [https://ucc.ulyssis.org/ UCC], but keep in mind to then also change the password in relevant configuration files, or you applications may stop working correctly. == Basic Usage == You can login by clicking on the only server in the left sidebar ''PostgreSQL voor gebruikers, kringen en organisaties''. Once you've logged in, you will see an overview of all your databases. You can then view databases, schemas and tables by clicking on them or navigating through the sidebar. For each table you can view the records, view and change the structure, add records, take backups, etc. Official documentation of all functionality is sadly lacking, but you can still refer to [http://phppgadmin.sourceforge.net/doku.php?id=faq_docs the official documentation] == Making Backups == {{notice|Keep in mind|If you are backing up and/or restoring a larger database, it's advised to use command line tools since they are more performant than webtools and don't have any timeouts that could interrupt your backup/restore. Please refer to [[Making Backups]] for more details.}} PHPPgAdmin has an export option which can be used to backup the structure and/or data of databases, schemas and tables, as well as more advanced features such as sequences and functions. When no database, schema or table has been selected, the export tab in the top menu allows to export all databases at the same time. When a specific database or table is selected, that database or table is exported. You can decide whether you wish to export the structure, the data or both, as well as the format and if DROPs need to be included. You can later restore backups by uploading the file through the form on the SQL page (top right corner). To make restoring easier, we suggest you backup individual databases or even individual tables and use the SQL format instead of COPY. [[Category:Databases]] 44c0873c0749db042e57523f44e2c0e6ba5eb94a 0 127 947 804 2019-11-01T00:49:10Z Bert 8 /* Making Backups */ wikitext text/x-wiki You can access both your MySQL and PostgreSQL databases using Adminer, though not both at the same time. This application can be found on https://adminer.ulyssis.org. To login you need to use your MySQL or PostgreSQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your passwords you can get it from your websites configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. You can change your database passwords through our control panel [https://ucc.ulyssis.org/ UCC], but keep in mind to then also change the password in relevant configuration files, or you applications may stop working correctly. To use MySQL, please use the server mysql.ulyssis.org. In case of PostgreSQL, please use pgsql.ulyssis.org. == Basic Usage == When logging in using MySQL, you will see an overview of all your databases. When using PostgreSQL you will see all databases that have been created by all of our users (this is a known problem with Adminer), though you won't be able to view them. You can then view databases and tables. For each table you can view the records, view and change the structure, add records, take backups, etc. Sadly no official documentation is available, though Adminer has a [https://sourceforge.net/p/adminer/discussion/ forum] where you can ask for help. == Making Backups == {{notice|Keep in mind|If you are backing up and/or restoring a larger database, it's advised to use command line tools since they are more performant than webtools and don't have any timeouts that could interrupt your backup/restore. Please refer to [[Making Backups]] for more details}} Adminer has an export option which can be used to backup the structure and/or data of databases and tables. When no database or table has been selected, the export button in the sidebar allows to export all databases at the same time. When a specific database or table is selected, that database or table is exported. You can specify to save the file, in what format, and whether structures and data should be dropped, truncated or created. You can later restore backups by uploading the file through the form available through the import button in the sidebar. To make restoring easier, we suggest you backup individual databases or even individual tables and use the SQL format. [[Category:Databases]] fd398d4f159f936a7a90658be733c20bb86b360b 948 947 2019-11-01T00:49:37Z Bert 8 wikitext text/x-wiki You can access both your MySQL and PostgreSQL databases using Adminer, though not both at the same time. This application can be found on https://adminer.ulyssis.org. To login you need to use your MySQL or PostgreSQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your passwords you can get it from your websites configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. You can change your database passwords through our control panel [https://ucc.ulyssis.org/ UCC], but keep in mind to then also change the password in relevant configuration files, or you applications may stop working correctly. To use MySQL, please use the server mysql.ulyssis.org. In case of PostgreSQL, please use pgsql.ulyssis.org. == Basic Usage == When logging in using MySQL, you will see an overview of all your databases. When using PostgreSQL you will see all databases that have been created by all of our users (this is a known problem with Adminer), though you won't be able to view them. You can then view databases and tables. For each table you can view the records, view and change the structure, add records, take backups, etc. Sadly no official documentation is available, though Adminer has a [https://sourceforge.net/p/adminer/discussion/ forum] where you can ask for help. == Making Backups == {{notice|Keep in mind|If you are backing up and/or restoring a larger database, it's advised to use command line tools since they are more performant than webtools and don't have any timeouts that could interrupt your backup/restore. Please refer to [[Making Backups]] for more details.}} Adminer has an export option which can be used to backup the structure and/or data of databases and tables. When no database or table has been selected, the export button in the sidebar allows to export all databases at the same time. When a specific database or table is selected, that database or table is exported. You can specify to save the file, in what format, and whether structures and data should be dropped, truncated or created. You can later restore backups by uploading the file through the form available through the import button in the sidebar. To make restoring easier, we suggest you backup individual databases or even individual tables and use the SQL format. [[Category:Databases]] b9fe3b4f3675726a3173da0d883b6b0257c0015c 0 33 970 719 2019-11-04T03:04:55Z Bert 8 /* Deploying Shibboleth */ wikitext text/x-wiki Shibboleth is the software powering the Central KU Leuven Login. It's a piece of software used by many universities to supply identification and access management. ULYSSIS works together with ICTS to supply limited access to Shibboleth. We are however only able to supply Shibboleth to those approved by ICTS. In practice all faculty unions will be granted access if they can prove they have the technical ability to use Shibboleth in a safe and privacy friendly way. For other organisations it can be more difficult to get access, therefore it is best to write an extensive explenation of what you plan to do with Shibboleth, why your organisation requires it, what your organisation does, and other relevant information. We will then contact ICTS with your request. == How to request == To request Shibboleth access, you first need to make sure the domain you wish to use Shibboleth on has valid SSL certificates. Lately ICTS has been pushing that all traffic to the website is already over HTTPS before Shibboleth is issued. For more info you can check [[Getting SSL]] If you have SSL set up you need to send an email to request Shibboleth to ulyssis@ulyssis.org. The email must contain the following info: * What domain you wish to use Shibboleth on (this must be a single domain, so keep subdomains and www in mind) * What you will be using Shibboleth for and in general what your application will do. This explanation is required by ICTS. If you fail to convince them they will not grant your domain access. * What attributes you wish to use and what you will do with them (and whether you will store them). You can find the list of attributes on https://admin.kuleuven.be/icts/services/aai/attributes * Explicitly state you grant ULYSSIS permission to edit the .htaccess file to be able to export the required Shibboleth Metadata * If you are not a recognised faculty union you will need to include an extra motivation why you require Shibboleth (as noted above) If your application is complete and correct we will file a formal request. We will of course notify you of ICTS' response. == Deploying Shibboleth == After you have been granted access you can soon start using Shibboleth. The first step is to add the following lines to your .htaccess ShibDisable Off AuthType Shibboleth require shibboleth ShibRequireSession off We disable certain features of Shibboleth here because it will otherwise interfere with any other HTTP-auth options you might be using. Now that you have added this information to .htaccess you are able to serve requests to Shibboleth.sso, if your request is well-formed the sso will handle communication with the IdP (identity provider) of the KU Leuven. A login link follows the following syntax: https://[YOUR_HOSTNAME]/Shibboleth.sso/WAYF/kuleuven?target=[URLENCODED_RETURN_URL] And logout links: https://[YOUR_HOSTNAME]/Shibboleth.sso/Logout?return=[URLENCODED_DISPLAY_URL] It is important to note that on logout the user will stay on the KU Leuven's IdP-page and your link will only be displayed. The user will NOT be redirected (even though this is the normale behaviour according to the Shibboleth documentation). As soon as a user is logged in, his or hers attributes will be available to your application. Attributes are certain properties that an account may have and that supply further information about them. Some examples are: first name, last name, mail, student id. All of these will be available as HTTP headers. But keep in mind that apache might prefix those with REDIRECT_ multiple times (for example when mod_rewrite is used). For an overview of all attributes you can check out http://shib.kuleuven.be/secure/allAttributes More general information on the KU Leuvens implementation can be found on http://shib.kuleuven.be/ . [[Category:Webserver]] 0bbdd6e1fe1b3ef4723d83073b8c0628f39224d2 971 970 2019-11-04T03:05:03Z Bert 8 /* Deploying Shibboleth */ wikitext text/x-wiki Shibboleth is the software powering the Central KU Leuven Login. It's a piece of software used by many universities to supply identification and access management. ULYSSIS works together with ICTS to supply limited access to Shibboleth. We are however only able to supply Shibboleth to those approved by ICTS. In practice all faculty unions will be granted access if they can prove they have the technical ability to use Shibboleth in a safe and privacy friendly way. For other organisations it can be more difficult to get access, therefore it is best to write an extensive explenation of what you plan to do with Shibboleth, why your organisation requires it, what your organisation does, and other relevant information. We will then contact ICTS with your request. == How to request == To request Shibboleth access, you first need to make sure the domain you wish to use Shibboleth on has valid SSL certificates. Lately ICTS has been pushing that all traffic to the website is already over HTTPS before Shibboleth is issued. For more info you can check [[Getting SSL]] If you have SSL set up you need to send an email to request Shibboleth to ulyssis@ulyssis.org. The email must contain the following info: * What domain you wish to use Shibboleth on (this must be a single domain, so keep subdomains and www in mind) * What you will be using Shibboleth for and in general what your application will do. This explanation is required by ICTS. If you fail to convince them they will not grant your domain access. * What attributes you wish to use and what you will do with them (and whether you will store them). You can find the list of attributes on https://admin.kuleuven.be/icts/services/aai/attributes * Explicitly state you grant ULYSSIS permission to edit the .htaccess file to be able to export the required Shibboleth Metadata * If you are not a recognised faculty union you will need to include an extra motivation why you require Shibboleth (as noted above) If your application is complete and correct we will file a formal request. We will of course notify you of ICTS' response. == Deploying Shibboleth == After you have been granted access you can soon start using Shibboleth. The first step is to add the following lines to your .htaccess ShibDisable Off AuthType Shibboleth require shibboleth ShibRequireSession off We disable certain features of Shibboleth here because it will otherwise interfere with any other HTTP-auth options you might be using. Now that you have added this information to .htaccess you are able to serve requests to Shibboleth.sso, if your request is well-formed the sso will handle communication with the IdP (identity provider) of the KU Leuven. A login link follows the following syntax: https://[YOUR_HOSTNAME]/Shibboleth.sso/WAYF/kuleuven?target=[URLENCODED_RETURN_URL] And logout links: https://[YOUR_HOSTNAME]/Shibboleth.sso/Logout?return=[URLENCODED_DISPLAY_URL] It is important to note that on logout the user will stay on the KU Leuven's IdP-page and your link will only be displayed. The user will NOT be redirected (even though this is the normale behaviour according to the Shibboleth documentation). As soon as a user is logged in, his or hers attributes will be available to your application. Attributes are certain properties that an account may have and that supply further information about them. Some examples are: first name, last name, mail, student id. All of these will be available as HTTP headers. But keep in mind that apache might prefix those with REDIRECT_ multiple times (for example when mod_rewrite is used). For an overview of all attributes you can check out http://shib.kuleuven.be/secure/allAttributes More general information on the KU Leuvens implementation can be found on http://shib.kuleuven.be/. [[Category:Webserver]] a0eae31fb1a422426a86569859c5ffab65451e57 0 19 972 724 2019-11-04T03:10:55Z Bert 8 wikitext text/x-wiki Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mailbox regularly, because all important information will be sent to this address. You can check your e-mail using webmail or an email client of your own. It is also possible to configure your email address in UCC to automatically [[Forwarders|forward]] all correspondence to another address. ==Webmail== You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to enter the website. ==POP and IMAP access== You can access your ulyssis mail by POP or IMAP protocol. The configuration parameters are: * '''server''': <tt>mail.ulyssis.org</tt> * '''username''': ''your ULYSSIS username'' * '''password''': ''your ULYSSIS password'' * '''security''': SSL ==SMTP== ULYSSIS doesn't offer SMTP. Instead, you can use KULeuven's SMTP server: * '''server''': <tt>smtps.kuleuven.be</tt> * '''port''': 443 * '''username''': ''your student id'' * '''password''': ''your KULeuven password'' * '''security''': SSL == Advanced == Your emails are stored within your account under ~/Maildir. These files can of course be read with a command line email client such as alpine or mutt. We support sendmail style local delivery using .forward. More information is available in the official documentation of [https://www.sendmail.org/~ca/email/doc8.9/op-sh-2.html#sh-2.8 Sendmail] and [http://www.postfix.org/local.8.html Postfix]. You can also use procmail on our servers. A very detailed explanation on procmail is available on the [https://wiki.archlinux.org/index.php/Procmail ArchWiki]. [[Category:Mail]] f317213451858325e37f58806f88bbdc3b67fb90 0 19 973 972 2019-11-04T03:11:16Z Bert 8 wikitext text/x-wiki Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mailbox regularly, because all important information will be sent to this address. You can check your e-mail using webmail or an email client of your own. It is also possible to configure your email address in UCC to automatically [[Forwarders|forward]] all correspondence to another address. ==Webmail== You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to login. ==POP and IMAP access== You can access your ulyssis mail by POP or IMAP protocol. The configuration parameters are: * '''server''': <tt>mail.ulyssis.org</tt> * '''username''': ''your ULYSSIS username'' * '''password''': ''your ULYSSIS password'' * '''security''': SSL ==SMTP== ULYSSIS doesn't offer SMTP. Instead, you can use KULeuven's SMTP server: * '''server''': <tt>smtps.kuleuven.be</tt> * '''port''': 443 * '''username''': ''your student id'' * '''password''': ''your KULeuven password'' * '''security''': SSL == Advanced == Your emails are stored within your account under ~/Maildir. These files can of course be read with a command line email client such as alpine or mutt. We support sendmail style local delivery using .forward. More information is available in the official documentation of [https://www.sendmail.org/~ca/email/doc8.9/op-sh-2.html#sh-2.8 Sendmail] and [http://www.postfix.org/local.8.html Postfix]. You can also use procmail on our servers. A very detailed explanation on procmail is available on the [https://wiki.archlinux.org/index.php/Procmail ArchWiki]. [[Category:Mail]] aad0eb8829097a8b18b150ccdcb4013e9d806616 974 973 2019-11-04T03:11:32Z Bert 8 /* POP and IMAP access */ wikitext text/x-wiki Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mailbox regularly, because all important information will be sent to this address. You can check your e-mail using webmail or an email client of your own. It is also possible to configure your email address in UCC to automatically [[Forwarders|forward]] all correspondence to another address. ==Webmail== You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to login. ==POP and IMAP access== You can access your ulyssis mail with POP or IMAP. The configuration parameters are: * '''server''': <tt>mail.ulyssis.org</tt> * '''username''': ''your ULYSSIS username'' * '''password''': ''your ULYSSIS password'' * '''security''': SSL ==SMTP== ULYSSIS doesn't offer SMTP. Instead, you can use KULeuven's SMTP server: * '''server''': <tt>smtps.kuleuven.be</tt> * '''port''': 443 * '''username''': ''your student id'' * '''password''': ''your KULeuven password'' * '''security''': SSL == Advanced == Your emails are stored within your account under ~/Maildir. These files can of course be read with a command line email client such as alpine or mutt. We support sendmail style local delivery using .forward. More information is available in the official documentation of [https://www.sendmail.org/~ca/email/doc8.9/op-sh-2.html#sh-2.8 Sendmail] and [http://www.postfix.org/local.8.html Postfix]. You can also use procmail on our servers. A very detailed explanation on procmail is available on the [https://wiki.archlinux.org/index.php/Procmail ArchWiki]. [[Category:Mail]] b4475ce080ceb691b393f111885c3696f95816fd 975 974 2019-11-04T03:11:48Z Bert 8 /* POP and IMAP access */ wikitext text/x-wiki Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mailbox regularly, because all important information will be sent to this address. You can check your e-mail using webmail or an email client of your own. It is also possible to configure your email address in UCC to automatically [[Forwarders|forward]] all correspondence to another address. ==Webmail== You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to login. ==POP and IMAP access== You can access your ulyssis mail with POP or IMAP. The configuration parameters are: * '''server''': <code>mail.ulyssis.org</code> * '''username''': ''your ULYSSIS username'' * '''password''': ''your ULYSSIS password'' * '''security''': SSL ==SMTP== ULYSSIS doesn't offer SMTP. Instead, you can use KULeuven's SMTP server: * '''server''': <tt>smtps.kuleuven.be</tt> * '''port''': 443 * '''username''': ''your student id'' * '''password''': ''your KULeuven password'' * '''security''': SSL == Advanced == Your emails are stored within your account under ~/Maildir. These files can of course be read with a command line email client such as alpine or mutt. We support sendmail style local delivery using .forward. More information is available in the official documentation of [https://www.sendmail.org/~ca/email/doc8.9/op-sh-2.html#sh-2.8 Sendmail] and [http://www.postfix.org/local.8.html Postfix]. You can also use procmail on our servers. A very detailed explanation on procmail is available on the [https://wiki.archlinux.org/index.php/Procmail ArchWiki]. [[Category:Mail]] 29498ceb57b049fc43e308d48be9b261fb133e3f 976 975 2019-11-04T03:11:59Z Bert 8 /* SMTP */ wikitext text/x-wiki Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mailbox regularly, because all important information will be sent to this address. You can check your e-mail using webmail or an email client of your own. It is also possible to configure your email address in UCC to automatically [[Forwarders|forward]] all correspondence to another address. ==Webmail== You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to login. ==POP and IMAP access== You can access your ulyssis mail with POP or IMAP. The configuration parameters are: * '''server''': <code>mail.ulyssis.org</code> * '''username''': ''your ULYSSIS username'' * '''password''': ''your ULYSSIS password'' * '''security''': SSL ==SMTP== ULYSSIS doesn't offer SMTP. Instead, you can use KULeuven's SMTP server: * '''server''': <code>smtps.kuleuven.be</code> * '''port''': 443 * '''username''': ''your student id'' * '''password''': ''your KULeuven password'' * '''security''': SSL == Advanced == Your emails are stored within your account under ~/Maildir. These files can of course be read with a command line email client such as alpine or mutt. We support sendmail style local delivery using .forward. More information is available in the official documentation of [https://www.sendmail.org/~ca/email/doc8.9/op-sh-2.html#sh-2.8 Sendmail] and [http://www.postfix.org/local.8.html Postfix]. You can also use procmail on our servers. A very detailed explanation on procmail is available on the [https://wiki.archlinux.org/index.php/Procmail ArchWiki]. [[Category:Mail]] d8b835df81dcce86838ca3e8981a7b95f00c968b 0 20 977 969 2019-11-04T12:25:22Z Bert 8 wikitext text/x-wiki ==How to install Wordpress for your account== First you need to download Wordpress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your <code>www</code> directory on our servers, which can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Wordpress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. Now we are ready to install Wordpress, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace username with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. The setup will ask you for your database configuration: *'''Database Name/Databasenaam:''' This is the name of the MySQL database you just created. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> Afterwards, you can proceed the installation. At a certain point, you receive a notification to log in on Wordpress. This means you have successfully installed your own Wordpress website. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 8718f96680cab00f20a91b44898f4a2d0b4a8ffa 978 977 2019-11-04T12:28:14Z Bert 8 wikitext text/x-wiki ==How to install Wordpress for your account== First you need to download Wordpress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your <code>www</code> directory on our servers, which can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Wordpress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. Now we are ready to install Wordpress, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace username with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. The setup will ask you for your database configuration:*'''Database Name/Databasenaam:''' This is the name of the MySQL database you just created. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> Afterwards, you can proceed the installation. At a certain point, you receive a notification to log in on Wordpress. This means you have successfully installed your own Wordpress website. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] b3a7b714436bba3cb290c1a410a23eeabff1f445 979 978 2019-11-04T12:28:23Z Bert 8 wikitext text/x-wiki ==How to install Wordpress for your account== First you need to download Wordpress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your <code>www</code> directory on our servers, which can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Wordpress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. Now we are ready to install Wordpress, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace username with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. The setup will ask you for your database configuration: *'''Database Name/Databasenaam:''' This is the name of the MySQL database you just created. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> Afterwards, you can proceed the installation. At a certain point, you receive a notification to log in on Wordpress. This means you have successfully installed your own Wordpress website. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] f188b16b891e27b765e635e385a7f5a2ecae3b6e 980 979 2019-11-04T12:28:34Z Bert 8 wikitext text/x-wiki ==How to install Wordpress for your account== First you need to download Wordpress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your <code>www</code> directory on our servers, which can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Wordpress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. Now we are ready to install Wordpress, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace username with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. The setup will ask you for your database configuration: *'''Database Name/Databasenaam:''' This is the name of the MySQL database you just created. *'''Username/Gebruikersnaam:''' The name you used during the creation of your database account. *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> Afterwards, you can proceed the installation. At a certain point, you receive a notification to log in on Wordpress. This means you have successfully installed your own Wordpress website. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 743a20c4aa40e3bcfc4d3a3521eb6ce996f4950b 981 980 2019-11-04T12:29:57Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you need to download Wordpress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your <code>www</code> directory on our servers, which can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Wordpress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. Now we are ready to install Wordpress, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace username with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. The setup will ask you for your database configuration: *'''Database Name/Databasenaam:''' This is the name of the MySQL database you just created. *'''Username/Gebruikersnaam:''' Your username *'''Password/Wachtwoord:''' The password you used during the creation of your database account. *'''Database Host/Hostnaam:''' This is has to be: <code>mysql.ulyssis.org</code> *'''Table Prefix:''' You do not have to change this field.<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> Afterwards, you can proceed the installation. At a certain point, you receive a notification to log in on Wordpress. This means you have successfully installed your own Wordpress website. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] bfaa22c68480e1ace96815d0cc0fdab3a56e29f6 982 981 2019-11-04T12:32:58Z Casper 39 wikitext text/x-wiki ==How to install Wordpress for your account== First you need to download Wordpress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your <code>www</code> directory on our servers, which can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Wordpress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. Now we are ready to install Wordpress, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace username with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. The setup will ask you for your database configuration: *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Table Prefix:''' only change this if you have multiple installations of wordpress in your database<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> Afterwards, you can proceed the installation. At a certain point, you receive a notification to log in on Wordpress. This means you have successfully installed your own Wordpress website. ==Setting up multiple instances of Wordpress== If you want to have multiple instances of a Wordpress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Wordpress installation, i.e. the steps in the section above. You can also use Wordpress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] bd252db50a308c3c0b0ad91fc81b925fa7b327a8 984 982 2019-11-04T12:35:10Z Casper 39 wikitext text/x-wiki ==How to install WordPress for your account== First you need to download WordPress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your <code>www</code> directory on our servers, which can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install WordPress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. Now we are ready to install WordPress, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace username with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. The setup will ask you for your database configuration: *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Table Prefix:''' only change this if you have multiple installations of WordPress in your database<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> Afterwards, you can proceed the installation. At a certain point, you receive a notification to log in on WordPress. This means you have successfully installed your own WordPress website. ==Setting up multiple instances of WordPress== If you want to have multiple instances of a WordPress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular WordPress installation, i.e. the steps in the section above. You can also use WordPress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] de6dc91cc77642b32fe122b090253a82d5af8d35 985 984 2019-11-04T12:37:11Z Bert 8 Bert moved page [[Setting up Wordpress]] to [[Setting up WordPress]] wikitext text/x-wiki ==How to install WordPress for your account== First you need to download WordPress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your <code>www</code> directory on our servers, which can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install WordPress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. Now we are ready to install WordPress, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace username with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. The setup will ask you for your database configuration: *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Table Prefix:''' only change this if you have multiple installations of WordPress in your database<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> Afterwards, you can proceed the installation. At a certain point, you receive a notification to log in on WordPress. This means you have successfully installed your own WordPress website. ==Setting up multiple instances of WordPress== If you want to have multiple instances of a WordPress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular WordPress installation, i.e. the steps in the section above. You can also use WordPress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] de6dc91cc77642b32fe122b090253a82d5af8d35 987 985 2019-11-04T12:37:49Z Bert 8 wikitext text/x-wiki ==How to install WordPress for your account== First you need to download WordPress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your <code>www</code> directory on our servers, which can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install WordPress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. Now we are ready to install WordPress, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace username with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. The setup will ask you for your database configuration: *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Table Prefix:''' only change this if you have multiple installations of WordPress in your database<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]]<br> Afterwards, you can proceed the installation. At a certain point, you receive a notification to log in on WordPress. This means you have successfully installed your own WordPress website. ==Setting up multiple instances of WordPress== If you want to have multiple instances of a WordPress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular WordPress installation, i.e. the steps in the section above. You can also use WordPress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 662b1902dd5cb2b2dcaddeaa6f65e95f1c45bb44 988 987 2019-11-04T12:38:02Z Bert 8 wikitext text/x-wiki ==How to install WordPress for your account== First you need to download WordPress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your <code>www</code> directory on our servers, which can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install WordPress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. Now we are ready to install WordPress, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace username with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. The setup will ask you for your database configuration: *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Table Prefix:''' only change this if you have multiple installations of WordPress in your database<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]] Afterwards, you can proceed the installation. At a certain point, you receive a notification to log in on WordPress. This means you have successfully installed your own WordPress website. ==Setting up multiple instances of WordPress== If you want to have multiple instances of a WordPress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular WordPress installation, i.e. the steps in the section above. You can also use WordPress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] fb5bd449d181d9becc53e9816934c83b5f0fad78 989 988 2019-11-04T12:47:44Z Casper 39 wikitext text/x-wiki ==How to install WordPress for your account== First you need to download WordPress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your <code>www</code> directory on our servers, which can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install WordPress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. Now we are ready to install WordPress, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace username with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. The setup will ask you for your database configuration: *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Table Prefix:''' only change this if you have multiple installations of WordPress in your database<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]] In the next step you have to fill in your own preferences. Finally you will be prompted to log into your WordPress website. ==Setting up multiple instances of WordPress== If you want to have multiple instances of a WordPress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular WordPress installation, i.e. the steps in the section above. You can also use WordPress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] abcf39502ae291e9a8fb5e870e0a2f6e810b1029 990 989 2019-11-04T12:48:14Z Casper 39 wikitext text/x-wiki ==How to install WordPress for your account== First you need to download WordPress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your <code>www</code> directory on our servers, which can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install WordPress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. Now we are ready to install WordPress, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace username with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. The setup will ask you for your database configuration: *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Table Prefix:''' only change this if you have multiple installations of WordPress in your database<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]] In the next step you need to fill in your own preferences. Finally you will be prompted to log into your WordPress website. ==Setting up multiple instances of WordPress== If you want to have multiple instances of a WordPress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular WordPress installation, i.e. the steps in the section above. You can also use WordPress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] aeb554f46eef28397b2d66f5fed0e77a3e93ba6b 991 990 2019-11-04T12:50:07Z Casper 39 wikitext text/x-wiki ==How to install WordPress for your account== First you need to download WordPress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your <code>www</code> directory on our servers, which can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install WordPress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. Now we are ready to install WordPress, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace username with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. The setup will ask you for your database configuration: *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Table Prefix:''' only change this if you have multiple installations of WordPress in your database<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]] In the next step you need to fill in your own preferences. Finally you will be prompted to log into your WordPress website. Now the installation is finished.<br> ==Setting up multiple instances of WordPress== If you want to have multiple instances of a WordPress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular WordPress installation, i.e. the steps in the section above. You can also use WordPress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 095f3d793acf09003ade7cb29b1cfdfcfb82325a 992 991 2019-11-04T12:55:47Z Casper 39 wikitext text/x-wiki ==How to install WordPress for your account== First you need to download WordPress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your <code>www</code> directory on our servers, which can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install WordPress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. Now we are ready to install WordPress, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace username with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. The setup will ask you for your database configuration: *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Table Prefix:''' only change this if you have multiple installations of WordPress in your database<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]] In the next step you need to fill in your own preferences. Finally you will be prompted to log into your WordPress website. Now the installation is finished. To help you design your website, there are a few guides from WordPress that can help you: *https://wordpress.org/support/article/first-steps-with-wordpress-b/ *https://wordpress.org/support/article/using-themes/#get-new-themes *https://wordpress.org/support/article/managing-plugins/ ==Setting up multiple instances of WordPress== If you want to have multiple instances of a WordPress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular WordPress installation, i.e. the steps in the section above. You can also use WordPress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 9b051129bc0b29d422426706165eb3ef5d945a6c 1013 992 2019-11-10T21:29:12Z Pcy 37 layout van 'username' wikitext text/x-wiki ==How to install WordPress for your account== First you need to download WordPress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your <code>www</code> directory on our servers, which can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install WordPress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. Now we are ready to install WordPress, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. The setup will ask you for your database configuration: *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Table Prefix:''' only change this if you have multiple installations of WordPress in your database<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]] In the next step you need to fill in your own preferences. Finally you will be prompted to log into your WordPress website. Now the installation is finished. To help you design your website, there are a few guides from WordPress that can help you: *https://wordpress.org/support/article/first-steps-with-wordpress-b/ *https://wordpress.org/support/article/using-themes/#get-new-themes *https://wordpress.org/support/article/managing-plugins/ ==Setting up multiple instances of WordPress== If you want to have multiple instances of a WordPress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular WordPress installation, i.e. the steps in the section above. You can also use WordPress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 14a8d2c929726183b358982ba9dd5512f7a9ae76 1016 1013 2019-11-15T18:25:21Z Casper 39 wikitext text/x-wiki ==How to install WordPress for your account== First you need to download WordPress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your webroot directory on our servers. Mostly this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install WordPress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. {{warning|Warning!|Postgresql databases are not supported by WordPress, only use MySQL databases.}} Now we are ready to install WordPress, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. The setup will ask you for your database configuration: *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Table Prefix:''' only change this if you have multiple installations of WordPress in your database<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]] In the next step you need to fill in your own preferences. Finally you will be prompted to log into your WordPress website. Now the installation is finished. To help you design your website, there are a few guides from WordPress that can help you: *https://wordpress.org/support/article/first-steps-with-wordpress-b/ *https://wordpress.org/support/article/using-themes/#get-new-themes *https://wordpress.org/support/article/managing-plugins/ ==Setting up multiple instances of WordPress== If you want to have multiple instances of a WordPress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular WordPress installation, i.e. the steps in the section above. You can also use WordPress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 6c596a9d9a43942bd62d3f28b8f115bd547f556d 1019 1016 2019-11-15T18:42:11Z Casper 39 wikitext text/x-wiki ==How to install WordPress for your account== First you need to download WordPress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your webroot directory on our servers. Mostly this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install WordPress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there.<br> '''Warning:''' Postgresql databases are not supported by WordPress, only use MySQL databases. Now we are ready to install WordPress, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. The setup will ask you for your database configuration: *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Table Prefix:''' only change this if you have multiple installations of WordPress in your database<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]] In the next step you need to fill in your own preferences. Finally you will be prompted to log into your WordPress website. Now the installation is finished. To help you design your website, there are a few guides from WordPress that can help you: *https://wordpress.org/support/article/first-steps-with-wordpress-b/ *https://wordpress.org/support/article/using-themes/#get-new-themes *https://wordpress.org/support/article/managing-plugins/ ==Setting up multiple instances of WordPress== If you want to have multiple instances of a WordPress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular WordPress installation, i.e. the steps in the section above. You can also use WordPress' [https://codex.wordpress.org/Create_A_Network multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 2c30284ac53c346e0a52a5ac11e4e6434e6124f2 1020 1019 2019-11-15T18:47:19Z Casper 39 wikitext text/x-wiki ==How to install WordPress for your account== First you need to download WordPress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your webroot directory on our servers. Mostly this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install WordPress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there.<br> '''Warning:''' Postgresql databases are not supported by WordPress, only use MySQL databases. Now we are ready to install WordPress, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. The setup will ask you for your database configuration: *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Table Prefix:''' only change this if you have multiple installations of WordPress in your database<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]] In the next step you need to fill in your own preferences. Finally you will be prompted to log into your WordPress website. Now the installation is finished. To help you design your website, there are a few guides from WordPress that can help you: *https://wordpress.org/support/article/first-steps-with-wordpress-b/ *https://wordpress.org/support/article/using-themes/#get-new-themes *https://wordpress.org/support/article/managing-plugins/ ==Setting up multiple instances of WordPress== If you want to have multiple instances of a WordPress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular WordPress installation, i.e. the steps in the section above. You can also use WordPress' [https://wordpress.org/support/article/create-a-network/ multisite] option. If you need more help with this, you can find it here: [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 5e66b9fd509d1a66fabaf470ea9b004f0b6b7889 0 3 983 791 2019-11-04T12:33:55Z Bert 8 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] * [[Secure file permissions]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Sending email from websites]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL|Getting SSL (https-security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] * [[Claiming a port]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up WordPress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] * [[Using PHPPgAdmin]] * [[Using Adminer]] * [[Making Backups]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ ce837ed05a9610deefc5d00a5539a0709e2f5770 0 141 986 2019-11-04T12:37:11Z Bert 8 Bert moved page [[Setting up Wordpress]] to [[Setting up WordPress]] wikitext text/x-wiki #REDIRECT [[Setting up WordPress]] 89bbb9593896d3b705406288e52ed5655144d749 0 127 993 948 2019-11-04T17:48:16Z Bert 8 wikitext text/x-wiki You can access both your MySQL and PostgreSQL databases using Adminer, though not both at the same time. This application can be found on https://adminer.ulyssis.org. To login you need to use your MySQL or PostgreSQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your passwords you can get it from your websites configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. You can change your database passwords through our control panel [https://ucc.ulyssis.org/ UCC], but keep in mind to then also change the password in relevant configuration files, or you applications may stop working correctly. To use MySQL, please use the server <code>mysql.ulyssis.org</code>. In case of PostgreSQL, please use <code>pgsql.ulyssis.org</code>. == Basic Usage == When logging in using MySQL, you will see an overview of all your databases. When using PostgreSQL you will see all databases that have been created by all of our users (this is a known problem with Adminer), though you won't be able to view them. You can then view databases and tables. For each table you can view the records, view and change the structure, add records, take backups, etc. Sadly no official documentation is available, though Adminer has a [https://sourceforge.net/p/adminer/discussion/ forum] where you can ask for help. == Making Backups == {{notice|Keep in mind|If you are backing up and/or restoring a larger database, it's advised to use command line tools since they are more performant than webtools and don't have any timeouts that could interrupt your backup/restore. Please refer to [[Making Backups]] for more details.}} Adminer has an export option which can be used to backup the structure and/or data of databases and tables. When no database or table has been selected, the export button in the sidebar allows to export all databases at the same time. When a specific database or table is selected, that database or table is exported. You can specify to save the file, in what format, and whether structures and data should be dropped, truncated or created. You can later restore backups by uploading the file through the form available through the import button in the sidebar. To make restoring easier, we suggest you backup individual databases or even individual tables and use the SQL format. [[Category:Databases]] 3da6b45f7e1fe03fdcc6250a66624fab327bf0a0 994 993 2019-11-04T17:48:33Z Bert 8 wikitext text/x-wiki You can access both your MySQL and PostgreSQL databases using Adminer, though not both at the same time. This application can be found on https://adminer.ulyssis.org. To login you need to use your MySQL or PostgreSQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your passwords you can get it from your websites configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. You can change your database passwords through our control panel [https://ucc.ulyssis.org/ UCC], but keep in mind to then also change the password in relevant configuration files, or you applications may stop working correctly. To use MySQL, please use the server <code>mysql.ulyssis.org</code>. In case of PostgreSQL, please use <code>pgsql.ulyssis.org</code>. == Basic Usage == When logging in using MySQL, you will see an overview of all your databases. When using PostgreSQL you will see all databases that have been created by all of our users (this is a known problem with Adminer), though you won't be able to view them. You can then view databases and tables. For each table you can view the records, view and change the structure, add records, take backups, etc. Sadly no official documentation is available, though Adminer has a [https://sourceforge.net/p/adminer/discussion/ forum] where you can ask for help. == Making Backups == {{notice|Keep in mind|If you are backing up and/or restoring a larger database, it's advised to use command line tools since they are more performant than webtools and don't have any timeouts that could interrupt your backup/restore. Please refer to [[Making Backups]] for more details.}} Adminer has an export option which can be used to backup the structure and/or data of databases and tables. When no database or table has been selected, the export button in the sidebar allows to export all databases at the same time. When a specific database or table is selected, that database or table is exported. You can specify to save the file, in what format, and whether structures and data should be dropped, truncated or created. You can later restore backups by uploading the file through the form available through the import button in the sidebar. To make restoring easier, we suggest you backup individual databases or even individual tables and use the SQL format. [[Category:Databases]] 60ea712588d792d0df666823f91461e0de2bd4c0 1011 994 2019-11-10T21:25:03Z Pcy 37 fix typos wikitext text/x-wiki You can access both your MySQL and PostgreSQL databases using Adminer, though not both at the same time. This application can be found on https://adminer.ulyssis.org. To login you need to use your MySQL or PostgreSQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your passwords you can get it from your website's configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. You can change your database passwords through our control panel [https://ucc.ulyssis.org/ UCC], but keep in mind to then also change the password in relevant configuration files, or your applications may stop working correctly. To use MySQL, please use the server <code>mysql.ulyssis.org</code>. In case of PostgreSQL, please use <code>pgsql.ulyssis.org</code>. == Basic Usage == When logging in using MySQL, you will see an overview of all your databases. When using PostgreSQL you will see all databases that have been created by all of our users (this is a known problem with Adminer), though you won't be able to view them. You can then view databases and tables. For each table you can view the records, view and change the structure, add records, take backups, etc. Sadly no official documentation is available, though Adminer has a [https://sourceforge.net/p/adminer/discussion/ forum] where you can ask for help. == Making Backups == {{notice|Keep in mind|If you are backing up and/or restoring a larger database, it's advised to use command line tools since they are more performant than webtools and don't have any timeouts that could interrupt your backup/restore. Please refer to [[Making Backups]] for more details.}} Adminer has an export option which can be used to backup the structure and/or data of databases and tables. When no database or table has been selected, the export button in the sidebar allows to export all databases at the same time. When a specific database or table is selected, that database or table is exported. You can specify to save the file, in what format, and whether structures and data should be dropped, truncated or created. You can later restore backups by uploading the file through the form available through the import button in the sidebar. To make restoring easier, we suggest you backup individual databases or even individual tables and use the SQL format. [[Category:Databases]] 8847559aab160715f666183957dd748aba587953 0 103 995 750 2019-11-04T19:09:22Z Bert 8 wikitext text/x-wiki While most webhosting providers give you access to a few or even just one programming language and a set amount of libraries, ULYSSIS prefers to offer more flexibility. We hope to give our users the chance to experiment with different languages, libraries and tools. There are of course limits to what is realistic for us to install. More on that below. == Using a programming language, library or tool that is not installed == If the package that you would like us to install is available in the software repository of our current operating system, then that is usually not a problem. We currently use Ubuntu on all our servers, specifically, we upgrade to the latest LTS every summer vacation following the release of a new one. You can verify which version we are running by executing "cat /etc/lsb-release" on one of our shellservers. After you have verified what version we are running, you can refer to https://packages.ubuntu.com/ to check whether your package is available in that version of Ubuntu. If it is, then you can contact us by email on ulyssis@ulyssis.org which package or packages you would like to have installed, and what you will be using it for. You will most likely get a positive response. If your package is not in the repository, you will have to go for a [[Installing packages#Manual installation|Manual installation]]. == Using a newer/different version == As you can read in the section concerning the installation of new packages, we only offer the version available in the repository of the version of Ubuntu that we are running. In most cases, this means you will have to wait for a version upgrade with the next LTS release, or go for a [[Installing packages#Manual installation|Manual installation]]. However, there are some exceptions. Sometimes multiple version will be available in the repository, such as with Python 2 and 3, or Perl 5 and 6. In such cases, you can refer to the section above for instructions on how to request an installation. == Manual installation == If you want to install a piece of software that is not available in the repository or you wish to install another version, you can always install it manually onto your account. It is important to keep in mind that ULYSSIS will not support manually installed software, and that you are fully responsible for the security of this software. You are free to ask us questions, but we will most probably not help you. If you do require a manual installation of specific software, we expect you to be capable of maintaining it as well. The way you install your software differs depending on the software. You could be using tools such as pip, gem or npm to install to a directory in your home folder, you could be using a virtual environment, or you could be compiling your own binary. We suggest you look at the documentation of the software you're using very thoroughly, and make sure you are comfortable with what you are doing and aware of your responsibilities. After installing your software locally onto your account, you will probably want to add an alias in your dotfiles (for example .profile or .bashrc) to make using your manually installed version easier. In case you are using your piece of software for a web service, you will want to make sure you edit your fastcgi script or any other involved scripts to use your binary by changing the path or hardcoding the location. == Node.js == We do not offer Node.js by default because we can't give you the most recent release. But you can use nvm ([https://github.com/creationix/nvm Node Version Manager]) which installs the required version for you. The installation should be straightforward and a guide can be found [https://github.com/creationix/nvm#installation here]. [[Category:Shell]] 4abe86a7077db4a3e3af4e5d7430c52a19ae6b74 0 41 1000 952 2019-11-05T22:26:26Z Yoa 30 /* A backup of your databases */ wikitext text/x-wiki ULYSSIS takes backups of all files, databases, settings and repositories 1-4 times a week. These backups can be restored in case of severe server failure or in case of an emergency (if for example a user by mistake deletes all of their site). It is, however, more convenient that users take their own backups when they do experimental things on their account. == A backup of your files == You can use the methods described in [[Accessing your files]] to download a copy of all of your files or specific folders you will be working on. If something goes wrong, you can easily restore files to a previous state by re-uploading those you have downloaded and saved. == A backup of your databases == To take a backup of your database you simple use the export function of PHPMyAdmin, PHPPgAdmin and/or Adminer as described on [[Using PHPMyAdmin]], [[Using PHPPgAdmin]] and [[Using Adminer]]. If you are backing up and/or restoring a larger database, it's advisale to use command line tools since they are more performant than webtools and don't have any timeouts that could interrupt your backup/restore. === MySQL command line === To take a backup, execute the following command on one of our shellservers (with the right database name filled in): mysqldump -h mysql.ulyssis.org -p username_database > backup.sql This will prompt you for your database password (please refer to [[Using MySQL]] if you don't know your password) and then dump the entire database to backup.sql file as SQL. To restore your backup you can use the mysql command on one of our shellservers (with the right database name filled in), whatever SQL file you specify will be executed: mysql -h mysql.ulyssis.org -p username_database < backup.sql Please keep in mind that by default mysqldump includes statements in the SQL file that will delete all tables that will be restored. If you wish to have more control over different settings when taking or restoring please, you can refer to the respective man pages of mysqldump and mysql using <code>man mysqldump</code> and <code>man mysql</code> === PostgreSQL command line === To take a backup, execute the following command on one of our shellservers (with the right database name filled in): pg_dump -h pgsql.ulyssis.org -W --clean username_database > backup.sql This will prompt you for your database password (please refer to [[Using PostgreSQL]] if you don't know your password) and then dump the entire database to backup.sql file as SQL with COPY statements. If you prefer INSERT instead of COPY statements, you can add <code>--inserts</code> to your command. To restore your backup you can use the pg_restore command on one of our shellservers (with the right database name filled in), whatever SQL file you specify will be executed: psql -h pgsql.ulyssis.org -W username_database < backup.sql Please keep in mind that because we specified <code>--clean</code> earlier, our SQL file includes statements that will delete all tables, sequences, functions and schemas that will be restored. If you wish to have more control over different settings when taking or restoring please, you can refer to the respective man pages of pg_dump and psql using <code>man pg_dump</code> and <code>man psql</code> [[Category:Files]] [[Category:Databases]] e3345907b2782ef14413b5ecd00eaa819ee1672e 1008 1000 2019-11-10T21:19:47Z Pcy 37 fix typos wikitext text/x-wiki ULYSSIS takes backups of all files, databases, settings and repositories 1-4 times a week. These backups can be restored in case of severe server failure or in case of an emergency (if for example a user by mistake deletes all of their site). It is, however, more convenient that users take their own backups when they do experiments on their account. == A backup of your files == You can use the methods described in [[Accessing your files]] to download a copy of all of your files or specific folders you will be working on. If something goes wrong, you can easily restore files to a previous state by re-uploading those you have downloaded and saved. == A backup of your databases == To take a backup of your database you simply use the export function of PHPMyAdmin, PHPPgAdmin and/or Adminer as described on [[Using PHPMyAdmin]], [[Using PHPPgAdmin]] and [[Using Adminer]]. If you are backing up and/or restoring a larger database, it's advisable to use command line tools since they are more performant than the web-based tools and don't have any timeouts that could interrupt your backup/restore. === MySQL command line === To take a backup, execute the following command on one of our shellservers (with the right database name filled in): mysqldump -h mysql.ulyssis.org -p username_database > backup.sql This will prompt you for your database password (please refer to [[Using MySQL]] if you don't know your password) and then dump the entire database to backup.sql file as SQL. To restore your backup you can use the mysql command on one of our shellservers (with the right database name filled in), whatever SQL file you specify will be executed: mysql -h mysql.ulyssis.org -p username_database < backup.sql Please keep in mind that by default mysqldump includes statements in the SQL file that will delete all tables that will be restored. If you wish to have more control over different settings when taking or restoring please, you can refer to the respective man pages of mysqldump and mysql using <code>man mysqldump</code> and <code>man mysql</code> === PostgreSQL command line === To take a backup, execute the following command on one of our shellservers (with the right database name filled in): pg_dump -h pgsql.ulyssis.org -W --clean username_database > backup.sql This will prompt you for your database password (please refer to [[Using PostgreSQL]] if you don't know your password) and then dump the entire database to backup.sql file as SQL with COPY statements. If you prefer INSERT instead of COPY statements, you can add <code>--inserts</code> to your command. To restore your backup you can use the pg_restore command on one of our shellservers (with the right database name filled in), whatever SQL file you specify will be executed: psql -h pgsql.ulyssis.org -W username_database < backup.sql Please keep in mind that because we specified <code>--clean</code> earlier, our SQL file includes statements that will delete all tables, sequences, functions and schemas that will be restored. If you wish to have more control over different settings when taking or restoring please, you can refer to the respective man pages of pg_dump and psql using <code>man pg_dump</code> and <code>man psql</code> [[Category:Files]] [[Category:Databases]] 3afd3df40de5ca5130c42286bd34300804a91763 0 37 1001 856 2019-11-05T22:44:08Z Yoa 30 /* FastCGI */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <syntaxhighlight lang="apache">Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</syntaxhighlight> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. {{warning|Warning!|Do not place sensitive files inside the web accessible folder. Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.}} It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [[Managing_Cron_jobs | cronjob]] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than were it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> Or, for Python 3: <pre>virtualenv ~/.venv --python=python3</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <syntaxhighlight lang="python">#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </syntaxhighlight> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [http://flask.pocoo.org/docs/0.10/deploying/fastcgi/ Flask documentation for FastCGI] [[Category:Webserver]] f96a4c777fec88ce4c0a6c8c34063762915389f8 1014 1001 2019-11-10T21:40:13Z Pcy 37 fix flask link wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where you ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <syntaxhighlight lang="apache">Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</syntaxhighlight> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. {{warning|Warning!|Do not place sensitive files inside the web accessible folder. Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.}} It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [[Managing_Cron_jobs | cronjob]] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than were it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> Or, for Python 3: <pre>virtualenv ~/.venv --python=python3</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <syntaxhighlight lang="python">#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </syntaxhighlight> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [https://flask.palletsprojects.com/en/1.1.x/deploying/fastcgi/ Flask documentation for FastCGI] [[Category:Webserver]] abeb587c872b34be9bdcf795ffc6e7c52d189ee6 1018 1014 2019-11-15T18:37:22Z Thomasd 40 verwijder verkeerde "you" wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <syntaxhighlight lang="apache">Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</syntaxhighlight> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. {{warning|Warning!|Do not place sensitive files inside the web accessible folder. Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.}} It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [[Managing_Cron_jobs | cronjob]] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than were it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> Or, for Python 3: <pre>virtualenv ~/.venv --python=python3</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <syntaxhighlight lang="python">#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </syntaxhighlight> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [https://flask.palletsprojects.com/en/1.1.x/deploying/fastcgi/ Flask documentation for FastCGI] [[Category:Webserver]] cdc3aff5646844aca8d1fb9c7c9574af61aa8089 0 114 1002 805 2019-11-05T22:48:34Z Yoa 30 /* How? */ wikitext text/x-wiki Sending email is fairly similar on most hosting services. ULYSSIS hosting is not too different in that sense. We do use a queueing system to detect accounts that are being abused by malicious actors to send spam. == How? == In PHP and most other programming languages, content management systems (CMS), and frameworks, you can use the builtin email function. This may be referred to with names such as builtin, default, standard, local or sendmail. == Delay and limitations == Because of the large amount of users on our hosting services, security breaches and misconfigurations due to user mismanagement happen from time to time. As many malicious actors focus their efforts on abusing servers with a good reputation for the distribution of spam, it is not uncommon to find several thousands of emails being sent once a problem occurs. To combat this, ULYSSIS hosting delays sending of emails for up to 5 minutes and verifies a certain amount (50) of email is never surpassed. If at any point the level is surpassed, ULYSSIS is notified and can take action, while probable spam is stopped from being transmitted. Therefore it is important to keep a potential delay in time when expecting email from your website, but also not to send vast amount of email all at once. It is in general good practice to spread the transmission of for example an email list with several hundred participants. [[Category:Webserver]] 0a7b521a455c356b1e6cef4980c5f6d00e058412 0 96 1003 744 2019-11-05T22:58:21Z Yoa 30 /* Introduction */ wikitext text/x-wiki ==Introduction== Content Management Systems, or CMS's, are easy tools to set up a website without requiring much programming or configuration. However, as is common in a lot of popular and wide-spread software, bugs or errors in the code occur. These errors can be exploited by hackers to gain access to websites or databases connected to those CMS's. Whenever a new update for a CMS, or other popular software (MediaWiki, PhpBB) is released, hackers will know which security flaws have been fixed, and try to hack websites using this knowledge. This is why it's critical to update a CMS, plugins/themes, or any related software as soon as the update comes out. To help you facilitate this, we have created a tool to help you keep the most popular software up-to-date. Currently this feature is only active if you have an organisation or student union (kring/facultair overlegorgaan) account. ==I received an e-mail!== If you receive an e-mail from the Version Checker, it's best you update the software mentioned in the e-mail as soon as possible. Make sure to download the latest public version, not just any newer version. It's also best to check if any other software you run is up-to-date: not all software is checked by the tool. (As seen below) ==Supported Software== * Drupal, Drupal Modules, Drupal Themes * Joomla (Joomla Plugins are not supported yet) * MediaWiki (MediaWiki Extensions and Themes are not supported yet) * PhpBB, PhpBB Plugins, PhpBB Styles * WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the Version Checker performs the following steps: * Retrieve all outdated software and respective locations from a database, and check their version * Mail accounts using outdated software * Scan relevant files, detect supported software, and store in database ==Stored Data== The following data is stored in the database: * The location of the CMS, plugin/extension or theme * The responsible organisation or student union (kring/facultair overlegorgaan) * The detected software version * The type and name of the software * The update URL for the software * The date the entry was added ==Ignored Paths== The Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. ==Ignored Organisations/Student Unions== In addition to the ignored paths feature, the Version Checker can also ignore specific Organisations or Student Unions entirely. This feature is possible on request, but only after extensive deliberation with ULYSSIS. Enabling this feature also carries possible consequences: no more mails about outdated software, ever (unless enabled on request), no support if/when your account gets hacked (the account will be expired immediately)... [[Category:CMSs]] [[Category:Security & anti-spam]] 2459ca6f7001187a9fda333bbcd3bab448382638 1004 1003 2019-11-05T22:58:57Z Yoa 30 /* I received an e-mail! */ wikitext text/x-wiki ==Introduction== Content Management Systems, or CMS's, are easy tools to set up a website without requiring much programming or configuration. However, as is common in a lot of popular and wide-spread software, bugs or errors in the code occur. These errors can be exploited by hackers to gain access to websites or databases connected to those CMS's. Whenever a new update for a CMS, or other popular software (MediaWiki, PhpBB) is released, hackers will know which security flaws have been fixed, and try to hack websites using this knowledge. This is why it's critical to update a CMS, plugins/themes, or any related software as soon as the update comes out. To help you facilitate this, we have created a tool to help you keep the most popular software up-to-date. Currently this feature is only active if you have an organisation or student union (kring/facultair overlegorgaan) account. ==I received an e-mail!== If you receive an e-mail from the Version Checker, it's best you update the software mentioned in the e-mail as soon as possible. Make sure to download the latest public version, not just any newer version. It's also best to check if any other software you run is up-to-date: not all software is checked by the tool (as seen below). ==Supported Software== * Drupal, Drupal Modules, Drupal Themes * Joomla (Joomla Plugins are not supported yet) * MediaWiki (MediaWiki Extensions and Themes are not supported yet) * PhpBB, PhpBB Plugins, PhpBB Styles * WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the Version Checker performs the following steps: * Retrieve all outdated software and respective locations from a database, and check their version * Mail accounts using outdated software * Scan relevant files, detect supported software, and store in database ==Stored Data== The following data is stored in the database: * The location of the CMS, plugin/extension or theme * The responsible organisation or student union (kring/facultair overlegorgaan) * The detected software version * The type and name of the software * The update URL for the software * The date the entry was added ==Ignored Paths== The Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. ==Ignored Organisations/Student Unions== In addition to the ignored paths feature, the Version Checker can also ignore specific Organisations or Student Unions entirely. This feature is possible on request, but only after extensive deliberation with ULYSSIS. Enabling this feature also carries possible consequences: no more mails about outdated software, ever (unless enabled on request), no support if/when your account gets hacked (the account will be expired immediately)... [[Category:CMSs]] [[Category:Security & anti-spam]] bcf5e676abf7be254aa7eb13c4c5e65af420c8bb 1005 1004 2019-11-05T23:03:02Z Yoa 30 /* Ignored Organisations/Student Unions */ wikitext text/x-wiki ==Introduction== Content Management Systems, or CMS's, are easy tools to set up a website without requiring much programming or configuration. However, as is common in a lot of popular and wide-spread software, bugs or errors in the code occur. These errors can be exploited by hackers to gain access to websites or databases connected to those CMS's. Whenever a new update for a CMS, or other popular software (MediaWiki, PhpBB) is released, hackers will know which security flaws have been fixed, and try to hack websites using this knowledge. This is why it's critical to update a CMS, plugins/themes, or any related software as soon as the update comes out. To help you facilitate this, we have created a tool to help you keep the most popular software up-to-date. Currently this feature is only active if you have an organisation or student union (kring/facultair overlegorgaan) account. ==I received an e-mail!== If you receive an e-mail from the Version Checker, it's best you update the software mentioned in the e-mail as soon as possible. Make sure to download the latest public version, not just any newer version. It's also best to check if any other software you run is up-to-date: not all software is checked by the tool (as seen below). ==Supported Software== * Drupal, Drupal Modules, Drupal Themes * Joomla (Joomla Plugins are not supported yet) * MediaWiki (MediaWiki Extensions and Themes are not supported yet) * PhpBB, PhpBB Plugins, PhpBB Styles * WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the Version Checker performs the following steps: * Retrieve all outdated software and respective locations from a database, and check their version * Mail accounts using outdated software * Scan relevant files, detect supported software, and store in database ==Stored Data== The following data is stored in the database: * The location of the CMS, plugin/extension or theme * The responsible organisation or student union (kring/facultair overlegorgaan) * The detected software version * The type and name of the software * The update URL for the software * The date the entry was added ==Ignored Paths== The Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. ==Ignored Organisations/Student Unions== In addition to the ignored paths feature, the Version Checker can also ignore specific Organisations or Student Unions entirely. This feature is possible on request, but only after extensive deliberation with ULYSSIS. Enabling this feature also carries possible consequences: no more mails about outdated software, ever (unless enabled on request), and no support if/when your account gets hacked (the account will be suspended immediately). [[Category:CMSs]] [[Category:Security & anti-spam]] d650088078673f69050db7dc0f79b1471631533c 1006 1005 2019-11-05T23:04:05Z Yoa 30 wikitext text/x-wiki ==Introduction== Content Management Systems, or CMS's, are easy tools to set up a website without requiring much programming or configuration. However, as is common in a lot of popular and wide-spread software, bugs or errors in the code occur. These errors can be exploited by hackers to gain access to websites or databases connected to those CMS's. Whenever a new update for a CMS, or other popular software (MediaWiki, PhpBB) is released, hackers will know which security flaws have been fixed, and try to hack websites using this knowledge. This is why it's critical to update a CMS, plugins/themes, or any related software as soon as the update comes out. To help you facilitate this, we have created a tool to help you keep the most popular software up-to-date. Currently this feature is only active if you have an organisation or student union (kring/facultair overlegorgaan) account. ==I received an e-mail!== If you receive an e-mail from the Version Checker, it's best you update the software mentioned in the e-mail as soon as possible. Make sure to download the latest public version, not just any newer version. It's also best to check if any other software you run is up-to-date: not all software is checked by the tool (as seen below). ==Supported Software== * Drupal, Drupal Modules, Drupal Themes * Joomla (Joomla Plugins are not supported yet) * MediaWiki (MediaWiki Extensions and Themes are not supported yet) * PhpBB, PhpBB Plugins, PhpBB Styles * WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the Version Checker does the following: * Scan relevant files, detect supported software, and store in database * Check the version and validity of outdated software * Mail accounts using outdated software ==Stored Data== The following data is stored in the database: * The location of the CMS, plugin/extension or theme * The responsible organisation or student union (kring/facultair overlegorgaan) * The detected software version * The type and name of the software * The update URL for the software * The date the entry was added ==Ignored Paths== The Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. ==Ignored Organisations/Student Unions== In addition to the ignored paths feature, the Version Checker can also ignore specific Organisations or Student Unions entirely. This feature is possible on request, but only after extensive deliberation with ULYSSIS. Enabling this feature also carries possible consequences: no more mails about outdated software, ever (unless enabled on request), and no support if/when your account gets hacked (the account will be suspended immediately). [[Category:CMSs]] [[Category:Security & anti-spam]] f8049ae42241e036770f395203bc3d50a550cb8f 0 43 1007 725 2019-11-10T19:27:53Z Casper 39 wikitext text/x-wiki You may want to receive e-mail from ulyssis on another email provider. It is very easy to set this up. == Change the forwarders for your @ulyssis.org email address == # Go to ucc.ulyssis.org and log in with your username and password. # On the right side, click on '''Mail'''. # Under '''Address forward''' you can change the forward address of your ULYSSIS mail by clicking on '''edit'''. # Choose '''forward''' and enter the email address you want to forward your ULYSSIS mail to and save the changes. # If you forward to Gmail, Hotmail. or use Thunderbird, we recommend looking at [[Using a forwarder as an alias]] so you can send mails under the forwarding address instead of just your own. == Change the forwarders for other domains == # Go to ucc.ulyssis.org and log in with your username and password. # On the right side, click on '''Mail'''. [[File:Forwarder Step1.png|700px]] 3. Under '''Virtual Domains''', click on the domain you want to change. [[File:Forwarder Step2.png|700px]] 4. You can change a forwarder by clicking on '''edit''' or on '''Add alias''' and add the forwarders you want. [[File:Forwarder Step3.png|700px]] 5. Save your changes == Use your mailbox and forwarders at the same time == An alternative way to set the forwarders, that will also allow you to use your mailbox and the webinterface, is to use a .forward file. On each line of this file, you can specify to wich addresses you want to forward the email. If one of the addresses is the same as your @ulyssis address, then the mail will also be placed in your ULYSSIS mailbox. In the following example, your @ulyssis email address is <code>user@ulyssis.org</code>. Example .forward file: user@ulyssis.org example@gmail.com example2@skynet.be This will place the email in your ULYSSIS mailbox so that you can access it from the webinterface or your local mailclient. It will also forward the mail to <code>example@gmail.com</code> and <code>example2@skynet.be</code>. To use this, place a .forward file with the prefered email addresses in your homedir, see [[Accessing your files]], and set your forwarder to 'Inbox' in https://ucc.ulyssis.org/mail [[Category:Mail]] 2e2cd59766278f558522df74c729d452440bf334 0 40 1009 950 2019-11-10T21:22:30Z Pcy 37 fix typos wikitext text/x-wiki You can access your MySQL databases using PHPMyAdmin. This application can be found on https://phpmyadmin.ulyssis.org. To login you need to use your MySQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your MySQL password, you can get it from your website's configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. You can change your database passwords through our control panel [https://ucc.ulyssis.org/ UCC], but keep in mind to then also change the password in relevant configuration files, or your applications may stop working correctly. == Basic Usage == Once you've logged in, you will see your username on the left. You can click the plus sign right next to your name to reveal all your databases. You can then view databases and tables. For each table you can view the records, view and change the structure, add records, take backups, etc. Detailed documentation is available on the PHPMyAdmin [https://www.phpmyadmin.net/docs/ official documentation website] == Making Backups == {{notice|Keep in mind|If you are backing up and/or restoring a larger database, it's advised to use command line tools since they are more performant than webtools and don't have any timeouts that could interrupt your backup/restore. Please refer to [[Making Backups]] for more details.}} PHPMyAdmin has an export option which can be used to backup the structure and/or data of databases and tables. When no database or table has been selected, the export tab in the top menu allows to export all databases at the same time. When a specific database or table is selected, that database or table is exported. You can either accept the default settings, or ask for more settings, to specificy whether any checks, DROPs or time settings are required, as well as to specify if you wish to export the structure, the data or both. You can restore backups at a later point in time by uploading the file through the form on the import tab. To make restoring easier, we suggest you backup individual databases or even individual tables. [[Category:Databases]] 54f0c93435cb68a08e41c9116ed9288e25d76794 0 126 1010 949 2019-11-10T21:24:07Z Pcy 37 fix typos wikitext text/x-wiki You can access your PostgreSQL databases using PHPPgAdmin. This application can be found on https://phppgadmin.ulyssis.org. To login you need to use your PostgreSQL password, this password is different from your account password for security reasons as well as convenience. In case you've forgotten your PostgreSQL password you can get it from your website's configuration file. This is usually called config.php, wp-config.php, settings.php or something similar. You can change your database passwords through our control panel [https://ucc.ulyssis.org/ UCC], but keep in mind to then also change the password in relevant configuration files, or your applications may stop working correctly. == Basic Usage == You can login by clicking on the only server in the left sidebar ''PostgreSQL voor gebruikers, kringen en organisaties''. Once you've logged in, you will see an overview of all your databases. You can then view databases, schemas and tables by clicking on them or navigating through the sidebar. For each table you can view the records, view and change the structure, add records, take backups, etc. Official documentation of all functionality is sadly lacking, but you can still refer to [http://phppgadmin.sourceforge.net/doku.php?id=faq_docs the official documentation] == Making Backups == {{notice|Keep in mind|If you are backing up and/or restoring a larger database, it's advised to use command line tools since they are more performant than webtools and don't have any timeouts that could interrupt your backup/restore. Please refer to [[Making Backups]] for more details.}} PHPPgAdmin has an export option which can be used to backup the structure and/or data of databases, schemas and tables, as well as more advanced features such as sequences and functions. When no database, schema or table has been selected, the export tab in the top menu allows to export all databases at the same time. When a specific database or table is selected, that database or table is exported. You can decide whether you wish to export the structure, the data or both, as well as the format and if DROPs need to be included. You can later restore backups by uploading the file through the form on the SQL page (top right corner). To make restoring easier, we suggest you backup individual databases or even individual tables and use the SQL format instead of COPY. [[Category:Databases]] 6eb31c3ab57b3a2e20c291b72fec2bd70dc9e036 0 78 1012 910 2019-11-10T21:26:34Z Pcy 37 zet vertaalde termen in cursief wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. # Set up agenda sync on KU Loket ## Visit [http://kuloket.be/ KU Loket] ## Go to the '''Agenda''' tab [[File:KUL-Agenda-Step1.PNG|thumb|200px]] ## Click '''Agenda sync''' ## Click '''Configure agenda''' (''Agenda instellen'') [[File:KUL-Agenda-Step2.PNG|thumb|200px]] ## Change the switch '''Show schedule in my agenda''' (''Toon uurrooster in mijn agenda'') to '''On'''. [[File:KUL-Agenda-Step3.PNG|thumb|200px]] You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (''Agenda'') # On the top right (below the menu bar), click the '''Share''' (''Delen'') button. A side-panel appears. # Enter a non-KU Leuven email address in the '''Share with''' (''Delen met'') textfield. After filling the email address, press the enter key. # Make sure '''Full details''' (''Volledige informatie'') is selected in the dropdown next to your email address # Click the '''Send''' (''Verzenden'') button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> [[Category:Tutorials]] 7c34d468f636660058088767da0c8cf0c39fe20d 0 10 1021 868 2019-11-20T19:38:26Z Yoa 30 /* Generating the certificates */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, we download the <code>acme.sh</code> script and make it executable: wget https://raw.githubusercontent.com/Neilpang/acme.sh/master/acme.sh chmod +x acme.sh Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be If we provide an email address, for example "email@example.com", Let's Encrypt will remind use to renew our certificates when necessary. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain -d mydomain.be ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] f17b829ceca39b9cbc4af66c38f78fd94834d592 1022 1021 2019-11-20T19:40:48Z Yoa 30 /* Generating the certificates */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, we download the <code>acme.sh</code> script and make it executable: wget https://raw.githubusercontent.com/Neilpang/acme.sh/master/acme.sh chmod +x acme.sh Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be If we provide an email address, for example "email@example.com", Let's Encrypt will remind us to renew our certificates when necessary. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain -d mydomain.be ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] 89da825a23a1afaa5058ef04fcf694be97fce658 0 29 1023 698 2019-11-23T18:22:09Z Cvm 41 wikitext text/x-wiki To register an account you can follow these easy steps: [[File:UCC Request New Account.png|thumb|right]] * Go to https://ucc.ulyssis.org/accounts and login using your Central KU Leuven Account * Select the kind of account you wish to register ** Most people will want to register a '''regular account''' for '''personal use''' ** If you are a recognised '''faculty''' union, assembly or representational organisation you are entitled to this free account. We verify this using the list of '''recognised "kringen"''' of LOKO, http://loko.be/verenigingen/ . Recognised organisations are not entitled to a free account. ** If you are a '''recognised organisation''' from LOKO, Studentenraad KU Leuven or the KU Leuven itself you are entitled to an organisation account, this account has a reduced price. * After picking your account type you have to choose which options you want, as well as a username and a language. * Aaccept the ULYSSIS terms of use and confirm your order. * An email will be sent to your KU Leuven email address to confirm your order alongside a request for payment. * As soon as we have received and processed your payment, your account will be activated and you will receive instructions to set a password. [[Category:Account]] a1fc5f5646f780f163ad4a28d69c8893fda41ccb 1024 1023 2019-11-23T18:22:36Z Cvm 41 wikitext text/x-wiki To register an account you can follow these easy steps: [[File:UCC Request New Account.png|thumb|right]] * Go to https://ucc.ulyssis.org/accounts and login using your Central KU Leuven Account * Select the kind of account you wish to register ** Most people will want to register a '''regular account''' for '''personal use''' ** If you are a recognised '''faculty''' union, assembly or representational organisation you are entitled to this free account. We verify this using the list of '''recognised "kringen"''' from LOKO, http://loko.be/verenigingen/ . Recognised organisations are not entitled to a free account. ** If you are a '''recognised organisation''' by LOKO, Studentenraad KU Leuven or the KU Leuven itself you are entitled to an organisation account, this account has a reduced price. * After picking your account type you have to choose which options you want, as well as a username and a language. * Aaccept the ULYSSIS terms of use and confirm your order. * An email will be sent to your KU Leuven email address to confirm your order alongside a request for payment. * As soon as we have received and processed your payment, your account will be activated and you will receive instructions to set a password. [[Category:Account]] f96e599939206c7994aebc6ea785489decba46f1 1025 1024 2019-11-23T18:24:32Z Cvm 41 wikitext text/x-wiki To register an account, follow these steps: [[File:UCC Request New Account.png|thumb|right]] * Go to https://ucc.ulyssis.org/accounts and login using your Central KU Leuven Account * Select the kind of account you wish to register ** Most people will want to register a '''regular account''' for '''personal use''' ** If you are a recognised '''faculty''' union, assembly or representational organisation you are entitled to this free account. We verify this using the list of '''recognised "kringen"''' from LOKO, http://loko.be/verenigingen/ . Recognised organisations are not entitled to a free account. ** If you are a '''recognised organisation''' by LOKO, Studentenraad KU Leuven or the KU Leuven itself you are entitled to an organisation account, this account has a reduced price. * After picking your account type you have to choose which options you want, as well as a username and a language. * Aaccept the ULYSSIS terms of use and confirm your order. * An email will be sent to your KU Leuven email address to confirm your order alongside a request for payment. * As soon as we have received and processed your payment, your account will be activated and you will receive instructions to set a password. [[Category:Account]] f0fdcf7d57791a9458d62760a85332825706bed9 1026 1025 2019-11-23T18:26:05Z Cvm 41 wikitext text/x-wiki To register an account, follow these steps: [[File:UCC Request New Account.png|thumb|right]] * Go to https://ucc.ulyssis.org/accounts and login using your Central KU Leuven Account * Select the kind of account you wish to register ** Most people will want to register a '''regular account''' for '''personal use''' ** If you are a recognised '''faculty''' union, assembly or representational organisation you are entitled to this free account. We verify this using the list of '''recognised "kringen"''' from LOKO, http://loko.be/verenigingen/ . Recognised organisations are not entitled to a free account. ** If you are a '''recognised organisation''' by LOKO, Studentenraad KU Leuven or the KU Leuven itself you are entitled to an organisation account, wich has a reduced price. * After picking your account type you have to choose which options you want, as well as a username and a language. * Aaccept the ULYSSIS terms of use and confirm your order. * An email will be sent to your KU Leuven email address to confirm your order alongside a request for payment. * As soon as we have received and processed your payment, your account will be activated and you will receive instructions to set a password. [[Category:Account]] 762a72170f37f1bf77b2db7b483abe60b8d5a10d 1027 1026 2019-11-23T18:27:27Z Cvm 41 wikitext text/x-wiki To register an account, follow these steps: [[File:UCC Request New Account.png|thumb|right]] * Go to https://ucc.ulyssis.org/accounts and login using your Central KU Leuven Account * Select the kind of account you wish to register ** Most people will want to register a '''regular account''' for '''personal use''' ** If you are a recognised '''faculty''' union, assembly or representational organisation you are entitled to this free account. We verify this using the list of '''recognised "kringen"''' from LOKO, http://loko.be/verenigingen/ . Recognised organisations are not entitled to a free account. ** If you are a '''recognised organisation''' by LOKO, Studentenraad KU Leuven or the KU Leuven itself you are entitled to an organisation account, wich has a reduced price. * After picking your account type you have to choose which options you want, as well as a username and a language. * Accept the ULYSSIS terms of use and confirm your order. * An email will be sent to your KU Leuven email address to confirm your order alongside a request for payment. * As soon as we have received and processed your payment, your account will be activated and you will receive instructions to set a password. [[Category:Account]] 2a080b8ae031fb0a2736fd545f7a3ef2bf8a8033 1028 1027 2019-11-23T18:28:14Z Cvm 41 wikitext text/x-wiki To register an account, follow these steps: [[File:UCC Request New Account.png|thumb|right]] * Go to https://ucc.ulyssis.org/accounts and login using your Central KU Leuven Account * Select the kind of account you wish to register ** Most people will want to register a '''regular account''' for '''personal use''' ** If you are a recognised '''faculty''' union, assembly or representational organisation you are entitled to this free account. We verify this using the list of '''recognised faculty unions''' from LOKO, http://loko.be/verenigingen/ . Recognised organisations are not entitled to a free account. ** If you are a '''recognised organisation''' by LOKO, Studentenraad KU Leuven or the KU Leuven itself you are entitled to an organisation account, wich has a reduced price. * After picking your account type you have to choose which options you want, as well as a username and a language. * Accept the ULYSSIS terms of use and confirm your order. * An email will be sent to your KU Leuven email address to confirm your order alongside a request for payment. * As soon as we have received and processed your payment, your account will be activated and you will receive instructions to set a password. [[Category:Account]] ea0303c9e7876959e46d8165142b5ec6f671f226 0 29 1029 1028 2019-11-23T18:28:57Z Cvm 41 wikitext text/x-wiki To register an account, follow these steps: [[File:UCC Request New Account.png|thumb|right]] * Go to https://ucc.ulyssis.org/accounts and login using your Central KU Leuven Account * Select the kind of account you wish to register ** Most people will want to register a '''regular account''' for '''personal use''' ** If you are a recognised '''faculty union''' (kring), assembly or representational organisation you are entitled to this free account. We verify this using the list of '''recognised faculty unions''' (kringen) from LOKO, http://loko.be/verenigingen/ . Recognised organisations are not entitled to a free account. ** If you are a '''recognised organisation''' by LOKO, Studentenraad KU Leuven or the KU Leuven itself you are entitled to an organisation account, wich has a reduced price. * After picking your account type you have to choose which options you want, as well as a username and a language. * Accept the ULYSSIS terms of use and confirm your order. * An email will be sent to your KU Leuven email address to confirm your order alongside a request for payment. * As soon as we have received and processed your payment, your account will be activated and you will receive instructions to set a password. [[Category:Account]] 4a8ae449003421798d0c2dccdba21250fa801cb9 1030 1029 2019-11-23T18:30:19Z Cvm 41 wikitext text/x-wiki To register an account, follow these steps: [[File:UCC Request New Account.png|thumb|right]] * Go to https://ucc.ulyssis.org/accounts and log in using your Central KU Leuven Account * Select the kind of account you wish to register ** Most people will want to register a '''regular account''' for '''personal use''' ** If you are a recognised '''faculty union''' (kring), assembly or representational organisation you are entitled to this free account. We verify this using the list of '''recognised faculty unions''' (kringen) from LOKO, http://loko.be/verenigingen/ . Recognised organisations are not entitled to a free account. ** If you are a '''recognised organisation''' by LOKO, Studentenraad KU Leuven or the KU Leuven itself you are entitled to an organisation account, wich has a reduced price. * After picking your account type you have to choose which options you want, as well as a username and a language. * Accept the ULYSSIS terms of use and confirm your order. * An email will be sent to your KU Leuven email address to confirm your order alongside a request for payment. * As soon as we have received and processed your payment, your account will be activated and you will receive instructions to set a password. [[Category:Account]] 219c33fdc4793dc456b9624f409ef1fc4661b0f9 1031 1030 2019-11-23T18:30:40Z Cvm 41 wikitext text/x-wiki To register an account, follow these steps: [[File:UCC Request New Account.png|thumb|right]] * Go to https://ucc.ulyssis.org/accounts and log in using your Central KU Leuven Account * Select the kind of account you wish to register. ** Most people will want to register a '''regular account''' for '''personal use'''. ** If you are a recognised '''faculty union''' (kring), assembly or representational organisation you are entitled to this free account. We verify this using the list of '''recognised faculty unions''' (kringen) from LOKO, http://loko.be/verenigingen/ . Recognised organisations are not entitled to a free account. ** If you are a '''recognised organisation''' by LOKO, Studentenraad KU Leuven or the KU Leuven itself you are entitled to an organisation account, wich has a reduced price. * After picking your account type you have to choose which options you want, as well as a username and a language. * Accept the ULYSSIS terms of use and confirm your order. * An email will be sent to your KU Leuven email address to confirm your order alongside a request for payment. * As soon as we have received and processed your payment, your account will be activated and you will receive instructions to set a password. [[Category:Account]] c7854d56e5db510e6448593592f2d9171a7d2711 1032 1031 2019-11-23T18:30:59Z Cvm 41 wikitext text/x-wiki To register an account, follow these steps: [[File:UCC Request New Account.png|thumb|right]] * Go to https://ucc.ulyssis.org/accounts and log in using your Central KU Leuven Account. * Select the kind of account you wish to register. ** Most people will want to register a '''regular account''' for '''personal use'''. ** If you are a recognised '''faculty union''' (kring), assembly or representational organisation you are entitled to this free account. We verify this using the list of '''recognised faculty unions''' (kringen) from LOKO, http://loko.be/verenigingen/ . Recognised organisations are not entitled to a free account. ** If you are a '''recognised organisation''' by LOKO, Studentenraad KU Leuven or the KU Leuven itself you are entitled to an organisation account, wich has a reduced price. * After picking your account type you have to choose which options you want, as well as a username and a language. * Accept the ULYSSIS terms of use and confirm your order. * An email will be sent to your KU Leuven email address to confirm your order alongside a request for payment. * As soon as we have received and processed your payment, your account will be activated and you will receive instructions to set a password. [[Category:Account]] 8814b21199bef82030868c60c10800ee399880b4 1033 1032 2019-11-23T18:31:09Z Cvm 41 wikitext text/x-wiki To register an account, follow these steps: [[File:UCC Request New Account.png|thumb|right]] * Go to https://ucc.ulyssis.org/accounts and log in using your Central KU Leuven Account. * Select the kind of account you wish to register: ** Most people will want to register a '''regular account''' for '''personal use'''. ** If you are a recognised '''faculty union''' (kring), assembly or representational organisation you are entitled to this free account. We verify this using the list of '''recognised faculty unions''' (kringen) from LOKO, http://loko.be/verenigingen/ . Recognised organisations are not entitled to a free account. ** If you are a '''recognised organisation''' by LOKO, Studentenraad KU Leuven or the KU Leuven itself you are entitled to an organisation account, wich has a reduced price. * After picking your account type you have to choose which options you want, as well as a username and a language. * Accept the ULYSSIS terms of use and confirm your order. * An email will be sent to your KU Leuven email address to confirm your order alongside a request for payment. * As soon as we have received and processed your payment, your account will be activated and you will receive instructions to set a password. [[Category:Account]] 69f08cf91bcddbcd3025daa5dc387183d4b63341 0 30 1034 699 2019-11-23T18:33:08Z Cvm 41 wikitext text/x-wiki Please keep in mind you have to be the owner of the account to be able to renew it. If you are not the owner you first have to look at [[Transferring your account]]. 3 weeks before your account expires you will start receiving emails reminding you to renew your account. These will continue until your account expires. To renew your account you visit https://ucc.ulyssis.org/accounts and, while making sure you are '''not''' logged into a ULYSSIS Account, login using the Central KU Leuven Login and select your account (the renewal option will only be available if the account is in the renewal period of 40 days or has expired already). * Select your account option, you are free to upgrade your personal account to a higher tier now * Verify your personal information (in case of errors please contact ULYSSIS) * Accept the terms of use * Confirm your order * An email will be sent to your KU Leuven emailaddress to confirm your order and with a request for payment. * As soon as we have received and processed your payment your account will get renewed, you will receive a notification. * If you are running late with your payment and you wish to prevent your account from getting expired you can contact ULYSSIS with a screenshot or scan that confirms the payment, we will then temporarily renew your account and verify that the money arrives within the near future. [[Category:Account]] c4e7d36c4ae6784ea1e07f9ec01e8a283d949c90 1035 1034 2019-11-23T18:33:28Z Cvm 41 wikitext text/x-wiki Please keep in mind you have to be the owner of the account to be able to renew it. If you are not the owner you first have to look at [[Transferring your account]]. 3 weeks before your account expires you will start receiving emails reminding you to renew your account. These will continue until your account expires. To renew your account you visit https://ucc.ulyssis.org/accounts and, while making sure you are '''not''' logged into a ULYSSIS Account, login using the Central KU Leuven Login and select your account (the renewal option will only be available if the account is in the renewal period of 40 days or has expired already). * Select your account option, you are free to upgrade your personal account to a higher tier now. * Verify your personal information (in case of errors please contact ULYSSIS). * Accept the terms of use. * Confirm your order. * An email will be sent to your KU Leuven emailaddress to confirm your order and with a request for payment. * As soon as we have received and processed your payment your account will get renewed, you will receive a notification. * If you are running late with your payment and you wish to prevent your account from getting expired you can contact ULYSSIS with a screenshot or scan that confirms the payment, we will then temporarily renew your account and verify that the money arrives within the near future. [[Category:Account]] a7b7a8ade686a0c15564f303769042d97428ea68 1036 1035 2019-11-23T18:34:22Z Cvm 41 wikitext text/x-wiki Please keep in mind you have to be the owner of the account to be able to renew it. If you are not the owner you first have to look at [[Transferring your account]]. 3 weeks before your account expires you will start receiving emails reminding you to renew your account. These will continue until your account expires. To renew your account you visit https://ucc.ulyssis.org/accounts and, while making sure you are '''not''' logged into a ULYSSIS Account, login using the Central KU Leuven Login and select your account (the renewal option will only be available if the account is in the renewal period of 40 days or has expired already). * Select your account option, you are free to upgrade your personal account to a higher tier now. * Verify your personal information (in case of errors please contact ULYSSIS). * Accept the terms of use. * Confirm your order. * An email will be sent to your KU Leuven email address to confirm your order alongside a request for payment. * As soon as we have received and processed your payment your account will be renewed and you will receive a notification. * If you are running late with your payment and you wish to prevent your account from getting expired you can contact ULYSSIS with a screenshot or scan that confirms the payment, we will then temporarily renew your account and verify that the money arrives within the near future. [[Category:Account]] 7d8ffce17b08d1172e3471ba27efd15a54b18326 1039 1036 2019-11-23T18:40:28Z Cvm 41 wikitext text/x-wiki Please keep in mind you have to be the owner of the account to be able to renew it. If you are not the owner you first have to look at [[Transferring your account]]. 3 weeks before your account expires you will start receiving emails reminding you to renew your account. These will continue until your account expires. To renew your account you visit https://ucc.ulyssis.org/accounts and, while making sure you are '''not''' logged into a ULYSSIS Account, log in using the Central KU Leuven Login and select your account (the renewal option will only be available if the account is in the renewal period of 40 days or has expired already). * Select your account option, you are free to upgrade your personal account to a higher tier now. * Verify your personal information (in case of errors please contact ULYSSIS). * Accept the terms of use. * Confirm your order. * An email will be sent to your KU Leuven email address to confirm your order alongside a request for payment. * As soon as we have received and processed your payment your account will be renewed and you will receive a notification. * If you are running late with your payment and you wish to prevent your account from getting expired you can contact ULYSSIS with a screenshot or scan that confirms the payment, we will then temporarily renew your account and verify that the money arrives within the near future. [[Category:Account]] c5b2d5ec3ec7b3d6aec69863aa714f3ddba4cf1b 0 15 1037 701 2019-11-23T18:36:59Z Cvm 41 wikitext text/x-wiki You can transfer the account of your (faculty) organization to a new webmaster. The new webmaster must have a valid Central KU Leuven Login. Otherwise the new webmaster can not accept the account transfer. The instructions below must be executed by the current account owner. * Login into [https://ucc.ulyssis.org/ UCC]. * Choose 'Transfer account' in the menu on the right. * Enter the details of the new account owner. (Make sure you type the KULeuven email address correct!) The new owner will get an email to confirm the transfer. [[Category:Account]] 559fb6941ccc1f2c934bbfd12848501cb747f318 1038 1037 2019-11-23T18:37:12Z Cvm 41 wikitext text/x-wiki You can transfer the account of your (faculty) organization to a new webmaster. The new webmaster must have a valid Central KU Leuven Login. Otherwise the new webmaster can not accept the account transfer. The instructions below must be executed by the current account owner. * Log in to [https://ucc.ulyssis.org/ UCC]. * Choose 'Transfer account' in the menu on the right. * Enter the details of the new account owner. (Make sure you type the KULeuven email address correct!) The new owner will get an email to confirm the transfer. [[Category:Account]] 21079b2cc658c6755332502b7408e46432b69776 0 45 1040 702 2019-11-23T18:41:35Z Cvm 41 wikitext text/x-wiki You can always reset your password. In order to reset your password, visit [https://ucc.ulyssis.org/ucc/passwd/reset UCC]. Please keep in mind you need to be logged out of UCC to be able to reset your password. * Fill in your username and click on 'reset password'. * You will then have to log in using your Central KU Leuven Login. * Choose another password. * Click on reset password. * You will immediately be logged out of your KU Leuven account again, but your password will be changed. * Try to log in at UCC with your new password. Be wise and pick a [https://xkcd.com/936/ strong and easy to remember password]. [[Category:Account]] 4a3904279b1c346235b4bea8d94b346682336154 1041 1040 2019-11-23T18:42:46Z Cvm 41 wikitext text/x-wiki You can always reset your password. In order to reset your password, visit [https://ucc.ulyssis.org/ucc/passwd/reset UCC]. Please keep in mind you need to be logged out of UCC to be able to reset your password. * Fill in your username and click on 'reset password'. * You will then have to log in using your Central KU Leuven Login. * Choose another password. * Click on reset password. * You will immediately be logged out of your KU Leuven account again, but your password will be changed. * Try to log in with your new password. Be wise and pick a [https://xkcd.com/936/ strong and easy to remember password]. [[Category:Account]] 393c5847e7af37387fca7aa5cc76e2b92823f7ec 1042 1041 2019-11-23T18:42:59Z Cvm 41 wikitext text/x-wiki You can always reset your password. In order to reset your password, visit [https://ucc.ulyssis.org/ucc/passwd/reset UCC]. Please keep in mind you need to be logged out of UCC to be able to reset your password. * Fill in your username and click 'reset password'. * You will then have to log in using your Central KU Leuven Login. * Choose another password. * Click on reset password. * You will immediately be logged out of your KU Leuven account again, but your password will be changed. * Try to log in with your new password. Be wise and pick a [https://xkcd.com/936/ strong and easy to remember password]. [[Category:Account]] 1865beb56919572860a9719362c8026ed2771f65 1043 1042 2019-11-23T18:43:19Z Cvm 41 wikitext text/x-wiki You can always reset your password. In order to reset your password, visit [https://ucc.ulyssis.org/ucc/passwd/reset UCC]. Please keep in mind you need to be logged out of UCC to be able to reset your password. * Fill in your username and click 'reset password'. * You will then have to log in using your Central KU Leuven Login. * Choose a different password. * Click on reset password. * You will immediately be logged out of your KU Leuven account again, but your password will be changed. * Try to log in with your new password. Be wise and pick a [https://xkcd.com/936/ strong and easy to remember password]. [[Category:Account]] 6e1e6fbcd0ad2953f89d9851eef7a9e22698d7f9 1044 1043 2019-11-23T18:45:51Z Cvm 41 wikitext text/x-wiki You can always reset your password. In order to reset your password, visit [https://ucc.ulyssis.org/ucc/passwd/reset UCC]. Please keep in mind you need to be logged out of UCC to be able to reset your password. * Fill in your username and click 'reset password'. * You will then have to log in using your Central KU Leuven Login. * Choose a different password. * Click reset password. * You will immediately be logged out of your KU Leuven account again, but your password will be changed. * Try to log in with your new password. Be wise and pick a [https://xkcd.com/936/ strong and easy to remember password]. [[Category:Account]] 84b32f0693baf01ac975429b4a4d2a2bffb1a2f9 1045 1044 2019-11-23T18:46:17Z Cvm 41 wikitext text/x-wiki You can always reset your password. In order to reset your password, visit [https://ucc.ulyssis.org/ucc/passwd/reset UCC]. Please keep in mind you need to be logged out of UCC to be able to reset your password. * Fill in your username and click 'reset password'. * You will then have to log in using your Central KU Leuven Login. * Choose a different password. * Click reset password. * You will immediately be logged out of your KU Leuven account, but your password will be changed. * Try to log in with your new password. Be wise and pick a [https://xkcd.com/936/ strong and easy to remember password]. [[Category:Account]] 454c8f7e9e2a2255ae69f42f1f2fe4dace416082 1046 1045 2019-11-23T18:46:40Z Cvm 41 wikitext text/x-wiki You can always reset your password. In order to reset your password, visit [https://ucc.ulyssis.org/ucc/passwd/reset UCC]. Please keep in mind you need to be logged out of UCC to be able to reset your password. * Fill in your username and click 'reset password'. * You will then have to log in using your Central KU Leuven Login. * Choose a different password. * Click reset password. * You will immediately be logged out ad your password should be changed. * Try to log in with your new password. Be wise and pick a [https://xkcd.com/936/ strong and easy to remember password]. [[Category:Account]] 36e4a165c9f324a74e4a9196d5078e6101ef0079 1047 1046 2019-11-23T18:46:51Z Cvm 41 wikitext text/x-wiki You can always reset your password. In order to reset your password, visit [https://ucc.ulyssis.org/ucc/passwd/reset UCC]. Please keep in mind you need to be logged out of UCC to be able to reset your password. * Fill in your username and click 'reset password'. * You will then have to log in using your Central KU Leuven Login. * Choose a different password. * Click reset password. * You will immediately be logged out and your password should be changed. * Try to log in with your new password. Be wise and pick a [https://xkcd.com/936/ strong and easy to remember password]. [[Category:Account]] f05de002f2e8644a9b54f5d0c6808653610a4fa5 0 10 1050 1022 2020-01-06T17:04:23Z Lars 26 wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, we download the <code>acme.sh</code> script and make it executable: wget https://raw.githubusercontent.com/Neilpang/acme.sh/master/acme.sh chmod +x acme.sh Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be If we provide an email address, for example "email@example.com", Let's Encrypt will remind us to renew our certificates when necessary. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain -d mydomain.be After renewing certificates, you have to email us to install your renewed certificate. ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] dceb3e33f0398f0c14ac4efc78e05aacd1b78d39 1051 1050 2020-02-13T11:01:56Z Bert 8 wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be and *.student.kuleuven.ac.be domain. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, we download the <code>acme.sh</code> script and make it executable: wget https://raw.githubusercontent.com/Neilpang/acme.sh/master/acme.sh chmod +x acme.sh Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be If we provide an email address, for example "email@example.com", Let's Encrypt will remind us to renew our certificates when necessary. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain -d mydomain.be After renewing certificates, you have to email us to install your renewed certificate. ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] 260f8240d83cbc08ac04bb6349abfadeae972a39 1052 1051 2020-02-13T11:02:26Z Bert 8 wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be and *.student.kuleuven.ac.be domain. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, we download the <code>acme.sh</code> script and make it executable: wget https://raw.githubusercontent.com/Neilpang/acme.sh/master/acme.sh chmod +x acme.sh Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be If we provide an email address, for example "email@example.com", Let's Encrypt will remind us to renew our certificates when necessary. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain -d mydomain.be After renewing certificates, you have to email us to install your renewed certificate. ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] 399e627a3ccdc00dde4168b338dac1d4412de8cd 1053 1052 2020-02-20T11:27:52Z Yoa 30 /* Renewing the certificates */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be and *.student.kuleuven.ac.be domain. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, we download the <code>acme.sh</code> script and make it executable: wget https://raw.githubusercontent.com/Neilpang/acme.sh/master/acme.sh chmod +x acme.sh Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be If we provide an email address, for example "email@example.com", Let's Encrypt will remind us to renew our certificates when necessary. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain -d mydomain.be '''After renewing certificates, you have to email us to install your renewed certificate.''' ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] 731fff9ca2bf637771adf9b96bacf895d1170721 1055 1053 2020-03-27T16:50:29Z Bert 8 wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be and *.student.kuleuven.ac.be domain. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, we download the <code>acme.sh</code> script and make it executable: wget https://raw.githubusercontent.com/Neilpang/acme.sh/master/acme.sh chmod +x acme.sh Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be If we provide an email address, for example "email@example.com", Let's Encrypt will remind us to renew our certificates when necessary. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain -d mydomain.be '''After renewing certificates, you have to email us to install your renewed certificate.''' ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] 22359ead147b76359f5939dba80a2756ca8da84b 1056 1055 2020-04-14T19:53:31Z Bert 8 Bert moved page [[Getting SSL]] to [[Getting SSL/TLS]] wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be and *.student.kuleuven.ac.be domain. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, we download the <code>acme.sh</code> script and make it executable: wget https://raw.githubusercontent.com/Neilpang/acme.sh/master/acme.sh chmod +x acme.sh Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be If we provide an email address, for example "email@example.com", Let's Encrypt will remind us to renew our certificates when necessary. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain -d mydomain.be '''After renewing certificates, you have to email us to install your renewed certificate.''' ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] 22359ead147b76359f5939dba80a2756ca8da84b 1074 1056 2020-06-02T10:32:05Z Principis 32 wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be and *.student.kuleuven.ac.be domain. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, we download the <code>acme.sh</code> script and make it executable: wget https://raw.githubusercontent.com/Neilpang/acme.sh/master/acme.sh chmod +x acme.sh Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be If we provide an email address, for example "email@example.com", Let's Encrypt will remind us to renew our certificates when necessary. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew -d mydomain.be The renewed certificates will automatically be copied to the path specified in the "--issue" command. '''After renewing certificates, you have to email us to install your renewed certificate.''' ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] cdcf7a726a987ad6c640526a76e73185828cf2c9 1075 1074 2020-06-02T10:55:19Z Principis 32 /* Generating the certificates */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be and *.student.kuleuven.ac.be domain. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, download the <code>acme.sh</code> script as explained in the documentation: https://github.com/acmesh-official/acme.sh#1-how-to-install Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be If we provide an email address, for example "email@example.com", Let's Encrypt will remind us to renew our certificates when necessary. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew -d mydomain.be The renewed certificates will automatically be copied to the path specified in the "--issue" command. '''After renewing certificates, you have to email us to install your renewed certificate.''' ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] 7a896d745812459b45979bd95320e8869f50bd8d 1076 1075 2020-06-02T10:55:36Z Principis 32 /* Renewing the certificates */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities to use free SSL for its services, organisations and employees. We have permission to request SSL for Student Unions recognized by LOKO or another official body. Organisations (Vrije Verenigingen) are required to be recognized by LOKO or another official body and need to supply a reasoning why they need SSL. Individual users can request SSL but ICTS will only grant permission with elaborate reasoning. Before sending us a request the following steps have to be done: *Setup the site that needs SSL *Change the domain's organisation-attribute to ''KU Leuven'' or ''Katholieke Universiteit Leuven'' *Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org Then you can send an email to ulyssis@ulyssis.org containing your name, the name of the organisation, what you will use SSL for and the domain and if needed a list of subdomains. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be and *.student.kuleuven.ac.be domain. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, download the <code>acme.sh</code> script as explained in the documentation: https://github.com/acmesh-official/acme.sh#1-how-to-install Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be If we provide an email address, for example "email@example.com", Let's Encrypt will remind us to renew our certificates when necessary. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew -d mydomain.be The renewed certificates will automatically be copied to the path specified in the <code>--issue</code> command. '''After renewing certificates, you have to email us to install your renewed certificate.''' ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] b65b9d5deab1d5fdacb2540482c27e8c4cd5b21f 1077 1076 2020-07-07T22:33:58Z Bert 8 /* Requesting SSL from the KU Leuven */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and employees. We have permission to request free SSL/TLS certificates for Student Unions (Kringen) recognized by LOKO or faculty representative body (Facultaire Overlegorganen) recognized by Stura body as well as Organisations (Vrije Verenigingen) recognized by LOKO or another official body. Before sending us a request the following steps have to be done: * Setup the site that needs SSL * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. Then the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible that for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be and *.student.kuleuven.ac.be domain. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, download the <code>acme.sh</code> script as explained in the documentation: https://github.com/acmesh-official/acme.sh#1-how-to-install Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be If we provide an email address, for example "email@example.com", Let's Encrypt will remind us to renew our certificates when necessary. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew -d mydomain.be The renewed certificates will automatically be copied to the path specified in the <code>--issue</code> command. '''After renewing certificates, you have to email us to install your renewed certificate.''' ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] 35779968cd069f19351de8bf36f28b40ff546fcb 1078 1077 2020-07-07T22:34:46Z Bert 8 /* Requesting SSL from the KU Leuven */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for Student Unions (Kringen) recognized by LOKO or faculty representative body (Facultaire Overlegorganen) recognized by Stura body as well as Organisations (Vrije Verenigingen) recognized by LOKO or another official body. Before sending us a request the following steps have to be done: * Setup the site that needs SSL * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. Then the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible that for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be and *.student.kuleuven.ac.be domain. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, download the <code>acme.sh</code> script as explained in the documentation: https://github.com/acmesh-official/acme.sh#1-how-to-install Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be If we provide an email address, for example "email@example.com", Let's Encrypt will remind us to renew our certificates when necessary. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew -d mydomain.be The renewed certificates will automatically be copied to the path specified in the <code>--issue</code> command. '''After renewing certificates, you have to email us to install your renewed certificate.''' ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] 5609fa8e8e5d1403d05999d7a5fdefe4c98f0f82 1079 1078 2020-07-07T22:36:30Z Bert 8 /* Requesting SSL from the KU Leuven */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty representative body (facultaire overlegorganen) recognized by Stura body as well as Organisations (Vrije Verenigingen) recognized by LOKO or another official body. Before sending us a request the following steps have to be done: * Setup the site that needs SSL * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. Then the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible that for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be and *.student.kuleuven.ac.be domain. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, download the <code>acme.sh</code> script as explained in the documentation: https://github.com/acmesh-official/acme.sh#1-how-to-install Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be If we provide an email address, for example "email@example.com", Let's Encrypt will remind us to renew our certificates when necessary. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew -d mydomain.be The renewed certificates will automatically be copied to the path specified in the <code>--issue</code> command. '''After renewing certificates, you have to email us to install your renewed certificate.''' ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] e7f57e8b78640934479734df99f5da24858d1934 1080 1079 2020-07-07T22:37:04Z Bert 8 /* Requesting SSL from the KU Leuven */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty representative body (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request the following steps have to be done: * Setup the site that needs SSL * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. Then the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible that for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be and *.student.kuleuven.ac.be domain. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, download the <code>acme.sh</code> script as explained in the documentation: https://github.com/acmesh-official/acme.sh#1-how-to-install Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be If we provide an email address, for example "email@example.com", Let's Encrypt will remind us to renew our certificates when necessary. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew -d mydomain.be The renewed certificates will automatically be copied to the path specified in the <code>--issue</code> command. '''After renewing certificates, you have to email us to install your renewed certificate.''' ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] 71f63f0130fea79d64c9de8f0a6d21b8a3c3b8b0 1081 1080 2020-07-07T22:37:25Z Bert 8 /* Requesting SSL from the KU Leuven */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty representative body (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request the following steps have to be taken: * Setup the site that needs SSL * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. Then the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible that for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be and *.student.kuleuven.ac.be domain. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, download the <code>acme.sh</code> script as explained in the documentation: https://github.com/acmesh-official/acme.sh#1-how-to-install Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be If we provide an email address, for example "email@example.com", Let's Encrypt will remind us to renew our certificates when necessary. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew -d mydomain.be The renewed certificates will automatically be copied to the path specified in the <code>--issue</code> command. '''After renewing certificates, you have to email us to install your renewed certificate.''' ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] 5ec26e48752a10a4d791d94bd791602d15949e5a 0 104 1054 745 2020-03-16T16:56:24Z Bert 8 wikitext text/x-wiki PHP code is run with PHP-FPM as your ULYSSIS user. This means you can tighten up you website's security by denying other users the permission to read your PHP files. However, due to the way the Apache webserver works, it must be able to determine the existence of your PHP files. Non-PHP files in your www directory must remain readable by other users, because Apache reads these as it's own user. === Recommended permissions === * Homedirectory: See [[#Homedirectory permissions | homedirectory]] * www directory (and other directories from where websites are served), including subdirectories: <code>0705/drwx---r-x</code> * Static website files (css, images, html, ...): <code>0604/-rw----r--</code> * Configuration files containing secrets/passwords: <code>0600/-rw-------</code> * Other directories and files that are not part of a website: <code>0600/-rw-------</code> or <code>0700/-rwx------</code> === Securing database login info === Suppose you have a file called <code>config.php</code>, containing login information for your database. To secure this information, you can make it readable and writeable by only you, and nobody else using <code>chmod 600 config.php</code>. In FileZilla, you can do this by right-clicking on the config file, clicking on "File permissions...", and changing the permissions according to the following screenshots: [[File:config-php_dropdown.png]] [[File:config-php_attrs.png]] === Securing uploads directory === Also, if there are directories that you made writeable by others, e.g. an uploads folder, this is no longer necessary. If this directory is called <code>uploads</code>, you can remove write rights for others with <code>chmod go-w uploads</code>. In FileZilla, you can do this by right-clicking on the config file, clicking on "File permissions...", and changing the permissions according to the following screenshots: [[File:uploads_dropdown.png]] [[File:uploads_attrs.png]] === Homedirectory permissions === In order to prevent other users entirely from accessing files in your homedirectory, the permissions on your homedirectory should only allow yourself and the www-data user access. This is by default configured properly for you from the 29th of July, 2018 onward. Note that you should still follow the guidelines as detailed above. If you have changed your permissions on your homedirectory and want to restore the defaults, you can execute <code>nfs4_setfacl -S /home/user/acl ~</code>. The file <code>/home/user/acl</code> contains the default permissions. [[Category:Files]] [[Category:Security & anti-spam]] 68532332b4044eddacb6cfc5d38717aaf5818ed6 0 142 1057 2020-04-14T19:53:31Z Bert 8 Bert moved page [[Getting SSL]] to [[Getting SSL/TLS]] wikitext text/x-wiki #REDIRECT [[Getting SSL/TLS]] f90457165c65892e7d656a7aac4cb4c0f1afd0b9 0 3 1058 983 2020-04-14T19:54:13Z Bert 8 /* Webserver */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] * [[Secure file permissions]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Sending email from websites]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL/TLS|Getting SSL/TLS (HTTPS security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] * [[Claiming a port]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up WordPress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] * [[Using PHPPgAdmin]] * [[Using Adminer]] * [[Making Backups]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 1b793b61403d1cd7e11e5b15ba68e46449455813 1059 1058 2020-04-14T20:05:41Z Bert 8 /* Webserver */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] * [[Secure file permissions]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Sending email from websites]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL/TLS|Getting SSL/TLS (HTTPS security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] * [[Claiming a port]] * [[ULYSSIS security measures]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up WordPress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] * [[Using PHPPgAdmin]] * [[Using Adminer]] * [[Making Backups]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 0ad390bba7f0214c1730117baef945e32d479884 1060 1059 2020-04-14T20:05:48Z Bert 8 /* Mail */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] * [[Secure file permissions]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Sending email from websites]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL/TLS|Getting SSL/TLS (HTTPS security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] * [[Claiming a port]] * [[ULYSSIS security measures]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up WordPress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] * [[Using PHPPgAdmin]] * [[Using Adminer]] * [[Making Backups]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 72349a3cf2f55c6301d6da75f6c02630f5db11eb 1061 1060 2020-04-14T20:05:58Z Bert 8 /* Security & anti-spam */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] * [[Secure file permissions]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Sending email from websites]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL/TLS|Getting SSL/TLS (HTTPS security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] * [[Claiming a port]] * [[ULYSSIS security measures]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up WordPress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] * [[Using PHPPgAdmin]] * [[Using Adminer]] * [[Making Backups]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 26db17059f91f61dea29b88cd373222905effe09 1062 1061 2020-04-15T14:40:36Z Bert 8 /* Mail */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] * [[Secure file permissions]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Sending email from websites]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL/TLS|Getting SSL/TLS (HTTPS security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] * [[Claiming a port]] * [[ULYSSIS security measures]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] * [[Spam]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up WordPress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] * [[Using PHPPgAdmin]] * [[Using Adminer]] * [[Making Backups]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 99600e79152778330bd074dc2fe8384faca0b3a4 0 143 1063 2020-04-16T03:17:18Z Bert 8 Created page with "At ULYSSIS we try to prevent as much spam as possible from ending up in our users mailboxes or being passed through forwarders. However, as we offer email to many organisation..." wikitext text/x-wiki At ULYSSIS we try to prevent as much spam as possible from ending up in our users mailboxes or being passed through forwarders. However, as we offer email to many organisations that post their contact information online in several languages, we attract large amount of spam, of which some may be in other languages than English. Because of this, regular spam filters may miss out on some of the spam. To further prevent spam from being delivered, we've not only enabled extra features to look for bulk emails, dubious cryptocurrency hashes and unexpected languages, but we've also written many custom spam tests based on common patterns within spam our users receive. We depend on gathering samples of spam and comparing them to regular email to decide what kind of custom test may be useful and what score we should give it. We therefore encourage users and spammers to email us their spam on spam-analysis@ulyssis.org. Keep in mind that we can achieve much better results if you supply us with all the headers when you forward your spam. You can refer to [https://www.auckland.ac.nz/en/students/safe-computing/recognising-online-threats/forward-email-headers.html|this guide] by the University of Auckland if you don't know how. 085aa67ef415fc126962f301580b9b36ad4bab28 1064 1063 2020-04-16T03:17:28Z Bert 8 wikitext text/x-wiki At ULYSSIS we try to prevent as much spam as possible from ending up in our users mailboxes or being passed through forwarders. However, as we offer email to many organisations that post their contact information online in several languages, we attract large amount of spam, of which some may be in other languages than English. Because of this, regular spam filters may miss out on some of the spam. To further prevent spam from being delivered, we've not only enabled extra features to look for bulk emails, dubious cryptocurrency hashes and unexpected languages, but we've also written many custom spam tests based on common patterns within spam our users receive. We depend on gathering samples of spam and comparing them to regular email to decide what kind of custom test may be useful and what score we should give it. We therefore encourage users and spammers to email us their spam on spam-analysis@ulyssis.org. Keep in mind that we can achieve much better results if you supply us with all the headers when you forward your spam. You can refer to [https://www.auckland.ac.nz/en/students/safe-computing/recognising-online-threats/forward-email-headers.html| this guide] by the University of Auckland if you don't know how. ee867619d88218861445bab1d510c51bda6c1626 1065 1064 2020-04-16T03:17:38Z Bert 8 wikitext text/x-wiki At ULYSSIS we try to prevent as much spam as possible from ending up in our users mailboxes or being passed through forwarders. However, as we offer email to many organisations that post their contact information online in several languages, we attract large amount of spam, of which some may be in other languages than English. Because of this, regular spam filters may miss out on some of the spam. To further prevent spam from being delivered, we've not only enabled extra features to look for bulk emails, dubious cryptocurrency hashes and unexpected languages, but we've also written many custom spam tests based on common patterns within spam our users receive. We depend on gathering samples of spam and comparing them to regular email to decide what kind of custom test may be useful and what score we should give it. We therefore encourage users and spammers to email us their spam on spam-analysis@ulyssis.org. Keep in mind that we can achieve much better results if you supply us with all the headers when you forward your spam. You can refer to [https://www.auckland.ac.nz/en/students/safe-computing/recognising-online-threats/forward-email-headers.html this guide] by the University of Auckland if you don't know how. 843880699fe34178663cbca4a6cec63964f34a5d 1066 1065 2020-04-16T03:19:39Z Bert 8 wikitext text/x-wiki At ULYSSIS we try to prevent as much spam as possible from ending up in our users mailboxes or being passed through forwarders. However, as we offer email to many organisations that post their contact information online in several languages, we attract large amount of spam, of which some may be in other languages than English. Because of this, regular spam filters may miss out on some of the spam. To further prevent spam from being delivered, we've not only enabled extra features to look for bulk emails, dubious cryptocurrency hashes and unexpected languages, but we've also written many custom spam tests based on common patterns within spam our users receive. We depend on gathering samples of spam and comparing them to regular email to decide what kind of custom test may be useful and what score we should give it. We therefore encourage users and spammers to email us their spam on [mailto:spam-analysis@ulyssis.org spam-analysis@ulyssis.org]. Keep in mind that we can achieve much better results if you supply us with all the headers when you forward your spam. You can refer to [https://www.auckland.ac.nz/en/students/safe-computing/recognising-online-threats/forward-email-headers.html this guide] by the University of Auckland if you don't know how to do this, but of course use [mailto:spam-analysis@ulyssis.org spam-analysis@ulyssis.org]. bda5f8959777a7886de33b8b9bcd5a99430841f6 1068 1066 2020-04-16T22:21:30Z Bert 8 wikitext text/x-wiki At ULYSSIS we try to prevent as much spam as possible from ending up in our users mailboxes or being passed through forwarders. However, as we offer email to many organisations that post information in several languages, we also attract a lot of non-English spam. Because of this, regular spam filters may miss out on some of the spam. To further prevent spam from being delivered, we've not only enabled extra features to look for bulk emails, dubious cryptocurrency hashes and unexpected languages, but we've also written many custom spam tests based on common patterns within spam our users receive. We depend on gathering samples of spam and comparing them to regular email to decide what kind of custom test may be useful and what score we should give it. We therefore encourage users and spammers to email us their spam on [mailto:spam-analysis@ulyssis.org spam-analysis@ulyssis.org]. Keep in mind that we can achieve much better results if you supply us with all the headers when you forward your spam. You can refer to [https://www.auckland.ac.nz/en/students/safe-computing/recognising-online-threats/forward-email-headers.html this guide] by the University of Auckland if you don't know how to do this. 3772d7d740fa931466241c39645dd95bd0e8630f 1071 1068 2020-04-20T01:12:37Z Bert 8 wikitext text/x-wiki At ULYSSIS we try to prevent as much spam as possible from ending up in our users mailboxes or being passed through forwarders. However, as we offer email to many organisations that post information in several languages, we also attract a lot of non-English spam. Because of this, regular spam filters may miss out on some of the spam. To further prevent spam from being delivered, we've not only enabled extra features to look for bulk emails, dubious cryptocurrency hashes and unexpected languages, but we've also written many custom spam tests based on common patterns within spam our users receive. We depend on gathering samples of spam and comparing them to regular email to decide what kind of custom test may be useful and what score we should give it. We therefore encourage users who receive spam in their ULYSSIS mailbox or through a forwarder hosted on our services to forward us their spam on [mailto:spam-analysis@ulyssis.org spam-analysis@ulyssis.org]. Keep in mind that we can achieve much better results if you supply us with all the headers when you forward your spam. You can refer to [https://www.auckland.ac.nz/en/students/safe-computing/recognising-online-threats/forward-email-headers.html this guide] by the University of Auckland if you don't know how to do this. Spammers are also free to send us as much email as they like on [mailto:spam-analysis@ulyssis.org spam-analysis@ulyssis.org]! 07b2c8056bb3c9fd25608a9e042deb12ee90f19d 0 96 1067 1006 2020-04-16T12:47:40Z Yoa 30 wikitext text/x-wiki ==Introduction== Content Management Systems, or CMSs, are easy tools to set up a website without requiring much programming or configuration. However, as is common in a lot of popular and wide-spread software, bugs or errors in the code occur. These errors can be exploited by hackers to gain access to websites or databases connected to those CMSs. Whenever a new update for a CMS, or other popular software (MediaWiki, PhpBB) is released, hackers will know which security flaws have been fixed, and try to hack websites using this knowledge. This is why it's critical to update a CMS, plugins/themes, or any related software as soon as the update comes out. To help you facilitate this, we have created a tool to help you keep the most popular software up-to-date. Currently this feature is only active if you have an organisation or student union (kring/facultair overlegorgaan) account. ==I received an e-mail!== If you receive an e-mail from the Version Checker, it's best you update the software mentioned in the e-mail as soon as possible. Make sure to download the latest public version, not just any newer version. It's also best to check if any other software you run is up-to-date: not all software is checked by the tool (as seen below). ==Supported Software== * Drupal, Drupal Modules, Drupal Themes * Joomla (Joomla Plugins are not supported yet) * MediaWiki (MediaWiki Extensions and Themes are not supported yet) * PhpBB, PhpBB Plugins, PhpBB Styles * WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the Version Checker does the following: * Scan relevant files, detect supported software, and store in database * Check the version and validity of outdated software * Mail accounts using outdated software ==Stored Data== The following data is stored in the database: * The location of the CMS, plugin/extension or theme * The responsible organisation or student union (kring/facultair overlegorgaan) * The detected software version * The type and name of the software * The update URL for the software * The date the entry was added ==Ignored Paths== The Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. ==Ignored Organisations/Student Unions== In addition to the ignored paths feature, the Version Checker can also ignore specific Organisations or Student Unions entirely. This feature is possible on request, but only after extensive deliberation with ULYSSIS. Enabling this feature also carries possible consequences: no more mails about outdated software, ever (unless enabled on request), and no support if/when your account gets hacked (the account will be suspended immediately). [[Category:CMSs]] [[Category:Security & anti-spam]] 31f49a16ebaabd9492ff6d59afaaff01e61b08cc 0 144 1069 2020-04-17T23:09:47Z Bert 8 Created page with "ULYSSIS considers security an important part of its services. While we of course make sure our software is up-to-date, there is also the security of the applications our users..." wikitext text/x-wiki ULYSSIS considers security an important part of its services. While we of course make sure our software is up-to-date, there is also the security of the applications our users use, the emails they receive, and the account they have on our servers. Even though it's obvious our users are responsible for their own software, passwords and emails, we attempt to safeguard them from harm and adhere to good general standards as well as those agreed upon with KU Leuven ICTS when we started. == Web == As the main service of our hosting accounts, most of our security revolves around securing the many applications our users use. The main responsibility for these applications lies of course with the users who should frequently apply updates and make sure the code they write is secure. === General measures === Under normal circumstances, most web applications will not have interaction with non-http(s) third party applications and APIs (if they have any external interaction in the first place), therefore we only allow general outgoing connections from our webworkers to ports 80 and 443. Based on requests from users and ICTS, we do allow specific outgoing connections to the KU Leuven LDAP and KU Leuven Dingnet MQTT server. If you require access to an unusual port on a specific service, preferably of some kind of academic value or offered by KU Leuven, feel free to contact us with a description of what you would like to do and what services, IP addresses and ports are relevant (and why). As part of our arrangement with KU Leuven ICTS, we pass all our mail through their central email and anti-virus system (CAV). Because of this restriction, it's not possible to connect to external services for email from within our network. You can however easily use local email on our servers, which will be processed as you would expect. To prevent spam and other problems, we do monitor volume and assess spaminess before forwarding emails. More details are available on [[Sending email from websites]] and in the section about email on this page. Most users are aware of Google and Bing, as well as their bots that scan the internet for interesting and useful websites. There are however many other search bots out there, some of which have far from the best reputation. These cause problems with high amounts of traffic due to lack of rate limiting within these bots (which can create problems for resource usage) and almost always collect data for commercial use within products such as SEO services. As these search bots bring no real benefits to our users, bots such as AhrefsBot, Majestic12 and LinkdexBot have been blocked from visiting our webservers in general. Beyond these measures, we also make sure to follow-up any problematic situation and move to suspend the user or website to prevent further harm. Some of these situations include sudden spikes in resource usage, unexpected large email queues, large email delivery failures, high amounts of attempts to connect to blocked ports, or the use of very insecure/outdated software. === CMSs and other popular software === On CMSs and certain pieces of popular software, security is even more important as they are often attacked. Installing updates frequently is therefore paramount. To make sure updates are taken seriously, we have implemented a [[Software Version Checker]] for organisation and kring accounts. Beyond updates, common or short passwords can also be a big problem with CMSs. With the growing popularity of WordPress, we've noticed more frequent dictionary and brute force attacks on WordPress login forms and XML RPC management interfaces. To protect our users, as well as to prevent problematic increases in traffic and resource usage, we automatically block IPs that attempt to access wp-login.php or xmlrpc.php too often and we've installed extra monitoring systems. This of course doesn't mean we don't expect our users to use strong passwords and perhaps even consider disabling XML RPC. == Email and spam == All emails that are processed by ULYSSIS pass through our spam setup as well as the central anti-virus (CAV) of the KU Leuven. While the KU Leuven focuses specifically on malware, we apply a more broad approach. Every email is given a spam score based on its headers and content. The score and tests are included in every email. If the score surpasses 5.0, the email is marked as spam but still delivered, if it surpasses 7.5 it is no longer delivered. Emails that include executables (even hidden within an archive or a screensaver) are never delivered and our team is notified. As we receive a lot of exotic spam that is often not in English, regular spam rules often don't suffice to prevent spam from being delivered. At ULYSSIS we therefore use a large set of custom spam rules we've written based on samples. Please refer to the [[spam]] article on this documentation website for details on how to submit spam samples. If you are having issues with emails that are processed by our servers being marked as spam, keep in mind that as our email has to pass through the CAV, we depend on the KU Leuven to maintain a good reputation with other email providers. == Other == Beyond specific measures on our web and email services, we also take certain security measures on other services or on our entire network. === Shellservers === On our shellservers we implement a simple technique to prevent brute forcing or dictionary attacks through SSH by temporarily blocking IP addresses after several failed login attempts. While this usually goes completely unnoticed by users, in circumstances where a user uses the wrong password many times, they may get hit by this security measure and would have to either wait for a few minutes or try to connect to our other shellserver. Similar to all of our webservers, connecting to external email servers is not allowed. You can refer to that part of this article or to [[Sending email from websites]] for more information. === Blocklists === We maintain automatic as well as manual blocklists to prevent spam and attacks from IP addresses or ranges that are known to commit these kinds of actions. We only block those IP addresses that have been implicated in illegal activities, and try to always prevent undue implications for addresses within the same range that have not necessarily been part of any activity. In case of addresses that may change operator, we may also consider a block to be temporary. ac08c961fcf21c9bd523d46ccfe4b6da7e4fbcee 0 34 1070 727 2020-04-19T10:39:06Z Principis 32 fix server wikitext text/x-wiki You may want to send e-mail from Gmail using your @ulyssis.org-address, or another domain name that you use for your account. Gmail allows you to do this, but asks for SMTP info. We don't provide SMTP on our own mail server, but you can use the SMTP servers of the KU Leuven. # In Gmail, go to '''Settings''' (in Dutch: '''Instellingen'''). # Go to the tab '''Accounts and Import''' (in Dutch: '''Accounts en import''') # Under '''Send mail as:''' ('''E-mailberichten sturen vanaf'''), click on: '''Add another email address you own''' ('''Nog een e-mailadres toevoegen waarvan je eigenaar bent'''). # Fill in your name and the e-mail address, and check '''Treat as an alias.''' ('''Beschouwen als alias.''') More info: https://support.google.com/a/answer/1710338 # Click on '''Next step''' ('''Volgende stap'''). # Fill in the following information SMTP information (https://admin.kuleuven.be/icts/services/email/begrippen): #* '''SMTP server''': '''smtps.kuleuven.be''' #* '''port''': 465 #* '''Username''': your student id #* '''Password''': your KU Leuven password #* SSL # Press on '''Add Account''' ('''Account toevoegen'''). [[Category:Mail]] 0f22049a475ff9fe678c380866f1fe31f55b86cf 0 103 1072 995 2020-05-15T11:14:55Z Bert 8 wikitext text/x-wiki While most webhosting providers give you access to a few or even just one programming language and a set amount of libraries, ULYSSIS prefers to offer more flexibility. We hope to give our users the chance to experiment with different languages, libraries and tools. There are of course limits to what is realistic for us to install. More on that below. == Using a programming language, library or tool that is not installed == If the package that you would like us to install is available in the software repository of our current operating system, then that is usually not a problem. We currently use Ubuntu on all our servers, specifically, we upgrade to the latest LTS every summer vacation following the release of a new one. You can verify which version we are running by executing "cat /etc/lsb-release" on one of our shellservers. After you have verified what version we are running, you can refer to https://packages.ubuntu.com/ to check whether your package is available in that version of Ubuntu. If it is, then you can contact us by email on ulyssis@ulyssis.org which package or packages you would like to have installed, and what you will be using it for. You will most likely get a positive response. If your package is not in the repository, you will have to go for a [[Installing packages#Manual installation|Manual installation]]. == Using a newer/different version == As you can read in the section concerning the installation of new packages, we only offer the version available in the repository of the version of Ubuntu that we are running. In most cases, this means you will have to wait for a version upgrade with the next LTS release, or go for a [[Installing packages#Manual installation|Manual installation]]. However, there are some exceptions. Sometimes multiple version will be available in the repository, such as with Python 2 and 3, or Perl 5 and 6. In such cases, you can refer to the section above for instructions on how to request an installation. == Manual installation == If you want to install a piece of software that is not available in the repository or you wish to install another version, you can always install it manually onto your account. It is important to keep in mind that ULYSSIS will not support manually installed software, and that you are fully responsible for the security of this software. You are free to ask us questions, but we will most probably not help you. If you do require a manual installation of specific software, we expect you to be capable of maintaining it as well. The way you install your software differs depending on the software. You could be using tools such as pip, gem or npm to install to a directory in your home folder, you could be using a virtual environment, or you could be compiling your own binary. We suggest you look at the documentation of the software you're using very thoroughly, and make sure you are comfortable with what you are doing and aware of your responsibilities. After installing your software locally onto your account, you will probably want to add an alias in your dotfiles (for example .profile or .bashrc) to make using your manually installed version easier. In case you are using your piece of software for a web service, you will want to make sure you edit your fastcgi script or any other involved scripts to use your binary by changing the path or hardcoding the location. == Node.js == We do not offer Node.js by default because we can't give you the most recent release. But you can use nvm ([https://github.com/creationix/nvm Node Version Manager]) which installs the required version for you. The installation should be straightforward and a guide can be found [https://github.com/nvm-sh/nvm#installing-and-updating here]. [[Category:Shell]] 40b7632f4b9aacc3363315d6d740b32dfb167e31 0 10 1082 1081 2020-07-07T22:38:53Z Bert 8 /* Requesting SSL from the KU Leuven */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty representative body (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request the following steps have to be taken: * Setup the site that needs SSL * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible that for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be and *.student.kuleuven.ac.be domain. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, download the <code>acme.sh</code> script as explained in the documentation: https://github.com/acmesh-official/acme.sh#1-how-to-install Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be If we provide an email address, for example "email@example.com", Let's Encrypt will remind us to renew our certificates when necessary. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew -d mydomain.be The renewed certificates will automatically be copied to the path specified in the <code>--issue</code> command. '''After renewing certificates, you have to email us to install your renewed certificate.''' ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] 6183524d174314522d11fe972d4ec73e1e6b5db1 1083 1082 2020-07-07T22:39:38Z Bert 8 /* Requesting SSL from the KU Leuven */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty representative body (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request the following steps have to be performed: * Setup the site that needs SSL * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. We will then generate the required cryptographic key and request and submit them with ICTS. It usually takes a few days before they have had time to verify both the domain and then the request for SSL itself. As soon as ICTS approves the request we will install the certificate and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible that for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be and *.student.kuleuven.ac.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, download the <code>acme.sh</code> script as explained in the documentation: https://github.com/acmesh-official/acme.sh#1-how-to-install Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be If we provide an email address, for example "email@example.com", Let's Encrypt will remind us to renew our certificates when necessary. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew -d mydomain.be The renewed certificates will automatically be copied to the path specified in the <code>--issue</code> command. '''After renewing certificates, you have to email us to install your renewed certificate.''' ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] 5bb5035776b8ab638143592d6684b9dfab57e678 1084 1083 2020-07-07T22:47:21Z Bert 8 /* Requesting SSL from the KU Leuven */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty representative body (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request the following steps have to be performed: * Setup the site that needs SSL * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible that for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be and *.student.kuleuven.ac.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, download the <code>acme.sh</code> script as explained in the documentation: https://github.com/acmesh-official/acme.sh#1-how-to-install Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be If we provide an email address, for example "email@example.com", Let's Encrypt will remind us to renew our certificates when necessary. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew -d mydomain.be The renewed certificates will automatically be copied to the path specified in the <code>--issue</code> command. '''After renewing certificates, you have to email us to install your renewed certificate.''' ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] 30ce3c46e52cc7c2efa0fdd1b90357a79eef6062 1085 1084 2020-07-07T23:03:28Z Bert 8 /* Requesting SSL from the KU Leuven */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty representative bodies (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request, the following steps have to be performed: * Set up the site that needs SSL * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible that for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be and *.student.kuleuven.ac.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, download the <code>acme.sh</code> script as explained in the documentation: https://github.com/acmesh-official/acme.sh#1-how-to-install Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be If we provide an email address, for example "email@example.com", Let's Encrypt will remind us to renew our certificates when necessary. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew -d mydomain.be The renewed certificates will automatically be copied to the path specified in the <code>--issue</code> command. '''After renewing certificates, you have to email us to install your renewed certificate.''' ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] 6ce8be875042f883399f3b67cb8f6a48626cf573 1086 1085 2020-07-07T23:03:49Z Bert 8 /* Requesting SSL from the KU Leuven */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty representative bodies (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request, the following steps have to be performed: * Set up the site that needs SSL * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible that for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be and *.student.kuleuven.ac.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, download the <code>acme.sh</code> script as explained in the documentation: https://github.com/acmesh-official/acme.sh#1-how-to-install Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be If we provide an email address, for example "email@example.com", Let's Encrypt will remind us to renew our certificates when necessary. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew -d mydomain.be The renewed certificates will automatically be copied to the path specified in the <code>--issue</code> command. '''After renewing certificates, you have to email us to install your renewed certificate.''' ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] 633218a2d09dd93c7cb9acc3ce7c1a8d97411d49 1087 1086 2020-07-07T23:05:18Z Bert 8 /* Requesting SSL from the KU Leuven */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty representative bodies (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request, the following steps have to be performed: * Set up the site that needs SSL * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be and *.student.kuleuven.ac.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, download the <code>acme.sh</code> script as explained in the documentation: https://github.com/acmesh-official/acme.sh#1-how-to-install Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be If we provide an email address, for example "email@example.com", Let's Encrypt will remind us to renew our certificates when necessary. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew -d mydomain.be The renewed certificates will automatically be copied to the path specified in the <code>--issue</code> command. '''After renewing certificates, you have to email us to install your renewed certificate.''' ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] ccbf19946bff37b60963ff463f40734a378516a7 1088 1087 2020-07-08T01:39:07Z Bert 8 wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty representative bodies (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request, the following steps have to be performed: * Make sure our nameservers are being used for the involved domain(s), see [[Adding domain names]] * Set up the site that needs SSL * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be and *.student.kuleuven.ac.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, download the <code>acme.sh</code> script as explained in the documentation: https://github.com/acmesh-official/acme.sh#1-how-to-install Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be If we provide an email address, for example "email@example.com", Let's Encrypt will remind us to renew our certificates when necessary. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew -d mydomain.be The renewed certificates will automatically be copied to the path specified in the <code>--issue</code> command. '''After renewing certificates, you have to email us to install your renewed certificate.''' ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] a9af1dee873f540e7fcbe16e1c7714271b069150 1089 1088 2020-07-08T01:39:24Z Bert 8 wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty representative bodies (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request, the following steps have to be performed: * Make sure our nameservers are being used for the involved domain(s), as explained on [[Adding domain names]] * Set up the site that needs SSL * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be and *.student.kuleuven.ac.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, download the <code>acme.sh</code> script as explained in the documentation: https://github.com/acmesh-official/acme.sh#1-how-to-install Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be If we provide an email address, for example "email@example.com", Let's Encrypt will remind us to renew our certificates when necessary. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew -d mydomain.be The renewed certificates will automatically be copied to the path specified in the <code>--issue</code> command. '''After renewing certificates, you have to email us to install your renewed certificate.''' ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] a250d047488d3a2dd5e8969ef28ccd5d44d6b36a 1090 1089 2020-07-08T01:41:11Z Bert 8 /* Requesting SSL from the KU Leuven */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty representative bodies (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request, the following steps have to be performed: * Make sure our nameservers are being used for the involved domain(s), as explained on [[Adding domain names]] * Set up the site that needs SSL if that's not already the case * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be and *.student.kuleuven.ac.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, download the <code>acme.sh</code> script as explained in the documentation: https://github.com/acmesh-official/acme.sh#1-how-to-install Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be If we provide an email address, for example "email@example.com", Let's Encrypt will remind us to renew our certificates when necessary. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew -d mydomain.be The renewed certificates will automatically be copied to the path specified in the <code>--issue</code> command. '''After renewing certificates, you have to email us to install your renewed certificate.''' ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] 7bb8cda83b5a971ff1596e51cdfab5fd0f52705b 1091 1090 2020-07-08T01:42:44Z Bert 8 wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty representative bodies (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request, the following steps have to be performed: * Set up the site that needs SSL if that's not already the case * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Make sure our nameservers are being used for the involved domain(s), as explained on [[Adding domain names]] * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be and *.student.kuleuven.ac.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, download the <code>acme.sh</code> script as explained in the documentation: https://github.com/acmesh-official/acme.sh#1-how-to-install Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be If we provide an email address, for example "email@example.com", Let's Encrypt will remind us to renew our certificates when necessary. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew -d mydomain.be The renewed certificates will automatically be copied to the path specified in the <code>--issue</code> command. '''After renewing certificates, you have to email us to install your renewed certificate.''' ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] bccb07d751f4495bddb9f4c45fc85275cb60047f 1092 1091 2020-07-08T01:51:35Z Bert 8 wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty consultative bodies (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request, the following steps have to be performed: * Set up the site that needs SSL if that's not already the case * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Make sure our nameservers are being used for the involved domain(s), as explained on [[Adding domain names]] * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be and *.student.kuleuven.ac.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, download the <code>acme.sh</code> script as explained in the documentation: https://github.com/acmesh-official/acme.sh#1-how-to-install Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be If we provide an email address, for example "email@example.com", Let's Encrypt will remind us to renew our certificates when necessary. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew -d mydomain.be The renewed certificates will automatically be copied to the path specified in the <code>--issue</code> command. '''After renewing certificates, you have to email us to install your renewed certificate.''' ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. ==Logs== Due to the nature of our setup (dumb loadbalancer combined with shibboleth on webworkers), all https traffic will seem to come from our loadbalancer IP address instead of the actual originating IP address. Keep this in mind when checking log files. [[Category:Webserver]] 451843e8c5576845ccbb962640cf62b9c6f50b1b 1129 1092 2020-09-18T08:29:32Z Bert 8 wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty consultative bodies (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request, the following steps have to be performed: * Set up the site that needs SSL if that's not already the case * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Make sure our nameservers are being used for the involved domain(s), as explained on [[Adding domain names]] * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be and *.student.kuleuven.ac.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, download the <code>acme.sh</code> script as explained in the documentation: https://github.com/acmesh-official/acme.sh#1-how-to-install Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be If we provide an email address, for example "email@example.com", Let's Encrypt will remind us to renew our certificates when necessary. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew -d mydomain.be The renewed certificates will automatically be copied to the path specified in the <code>--issue</code> command. '''After renewing certificates, you have to email us to install your renewed certificate.''' ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. [[Category:Webserver]] c9367a4efbb0e5905557381d57c222339241e5e1 0 145 1093 2020-07-08T19:46:57Z Vincenttc 21 Created page with "This page lists the changes to the webservers of ULYSSIS in the summer of 2020, and how you can prepare for it. If any of these instructions are not clear to you, or if you ha..." wikitext text/x-wiki This page lists the changes to the webservers of ULYSSIS in the summer of 2020, and how you can prepare for it. If any of these instructions are not clear to you, or if you have some more questions about the change, '''don't hesitate to e-mail us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]'''. = When are the changes planned? = The change will be in effect after the downtime in september when we upgrade all of our servers. The exact date has not yet been decided. We will contact our users once it has. After that, we will use the new webserver configuration. = What will change? = We will upgrade the Ubuntu release on our servers from 18.04 LTS to 20.04 LTS. This will include newer version of many services. An overview of the most important version changes can be found below. For other services/packages, one can always use the [https://packages.ubuntu.com/ Ubuntu Package Search]. The distribution name for Ubuntu 20.04 LTS is "focal". * PHP will be updated from 7.2 to 7.4 * PostgreSQL will be updated from 10 to 12 * MariaDB (MySQL) will be updated from 10.1.44 to 10.3.22 * Python will be updated from 3.6 to 3.8 Note that any existing Python virtual environments in use will need to be recreated in order to function properly. Additionally, we will make use of the maintenance window to change certain aspects of our services. Notably, we will no longer support the user of <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> files. Instead, users are advised to use <code>.user.ini</code> files. More details regarding the changes can be found on the remainder of this page. == Support for <code>php_flag</code> and <code>php_value</code> == Support for <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> as described in older versions of [[Special:PermanentLink/714|Managing PHP errors]] and [[Special:PermanentLink/715]] will no longer be supported. If you have added these options, you will have to remove them and migrate them to a <code>.user.ini</code> file. The current versions of these pages ([[Managing PHP errors]] and [[Setting PHP options]]) explain how one can do this. Note that if the the options are inside a block that checks for the existence of a specific version of <code>mod_php</code>, then this will not cause an error. This is the case for many CMSs. == Basic Auth in PHP and FCGI scripts == When using Basic authentication on a PHP or FCGI script, it was necessary to apply a [[Basic authentication|workaround]]. This will no longer be needed in the future as the Authorization header will be passed by default to the script. This behavior can be disabled using the CGIPassAuth directive. For more details see https://httpd.apache.org/docs/current/en/mod/core.html#cgipassauth . == Client IP address == Currently, the [[Getting Apache logs|Apache logs]] only show the proper client IP when unencrypted traffic is used (no HTTPS). When using HTTPS, the client IP is logged as 193.190.253.234, the IP address of our loadbalancer. During the maintenance, we will make the required changes to ensure that the logged IP adres will be the clients IP adres, even if HTTPS is used. Additionally, this will improve the effectiveness of the brute-force detection in place on our webservers for Wordpress installations. For more information, see [[ULYSSIS security measures#CMSs and other popular software|ULYSSIS security measures]]. 3e71cffc979350b0c7b7f94e6e18147a35775e15 1094 1093 2020-07-08T19:50:54Z Vincenttc 21 /* Support for php_flag and php_value */ wikitext text/x-wiki This page lists the changes to the webservers of ULYSSIS in the summer of 2020, and how you can prepare for it. If any of these instructions are not clear to you, or if you have some more questions about the change, '''don't hesitate to e-mail us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]'''. = When are the changes planned? = The change will be in effect after the downtime in september when we upgrade all of our servers. The exact date has not yet been decided. We will contact our users once it has. After that, we will use the new webserver configuration. = What will change? = We will upgrade the Ubuntu release on our servers from 18.04 LTS to 20.04 LTS. This will include newer version of many services. An overview of the most important version changes can be found below. For other services/packages, one can always use the [https://packages.ubuntu.com/ Ubuntu Package Search]. The distribution name for Ubuntu 20.04 LTS is "focal". * PHP will be updated from 7.2 to 7.4 * PostgreSQL will be updated from 10 to 12 * MariaDB (MySQL) will be updated from 10.1.44 to 10.3.22 * Python will be updated from 3.6 to 3.8 Note that any existing Python virtual environments in use will need to be recreated in order to function properly. Additionally, we will make use of the maintenance window to change certain aspects of our services. Notably, we will no longer support the user of <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> files. Instead, users are advised to use <code>.user.ini</code> files. More details regarding the changes can be found on the remainder of this page. == Support for <code>php_flag</code> and <code>php_value</code> == Support for <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> as described in older versions of [[Special:PermanentLink/714|Managing PHP errors]] and [[Special:PermanentLink/715|Setting PHP options]] will no longer be supported. If you have added these options, you will have to remove them and migrate them to a <code>.user.ini</code> file. The current versions of these pages ([[Managing PHP errors]] and [[Setting PHP options]]) explain how one can do this. Note that if the the options are inside a block that checks for the existence of a specific version of <code>mod_php</code>, then this will not cause an error. This is the case for many CMSs. == Basic Auth in PHP and FCGI scripts == When using Basic authentication on a PHP or FCGI script, it was necessary to apply a [[Basic authentication|workaround]]. This will no longer be needed in the future as the Authorization header will be passed by default to the script. This behavior can be disabled using the CGIPassAuth directive. For more details see https://httpd.apache.org/docs/current/en/mod/core.html#cgipassauth . == Client IP address == Currently, the [[Getting Apache logs|Apache logs]] only show the proper client IP when unencrypted traffic is used (no HTTPS). When using HTTPS, the client IP is logged as 193.190.253.234, the IP address of our loadbalancer. During the maintenance, we will make the required changes to ensure that the logged IP adres will be the clients IP adres, even if HTTPS is used. Additionally, this will improve the effectiveness of the brute-force detection in place on our webservers for Wordpress installations. For more information, see [[ULYSSIS security measures#CMSs and other popular software|ULYSSIS security measures]]. 122adb5680a645f9534a41e06af464013fb58b58 1099 1094 2020-07-08T22:42:07Z Bert 8 wikitext text/x-wiki This page lists the changes to the webservers of ULYSSIS in the summer of 2020, and how you can prepare for it. If any of these instructions are not clear to you, or if you have some more questions about the change, '''don't hesitate to e-mail us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]'''. == When are the changes planned? == The change will be in effect after the downtime in september when we upgrade all of our servers. The exact date has not yet been decided. We will contact our users once it has. After that, we will use the new webserver configuration. == What will change? == We will upgrade the Ubuntu release on our servers from 18.04 LTS to 20.04 LTS. This will include newer version of many services. An overview of the most important version changes can be found below. For other services/packages, one can always use the [https://packages.ubuntu.com/ Ubuntu Package Search]. The distribution name for Ubuntu 20.04 LTS is "focal". * PHP will be updated from 7.2 to 7.4 * PostgreSQL will be updated from 10 to 12 * MariaDB (MySQL) will be updated from 10.1.44 to 10.3.22 * Python will be updated from 3.6 to 3.8 Note that any existing Python virtual environments in use will need to be recreated in order to function properly. Additionally, we will make use of the maintenance window to change certain aspects of our services. Notably, we will no longer support the user of <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> files. Instead, users are advised to use <code>.user.ini</code> files. More details regarding the changes can be found on the remainder of this page. === Support for <code>php_flag</code> and <code>php_value</code> === Support for <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> as described in older versions of [[Special:PermanentLink/714|Managing PHP errors]] and [[Special:PermanentLink/715|Setting PHP options]] will no longer be supported. If you have added these options, you will have to remove them and migrate them to a <code>.user.ini</code> file. The current versions of these pages ([[Managing PHP errors]] and [[Setting PHP options]]) explain how one can do this. Note that if the the options are inside a block that checks for the existence of a specific version of <code>mod_php</code>, then this will not cause an error. This is the case for many CMSs. === Basic Auth in PHP and FCGI scripts === When using Basic authentication on a PHP or FCGI script, it was necessary to apply a [[Basic authentication|workaround]]. This will no longer be needed in the future as the Authorization header will be passed by default to the script. This behavior can be disabled using the CGIPassAuth directive. For more details see https://httpd.apache.org/docs/current/en/mod/core.html#cgipassauth . === Client IP address === Currently, the [[Getting Apache logs|Apache logs]] only show the proper client IP when unencrypted traffic is used (no HTTPS). When using HTTPS, the client IP is logged as 193.190.253.234, the IP address of our loadbalancer. During the maintenance, we will make the required changes to ensure that the logged IP adres will be the clients IP adres, even if HTTPS is used. Additionally, this will improve the effectiveness of the brute-force detection in place on our webservers for Wordpress installations. For more information, see [[ULYSSIS security measures#CMSs and other popular software|ULYSSIS security measures]]. da6b382a1b749e642344f32f636a0e53a22ca880 1100 1099 2020-07-08T23:00:22Z Bert 8 wikitext text/x-wiki This page lists the changes to the webservers of ULYSSIS in the summer of 2020, and how you can prepare for it. If any of these instructions are not clear to you, or if you have some more questions about the changes, '''don't hesitate to e-mail us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]'''. == When are the changes planned? == The change will be in effect after the downtime in september when we upgrade all of our servers. The exact date has not yet been decided. We will contact our users once it has. After that, we will use the new webserver configuration. == What will change? == We will upgrade the Ubuntu release on our servers from 18.04 LTS to 20.04 LTS. This will include newer version of many services. An overview of the most important version changes can be found below. For other services/packages, one can always use the [https://packages.ubuntu.com/ Ubuntu Package Search]. The distribution name for Ubuntu 20.04 LTS is "focal". * PHP will be updated from 7.2 to 7.4 * PostgreSQL will be updated from 10 to 12 * MariaDB (MySQL) will be updated from 10.1.44 to 10.3.22 * Python will be updated from 3.6 to 3.8 Note that any existing Python virtual environments in use will need to be recreated in order to function properly. Additionally, we will make use of the maintenance window to change certain aspects of our services. Notably, we will no longer support the user of <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> files. Instead, users are advised to use <code>.user.ini</code> files. More details regarding the changes can be found on the remainder of this page. === Support for <code>php_flag</code> and <code>php_value</code> === Support for <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> as described in older versions of [[Special:PermanentLink/714|Managing PHP errors]] and [[Special:PermanentLink/715|Setting PHP options]] will no longer be supported. If you have added these options, you will have to remove them and migrate them to a <code>.user.ini</code> file. The current versions of these pages ([[Managing PHP errors]] and [[Setting PHP options]]) explain how one can do this. Note that if the the options are inside a block that checks for the existence of a specific version of <code>mod_php</code>, then this will not cause an error. This is the case for many CMSs. === Basic Auth in PHP and FCGI scripts === When using Basic authentication on a PHP or FCGI script, it was necessary to apply a [[Basic authentication|workaround]]. This will no longer be needed in the future as the Authorization header will be passed by default to the script. This behavior can be disabled using the CGIPassAuth directive. For more details see https://httpd.apache.org/docs/current/en/mod/core.html#cgipassauth . === Client IP address === Currently, the [[Getting Apache logs|Apache logs]] only show the proper client IP when unencrypted traffic is used (no HTTPS). When using HTTPS, the client IP is logged as 193.190.253.234, the IP address of our loadbalancer. During the maintenance, we will make the required changes to ensure that the logged IP adres will be the clients IP adres, even if HTTPS is used. Additionally, this will improve the effectiveness of the brute-force detection in place on our webservers for Wordpress installations. For more information, see [[ULYSSIS security measures#CMSs and other popular software|ULYSSIS security measures]]. 238a19105aa71a4e3449d3956a098e54e2eb149c 1101 1100 2020-07-08T23:01:15Z Bert 8 /* When are the changes planned? */ wikitext text/x-wiki This page lists the changes to the webservers of ULYSSIS in the summer of 2020, and how you can prepare for it. If any of these instructions are not clear to you, or if you have some more questions about the changes, '''don't hesitate to e-mail us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]'''. == When are the changes planned? == The changes will be in effect after the downtime in September when we upgrade all of our servers. The exact date has not yet been decided. We will contact our users once it has. After that, we will use the new webserver configuration. == What will change? == We will upgrade the Ubuntu release on our servers from 18.04 LTS to 20.04 LTS. This will include newer version of many services. An overview of the most important version changes can be found below. For other services/packages, one can always use the [https://packages.ubuntu.com/ Ubuntu Package Search]. The distribution name for Ubuntu 20.04 LTS is "focal". * PHP will be updated from 7.2 to 7.4 * PostgreSQL will be updated from 10 to 12 * MariaDB (MySQL) will be updated from 10.1.44 to 10.3.22 * Python will be updated from 3.6 to 3.8 Note that any existing Python virtual environments in use will need to be recreated in order to function properly. Additionally, we will make use of the maintenance window to change certain aspects of our services. Notably, we will no longer support the user of <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> files. Instead, users are advised to use <code>.user.ini</code> files. More details regarding the changes can be found on the remainder of this page. === Support for <code>php_flag</code> and <code>php_value</code> === Support for <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> as described in older versions of [[Special:PermanentLink/714|Managing PHP errors]] and [[Special:PermanentLink/715|Setting PHP options]] will no longer be supported. If you have added these options, you will have to remove them and migrate them to a <code>.user.ini</code> file. The current versions of these pages ([[Managing PHP errors]] and [[Setting PHP options]]) explain how one can do this. Note that if the the options are inside a block that checks for the existence of a specific version of <code>mod_php</code>, then this will not cause an error. This is the case for many CMSs. === Basic Auth in PHP and FCGI scripts === When using Basic authentication on a PHP or FCGI script, it was necessary to apply a [[Basic authentication|workaround]]. This will no longer be needed in the future as the Authorization header will be passed by default to the script. This behavior can be disabled using the CGIPassAuth directive. For more details see https://httpd.apache.org/docs/current/en/mod/core.html#cgipassauth . === Client IP address === Currently, the [[Getting Apache logs|Apache logs]] only show the proper client IP when unencrypted traffic is used (no HTTPS). When using HTTPS, the client IP is logged as 193.190.253.234, the IP address of our loadbalancer. During the maintenance, we will make the required changes to ensure that the logged IP adres will be the clients IP adres, even if HTTPS is used. Additionally, this will improve the effectiveness of the brute-force detection in place on our webservers for Wordpress installations. For more information, see [[ULYSSIS security measures#CMSs and other popular software|ULYSSIS security measures]]. 9d2a3a35c85ae38d36a3c89081256f732d06afcd 1103 1101 2020-07-08T23:36:08Z Bert 8 /* Support for php_flag and php_value */ wikitext text/x-wiki This page lists the changes to the webservers of ULYSSIS in the summer of 2020, and how you can prepare for it. If any of these instructions are not clear to you, or if you have some more questions about the changes, '''don't hesitate to e-mail us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]'''. == When are the changes planned? == The changes will be in effect after the downtime in September when we upgrade all of our servers. The exact date has not yet been decided. We will contact our users once it has. After that, we will use the new webserver configuration. == What will change? == We will upgrade the Ubuntu release on our servers from 18.04 LTS to 20.04 LTS. This will include newer version of many services. An overview of the most important version changes can be found below. For other services/packages, one can always use the [https://packages.ubuntu.com/ Ubuntu Package Search]. The distribution name for Ubuntu 20.04 LTS is "focal". * PHP will be updated from 7.2 to 7.4 * PostgreSQL will be updated from 10 to 12 * MariaDB (MySQL) will be updated from 10.1.44 to 10.3.22 * Python will be updated from 3.6 to 3.8 Note that any existing Python virtual environments in use will need to be recreated in order to function properly. Additionally, we will make use of the maintenance window to change certain aspects of our services. Notably, we will no longer support the user of <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> files. Instead, users are advised to use <code>.user.ini</code> files. More details regarding the changes can be found on the remainder of this page. === Support for <code>php_flag</code> and <code>php_value</code> === Support for <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> as described in older versions of [[Special:PermanentLink/714|Managing PHP errors]] and [[Special:PermanentLink/715|Setting PHP options]] will no longer be supported. If you have added these options, you will have to remove them and migrate them to a <code>.user.ini</code> file. The current versions of these pages ([[Managing PHP errors]] and [[Setting PHP options]]) explain how one can do this. Note that if the options are inside a block that checks for the existence of a specific version of <code>mod_php</code>, then this will not cause an error. This is the case for many CMSs. === Basic Auth in PHP and FCGI scripts === When using Basic authentication on a PHP or FCGI script, it was necessary to apply a [[Basic authentication|workaround]]. This will no longer be needed in the future as the Authorization header will be passed by default to the script. This behavior can be disabled using the CGIPassAuth directive. For more details see https://httpd.apache.org/docs/current/en/mod/core.html#cgipassauth . === Client IP address === Currently, the [[Getting Apache logs|Apache logs]] only show the proper client IP when unencrypted traffic is used (no HTTPS). When using HTTPS, the client IP is logged as 193.190.253.234, the IP address of our loadbalancer. During the maintenance, we will make the required changes to ensure that the logged IP adres will be the clients IP adres, even if HTTPS is used. Additionally, this will improve the effectiveness of the brute-force detection in place on our webservers for Wordpress installations. For more information, see [[ULYSSIS security measures#CMSs and other popular software|ULYSSIS security measures]]. 94d50a29ec2a7468ee0cc849c1b55888a28c73aa 1104 1103 2020-07-08T23:37:58Z Bert 8 /* Client IP address */ wikitext text/x-wiki This page lists the changes to the webservers of ULYSSIS in the summer of 2020, and how you can prepare for it. If any of these instructions are not clear to you, or if you have some more questions about the changes, '''don't hesitate to e-mail us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]'''. == When are the changes planned? == The changes will be in effect after the downtime in September when we upgrade all of our servers. The exact date has not yet been decided. We will contact our users once it has. After that, we will use the new webserver configuration. == What will change? == We will upgrade the Ubuntu release on our servers from 18.04 LTS to 20.04 LTS. This will include newer version of many services. An overview of the most important version changes can be found below. For other services/packages, one can always use the [https://packages.ubuntu.com/ Ubuntu Package Search]. The distribution name for Ubuntu 20.04 LTS is "focal". * PHP will be updated from 7.2 to 7.4 * PostgreSQL will be updated from 10 to 12 * MariaDB (MySQL) will be updated from 10.1.44 to 10.3.22 * Python will be updated from 3.6 to 3.8 Note that any existing Python virtual environments in use will need to be recreated in order to function properly. Additionally, we will make use of the maintenance window to change certain aspects of our services. Notably, we will no longer support the user of <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> files. Instead, users are advised to use <code>.user.ini</code> files. More details regarding the changes can be found on the remainder of this page. === Support for <code>php_flag</code> and <code>php_value</code> === Support for <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> as described in older versions of [[Special:PermanentLink/714|Managing PHP errors]] and [[Special:PermanentLink/715|Setting PHP options]] will no longer be supported. If you have added these options, you will have to remove them and migrate them to a <code>.user.ini</code> file. The current versions of these pages ([[Managing PHP errors]] and [[Setting PHP options]]) explain how one can do this. Note that if the options are inside a block that checks for the existence of a specific version of <code>mod_php</code>, then this will not cause an error. This is the case for many CMSs. === Basic Auth in PHP and FCGI scripts === When using Basic authentication on a PHP or FCGI script, it was necessary to apply a [[Basic authentication|workaround]]. This will no longer be needed in the future as the Authorization header will be passed by default to the script. This behavior can be disabled using the CGIPassAuth directive. For more details see https://httpd.apache.org/docs/current/en/mod/core.html#cgipassauth . === Client IP address === Currently, the [[Getting Apache logs|Apache logs]] only show the proper client IP when unencrypted traffic is used (no HTTPS). When using HTTPS, the client IP is logged as 193.190.253.234, the IP address of our loadbalancer. During the maintenance, we will make the required changes to ensure that the logged IP address will be the client's IP address, even if HTTPS is used. Additionally, this will improve the effectiveness of the brute-force detection in place on our webservers for WordPress installations. For more information, see [[ULYSSIS security measures#CMSs and other popular software|ULYSSIS security measures]]. e692179e5bc9f3cbde23fc72ef21982b6b4ef727 1105 1104 2020-07-09T09:59:51Z Vincenttc 21 wikitext text/x-wiki This page lists the changes to the webservers of ULYSSIS in the summer of 2020, and how you can prepare for it. If any of these instructions are not clear to you, or if you have some more questions about the changes, '''don't hesitate to e-mail us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]'''. == When are the changes planned? == The changes will be in effect after the downtime in September when we upgrade all of our servers. The exact date has not yet been decided. We will contact our users once it has. After that, we will use the new webserver configuration. == What will change? == We will upgrade the Ubuntu release on our servers from 18.04 LTS to 20.04 LTS. This will include newer version of many services. An overview of the most important version changes can be found below. For other services/packages, you can always use the [https://packages.ubuntu.com/ Ubuntu Package Search]. The distribution name for Ubuntu 20.04 LTS is "focal". * PHP will be updated from 7.2 to 7.4 * PostgreSQL will be updated from 10 to 12 * MariaDB (MySQL) will be updated from 10.1.44 to 10.3.22 * Python will be updated from 3.6 to 3.8 Note that any existing Python virtual environments in use will need to be recreated in order to function properly. Additionally, we will make use of the maintenance window to change certain aspects of our services. Notably, we will no longer support the user of <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> files. Instead, users are advised to use <code>.user.ini</code> files. More details regarding the changes can be found on the remainder of this page. === Support for <code>php_flag</code> and <code>php_value</code> === Support for <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> as described in older versions of [[Special:PermanentLink/714|Managing PHP errors]] and [[Special:PermanentLink/715|Setting PHP options]] will no longer be supported. If you have added these options, you will have to remove them and migrate them to a <code>.user.ini</code> file. The current versions of these pages ([[Managing PHP errors]] and [[Setting PHP options]]) explain how you can do this. Note that if the options are inside a block that checks for the existence of a specific version of <code>mod_php</code>, then this will not cause an error. This is the case for many CMSs. === Basic Auth in PHP and FCGI scripts === When using Basic authentication on a PHP or FCGI script, it was necessary to apply a [[Basic authentication|workaround]]. This will no longer be needed in the future as the Authorization header will be passed by default to the script. This behavior can be disabled using the CGIPassAuth directive. For more details see https://httpd.apache.org/docs/current/en/mod/core.html#cgipassauth . === Client IP address === Currently, the [[Getting Apache logs|Apache logs]] only show the proper client IP when unencrypted traffic is used (no HTTPS). When using HTTPS, the client IP is logged as 193.190.253.234, the IP address of our loadbalancer. During the maintenance, we will make the required changes to ensure that the logged IP address will be the client's IP address, even if HTTPS is used. Additionally, this will improve the effectiveness of the brute-force detection in place on our webservers for WordPress installations. For more information, see [[ULYSSIS security measures#CMSs and other popular software|ULYSSIS security measures]]. ef80191dd07b1b2e699056b373884238bbc0757f 1108 1105 2020-07-19T20:49:18Z Bert 8 /* Support for php_flag and php_value */ wikitext text/x-wiki This page lists the changes to the webservers of ULYSSIS in the summer of 2020, and how you can prepare for it. If any of these instructions are not clear to you, or if you have some more questions about the changes, '''don't hesitate to e-mail us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]'''. == When are the changes planned? == The changes will be in effect after the downtime in September when we upgrade all of our servers. The exact date has not yet been decided. We will contact our users once it has. After that, we will use the new webserver configuration. == What will change? == We will upgrade the Ubuntu release on our servers from 18.04 LTS to 20.04 LTS. This will include newer version of many services. An overview of the most important version changes can be found below. For other services/packages, you can always use the [https://packages.ubuntu.com/ Ubuntu Package Search]. The distribution name for Ubuntu 20.04 LTS is "focal". * PHP will be updated from 7.2 to 7.4 * PostgreSQL will be updated from 10 to 12 * MariaDB (MySQL) will be updated from 10.1.44 to 10.3.22 * Python will be updated from 3.6 to 3.8 Note that any existing Python virtual environments in use will need to be recreated in order to function properly. Additionally, we will make use of the maintenance window to change certain aspects of our services. Notably, we will no longer support the user of <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> files. Instead, users are advised to use <code>.user.ini</code> files. More details regarding the changes can be found on the remainder of this page. === Support for <code>php_flag</code> and <code>php_value</code> === {{info|Want to make sure you haven't missed any php_flag or php_value in your .htaccess files? You can find an easy tool to check [[https://docs.ulyssis.org/summer2020tool/|here]]}} Support for <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> as described in older versions of [[Special:PermanentLink/714|Managing PHP errors]] and [[Special:PermanentLink/715|Setting PHP options]] will no longer be supported. If you have added these options, you will have to remove them and migrate them to a <code>.user.ini</code> file. The current versions of these pages ([[Managing PHP errors]] and [[Setting PHP options]]) explain how you can do this. Note that if the options are inside a block that checks for the existence of a specific version of <code>mod_php</code>, then this will not cause an error. This is the case for many CMSs. === Basic Auth in PHP and FCGI scripts === When using Basic authentication on a PHP or FCGI script, it was necessary to apply a [[Basic authentication|workaround]]. This will no longer be needed in the future as the Authorization header will be passed by default to the script. This behavior can be disabled using the CGIPassAuth directive. For more details see https://httpd.apache.org/docs/current/en/mod/core.html#cgipassauth . === Client IP address === Currently, the [[Getting Apache logs|Apache logs]] only show the proper client IP when unencrypted traffic is used (no HTTPS). When using HTTPS, the client IP is logged as 193.190.253.234, the IP address of our loadbalancer. During the maintenance, we will make the required changes to ensure that the logged IP address will be the client's IP address, even if HTTPS is used. Additionally, this will improve the effectiveness of the brute-force detection in place on our webservers for WordPress installations. For more information, see [[ULYSSIS security measures#CMSs and other popular software|ULYSSIS security measures]]. 2b094de9268a15a2e6706c007453c78f717df793 1109 1108 2020-07-19T20:49:41Z Bert 8 /* Support for php_flag and php_value */ wikitext text/x-wiki This page lists the changes to the webservers of ULYSSIS in the summer of 2020, and how you can prepare for it. If any of these instructions are not clear to you, or if you have some more questions about the changes, '''don't hesitate to e-mail us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]'''. == When are the changes planned? == The changes will be in effect after the downtime in September when we upgrade all of our servers. The exact date has not yet been decided. We will contact our users once it has. After that, we will use the new webserver configuration. == What will change? == We will upgrade the Ubuntu release on our servers from 18.04 LTS to 20.04 LTS. This will include newer version of many services. An overview of the most important version changes can be found below. For other services/packages, you can always use the [https://packages.ubuntu.com/ Ubuntu Package Search]. The distribution name for Ubuntu 20.04 LTS is "focal". * PHP will be updated from 7.2 to 7.4 * PostgreSQL will be updated from 10 to 12 * MariaDB (MySQL) will be updated from 10.1.44 to 10.3.22 * Python will be updated from 3.6 to 3.8 Note that any existing Python virtual environments in use will need to be recreated in order to function properly. Additionally, we will make use of the maintenance window to change certain aspects of our services. Notably, we will no longer support the user of <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> files. Instead, users are advised to use <code>.user.ini</code> files. More details regarding the changes can be found on the remainder of this page. === Support for <code>php_flag</code> and <code>php_value</code> === {{info|Want to make sure you haven't missed any php_flag or php_value in your .htaccess files? You can find an easy tool to check [https://docs.ulyssis.org/summer2020tool/ here]}} Support for <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> as described in older versions of [[Special:PermanentLink/714|Managing PHP errors]] and [[Special:PermanentLink/715|Setting PHP options]] will no longer be supported. If you have added these options, you will have to remove them and migrate them to a <code>.user.ini</code> file. The current versions of these pages ([[Managing PHP errors]] and [[Setting PHP options]]) explain how you can do this. Note that if the options are inside a block that checks for the existence of a specific version of <code>mod_php</code>, then this will not cause an error. This is the case for many CMSs. === Basic Auth in PHP and FCGI scripts === When using Basic authentication on a PHP or FCGI script, it was necessary to apply a [[Basic authentication|workaround]]. This will no longer be needed in the future as the Authorization header will be passed by default to the script. This behavior can be disabled using the CGIPassAuth directive. For more details see https://httpd.apache.org/docs/current/en/mod/core.html#cgipassauth . === Client IP address === Currently, the [[Getting Apache logs|Apache logs]] only show the proper client IP when unencrypted traffic is used (no HTTPS). When using HTTPS, the client IP is logged as 193.190.253.234, the IP address of our loadbalancer. During the maintenance, we will make the required changes to ensure that the logged IP address will be the client's IP address, even if HTTPS is used. Additionally, this will improve the effectiveness of the brute-force detection in place on our webservers for WordPress installations. For more information, see [[ULYSSIS security measures#CMSs and other popular software|ULYSSIS security measures]]. 00a866029a76c0eb1f4a9f733bdc60b403e99940 1110 1109 2020-07-19T20:49:51Z Bert 8 /* Support for php_flag and php_value */ wikitext text/x-wiki This page lists the changes to the webservers of ULYSSIS in the summer of 2020, and how you can prepare for it. If any of these instructions are not clear to you, or if you have some more questions about the changes, '''don't hesitate to e-mail us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]'''. == When are the changes planned? == The changes will be in effect after the downtime in September when we upgrade all of our servers. The exact date has not yet been decided. We will contact our users once it has. After that, we will use the new webserver configuration. == What will change? == We will upgrade the Ubuntu release on our servers from 18.04 LTS to 20.04 LTS. This will include newer version of many services. An overview of the most important version changes can be found below. For other services/packages, you can always use the [https://packages.ubuntu.com/ Ubuntu Package Search]. The distribution name for Ubuntu 20.04 LTS is "focal". * PHP will be updated from 7.2 to 7.4 * PostgreSQL will be updated from 10 to 12 * MariaDB (MySQL) will be updated from 10.1.44 to 10.3.22 * Python will be updated from 3.6 to 3.8 Note that any existing Python virtual environments in use will need to be recreated in order to function properly. Additionally, we will make use of the maintenance window to change certain aspects of our services. Notably, we will no longer support the user of <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> files. Instead, users are advised to use <code>.user.ini</code> files. More details regarding the changes can be found on the remainder of this page. === Support for <code>php_flag</code> and <code>php_value</code> === {{info|Want to make sure you haven't missed any php_flag or php_value in your .htaccess files? You can find an easy tool to check [https://docs.ulyssis.org/summer2020tool/ here]}} Support for <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> as described in older versions of [[Special:PermanentLink/714|Managing PHP errors]] and [[Special:PermanentLink/715|Setting PHP options]] will no longer be supported. If you have added these options, you will have to remove them and migrate them to a <code>.user.ini</code> file. The current versions of these pages ([[Managing PHP errors]] and [[Setting PHP options]]) explain how you can do this. Note that if the options are inside a block that checks for the existence of a specific version of <code>mod_php</code>, then this will not cause an error. This is the case for many CMSs. === Basic Auth in PHP and FCGI scripts === When using Basic authentication on a PHP or FCGI script, it was necessary to apply a [[Basic authentication|workaround]]. This will no longer be needed in the future as the Authorization header will be passed by default to the script. This behavior can be disabled using the CGIPassAuth directive. For more details see https://httpd.apache.org/docs/current/en/mod/core.html#cgipassauth . === Client IP address === Currently, the [[Getting Apache logs|Apache logs]] only show the proper client IP when unencrypted traffic is used (no HTTPS). When using HTTPS, the client IP is logged as 193.190.253.234, the IP address of our loadbalancer. During the maintenance, we will make the required changes to ensure that the logged IP address will be the client's IP address, even if HTTPS is used. Additionally, this will improve the effectiveness of the brute-force detection in place on our webservers for WordPress installations. For more information, see [[ULYSSIS security measures#CMSs and other popular software|ULYSSIS security measures]]. 86eb80d5e5eff33dc20dd7b36d71237e9a504241 1112 1110 2020-07-20T03:15:17Z Bert 8 /* Support for php_flag and php_value */ wikitext text/x-wiki This page lists the changes to the webservers of ULYSSIS in the summer of 2020, and how you can prepare for it. If any of these instructions are not clear to you, or if you have some more questions about the changes, '''don't hesitate to e-mail us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]'''. == When are the changes planned? == The changes will be in effect after the downtime in September when we upgrade all of our servers. The exact date has not yet been decided. We will contact our users once it has. After that, we will use the new webserver configuration. == What will change? == We will upgrade the Ubuntu release on our servers from 18.04 LTS to 20.04 LTS. This will include newer version of many services. An overview of the most important version changes can be found below. For other services/packages, you can always use the [https://packages.ubuntu.com/ Ubuntu Package Search]. The distribution name for Ubuntu 20.04 LTS is "focal". * PHP will be updated from 7.2 to 7.4 * PostgreSQL will be updated from 10 to 12 * MariaDB (MySQL) will be updated from 10.1.44 to 10.3.22 * Python will be updated from 3.6 to 3.8 Note that any existing Python virtual environments in use will need to be recreated in order to function properly. Additionally, we will make use of the maintenance window to change certain aspects of our services. Notably, we will no longer support the user of <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> files. Instead, users are advised to use <code>.user.ini</code> files. More details regarding the changes can be found on the remainder of this page. === Support for <code>php_flag</code> and <code>php_value</code> === {{info|To help users trying to find out if their accounts still contain problematic cases of php_flag and php_value, we've introduced a [https://docs.ulyssis.org/summer2020tool/ simple tool] that tries to automatically check all .htaccess files that are in use.}} Support for <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> as described in older versions of [[Special:PermanentLink/714|Managing PHP errors]] and [[Special:PermanentLink/715|Setting PHP options]] will no longer be supported. If you have added these options, you will have to remove them and migrate them to a <code>.user.ini</code> file. The current versions of these pages ([[Managing PHP errors]] and [[Setting PHP options]]) explain how you can do this. Note that if the options are inside a block that checks for the existence of a specific version of <code>mod_php</code>, then this will not cause an error. This is the case for many CMSs. === Basic Auth in PHP and FCGI scripts === When using Basic authentication on a PHP or FCGI script, it was necessary to apply a [[Basic authentication|workaround]]. This will no longer be needed in the future as the Authorization header will be passed by default to the script. This behavior can be disabled using the CGIPassAuth directive. For more details see https://httpd.apache.org/docs/current/en/mod/core.html#cgipassauth . === Client IP address === Currently, the [[Getting Apache logs|Apache logs]] only show the proper client IP when unencrypted traffic is used (no HTTPS). When using HTTPS, the client IP is logged as 193.190.253.234, the IP address of our loadbalancer. During the maintenance, we will make the required changes to ensure that the logged IP address will be the client's IP address, even if HTTPS is used. Additionally, this will improve the effectiveness of the brute-force detection in place on our webservers for WordPress installations. For more information, see [[ULYSSIS security measures#CMSs and other popular software|ULYSSIS security measures]]. d5d5f2194a0008ae18326c53fb076a0e15e93fdf 0 8 1095 714 2020-07-08T20:05:21Z Vincenttc 21 wikitext text/x-wiki PHP errors are not displayed by default. If an error occurs, you will simply get a blank page. This is for security reasons: this way, an attacker doesn't know about possible vulnerabilities of your website. If you want to see PHP errors, you can log them to a file, or enable the display of errors. = Logging errors to a file = If your username is ''foobar'', create a <code>.user.ini</code> file (for example: <code>~/www/.user.ini</code>) with this content, if you are a regular user: log_errors = on error_log = "/home/user/foobar/php_error.log" Or if you are an organization: log_errors = on error_log = "/home/org/foobar/php_error.log" = Displaying errors = Create a <code>.user.ini</code> file (for example: <code>~/www/.user.ini</code>) with this content: display_errors = on Note that PHP errors may include sensitive information, and enabling <code>display_errors</code> will cause that to be visible to the entire internet. It is therefore advised to only enable <code>display_errors</code> when actively troubleshooting a problem. Instead use an error log as specified above. [[Category:Webserver]] 1655a7273b9bd74d08689c2e687a10c6de3a86f4 1096 1095 2020-07-08T20:19:14Z Vincenttc 21 wikitext text/x-wiki PHP errors are not displayed by default. If an error occurs, you will simply get a blank page. This is for security reasons: this way, an attacker doesn't know about possible vulnerabilities of your website. If you want to see PHP errors, you can log them to a file, or enable the display of errors. Note that it can take up to 5 minutes for any of the options mentioned below to be detected. = Logging errors to a file = If your username is ''foobar'', create a <code>.user.ini</code> file (for example: <code>~/www/.user.ini</code>) with this content, if you are a regular user: log_errors = on error_log = "/home/user/foobar/php_error.log" Or if you are an organization: log_errors = on error_log = "/home/org/foobar/php_error.log" = Displaying errors = Create a <code>.user.ini</code> file (for example: <code>~/www/.user.ini</code>) with this content: display_errors = on Note that PHP errors may include sensitive information, and enabling <code>display_errors</code> will cause that to be visible to the entire internet. It is therefore advised to only enable <code>display_errors</code> when actively troubleshooting a problem. Instead use an error log as specified above. [[Category:Webserver]] 0ad7640595ae84705de198971e9cd09c8b9fed5b 1102 1096 2020-07-08T23:05:38Z Bert 8 wikitext text/x-wiki PHP errors are not displayed by default. If an error occurs, you will simply get a blank page. This is for security reasons: this way, an attacker doesn't know about possible vulnerabilities of your website. If you want to see PHP errors, you can log them to a file, or enable the display of errors. Note that it can take up to 5 minutes for any of the options mentioned below to be detected. == Logging errors to a file == If your username is ''foobar'', create a <code>.user.ini</code> file (for example: <code>~/www/.user.ini</code>) with this content, if you are a regular user: log_errors = on error_log = "/home/user/foobar/php_error.log" Or if you are an organization: log_errors = on error_log = "/home/org/foobar/php_error.log" == Displaying errors == Create a <code>.user.ini</code> file (for example: <code>~/www/.user.ini</code>) with this content: display_errors = on Note that PHP errors may include sensitive information, and enabling <code>display_errors</code> will cause that to be visible to the entire internet. It is therefore advised to only enable <code>display_errors</code> when actively troubleshooting a problem. Instead use an error log as specified above. [[Category:Webserver]] 30326a32c05f43a57d7b44f979e7cb21f1a94b4d 0 32 1097 715 2020-07-08T20:30:41Z Vincenttc 21 wikitext text/x-wiki You can set PHP options you would normally set in <code>php.ini</code> in <code>.user.ini</code>, . For example, to increase the maximum filesize of uploads, create a <code>.user.ini</code> file (for example: <code>~/www/.user.ini</code>) upload_max_filesize = 20M post_max_size = 25M ; post_max_size needs to be larger than upload_max_size It is also possible to use the [http://be2.php.net/manual/en/function.ini-set.php ini_set] function, however this does not support all options. [[Category:Webserver]] cd5767384cb57cd13e56e26c1d15583fc739e850 1098 1097 2020-07-08T20:30:54Z Vincenttc 21 wikitext text/x-wiki You can set PHP options you would normally set in <code>php.ini</code> in <code>.user.ini</code>. For example, to increase the maximum filesize of uploads, create a <code>.user.ini</code> file (for example: <code>~/www/.user.ini</code>) upload_max_filesize = 20M post_max_size = 25M ; post_max_size needs to be larger than upload_max_size It is also possible to use the [http://be2.php.net/manual/en/function.ini-set.php ini_set] function, however this does not support all options. [[Category:Webserver]] 1e1c35851f19b1c56ed40ec5098fa1c6b4d6cf09 0 33 1106 971 2020-07-13T23:04:48Z Bert 8 /* Deploying Shibboleth */ wikitext text/x-wiki Shibboleth is the software powering the Central KU Leuven Login. It's a piece of software used by many universities to supply identification and access management. ULYSSIS works together with ICTS to supply limited access to Shibboleth. We are however only able to supply Shibboleth to those approved by ICTS. In practice all faculty unions will be granted access if they can prove they have the technical ability to use Shibboleth in a safe and privacy friendly way. For other organisations it can be more difficult to get access, therefore it is best to write an extensive explenation of what you plan to do with Shibboleth, why your organisation requires it, what your organisation does, and other relevant information. We will then contact ICTS with your request. == How to request == To request Shibboleth access, you first need to make sure the domain you wish to use Shibboleth on has valid SSL certificates. Lately ICTS has been pushing that all traffic to the website is already over HTTPS before Shibboleth is issued. For more info you can check [[Getting SSL]] If you have SSL set up you need to send an email to request Shibboleth to ulyssis@ulyssis.org. The email must contain the following info: * What domain you wish to use Shibboleth on (this must be a single domain, so keep subdomains and www in mind) * What you will be using Shibboleth for and in general what your application will do. This explanation is required by ICTS. If you fail to convince them they will not grant your domain access. * What attributes you wish to use and what you will do with them (and whether you will store them). You can find the list of attributes on https://admin.kuleuven.be/icts/services/aai/attributes * Explicitly state you grant ULYSSIS permission to edit the .htaccess file to be able to export the required Shibboleth Metadata * If you are not a recognised faculty union you will need to include an extra motivation why you require Shibboleth (as noted above) If your application is complete and correct we will file a formal request. We will of course notify you of ICTS' response. == Deploying Shibboleth == After you have been granted access you can soon start using Shibboleth. The first step is to add the following lines to your .htaccess ShibDisable Off AuthType Shibboleth require shibboleth ShibRequireSession off We disable certain features of Shibboleth here because it will otherwise interfere with any other HTTP-auth options you might be using. Now that you have added this information to .htaccess you are able to serve requests to Shibboleth.sso, if your request is well-formed the sso will handle communication with the IdP (identity provider) of the KU Leuven. A login link follows the following syntax: https://[YOUR_HOSTNAME]/Shibboleth.sso/WAYF/kuleuven?target=[URLENCODED_RETURN_URL] And logout links: https://[YOUR_HOSTNAME]/Shibboleth.sso/Logout?return=[URLENCODED_DISPLAY_URL] It is important to note that on logout the user will stay on the KU Leuven's IdP-page and your link will only be displayed. The user will NOT be redirected (even though this is the normale behaviour according to the Shibboleth documentation). As soon as a user is logged in, their attributes will be available to your application. Attributes are certain properties that an account may have and that supply further information about them. Some examples are: first name, last name, mail, student id. All of these will be available as environment variables. In PHP these are part of $_SERVER. Keep in mind that Apache might prefix the names of these variables with REDIRECT_ multiple times (for example when mod_rewrite is used). For an overview of all attributes you can check out http://shib.kuleuven.be/secure/allAttributes More general information on the KU Leuvens implementation can be found on http://shib.kuleuven.be/. [[Category:Webserver]] 2da6438593c54a726d7dd4a8daff8a20e2e06683 10 146 1107 2020-07-19T20:38:50Z Bert 8 Created page with "<div style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #c0dcf4; border: 1px solid #9eb6d4;"> <p style="margin-bottom: 0;">{{{1}}}</p> </div>..." wikitext text/x-wiki <div style="background: transparent; margin-top:0.5em;padding:0.5em;background-color: #c0dcf4; border: 1px solid #9eb6d4;"> <p style="margin-bottom: 0;">{{{1}}}</p> </div> <noinclude> == Usage == <nowiki>{{info|This is a general info box, stands out more than the default grey code box}}</nowiki> {{info|This is a general info box, stands out more than the default grey code box}} e7fe10d19e07f7ecc0bd48d0caf0c0d81a4ecca9 1111 1107 2020-07-19T21:12:05Z Bert 8 wikitext text/x-wiki <div style="background: transparent; margin-top:0.5em;padding:1em;background-color: #c0dcf4; border: 1px solid #9eb6d4;"> <p style="margin-bottom: 0;">{{{1}}}</p> </div> <noinclude> == Usage == <nowiki>{{info|This is a general info box, stands out more than the default grey code box}}</nowiki> {{info|This is a general info box, stands out more than the default grey code box}} 59d725af4c103fb2668e892c29e635c68dfa210c 0 7 1113 762 2020-07-28T00:35:46Z Pcy 37 wikitext text/x-wiki ULYSSIS hosts its own IRC network. IRC stands for Internet Relay Chat, [https://en.wikipedia.org/wiki/Internet_Relay_Chat IRC on wikipedia]. It is a chat protocol that mainly focuses on group chat, but also allows for private chat. If you have an urgent question, IRC is often the quickest way to contact us. But also if you don't have a question and just want to hang out in our chat, feel free to join! ==Web IRC client== If you won't regularly use our IRC or if you just want to check it out, you can use our web IRC client. You can find it at [https://webirc.ulyssis.org/ webirc.ulyssis.org]. ==IRC network details== Below are specific instructions for some clients, but if you are already familiar with IRC, here are the details you need to connect to our server. We highly recommend using SSL. Server: irc.ulyssis.org Port: 6668 (SSL) Channel: #ulyssis If <code>irc.ulyssis.org</code> is down, you can also try the other server in the same network, hosted at <code>irc2.ulyssis.org</code>. Both are connected to each other and you can use them interchangeably. It is advised to add it as a fallback in your IRC client. ==IRC clients== To use IRC, you'll need an IRC client. We advise the terminal based [https://irssi.org/ irssi] or [https://weechat.org/ weechat] for Linux and [https://hexchat.github.io/ hexchat] or [https://www.mirc.com/ mIRC] for Windows, but there are a lot of other free options. You can only receive messages over IRC while you're connected. Therefore, we advise you to run irssi or weechat in either a screen or a tmux session. With a ULYSSIS account, you can run screen or tmux on our shellservers, as they keep running 24/7 you can use them to keep track of your conversations. Screen and tmux are similar programs. Screen has been around for longer and is more tested, while tmux is more modern with new features and being easier to use for beginners. ===Using irssi on our shell servers=== ====Connect to the shellserver==== Use the ssh command in your Linux or OS X terminal, or use PuTTY to connect on windows. Extensive information on how to do so can be found on [[Accessing shell servers over SSH]]. ====Start irssi in a screen==== *When on the shellserver, enter <code>screen -U</code> to start a screen session, or <code>tmux</code> to start a tmux session. *Enter <code>irssi</code> to start irssi *Connect to the IRC server: <code>/server -ssl irc.ulyssis.org 6668</code> *Connect to the public channel: <code>/join #ulyssis</code> ====Screen usage==== *To exit the screen: press Ctrl-A and press D ('detach') to return to the shellserver. *To reconnect: enter <code>screen -r</code> or <code>screen -DR</code> (the latter will create a new screen if it wasn't already made). ====Tmux usage==== *To exit the tmux session: press Ctrl-B and press D ('detach') to return to the shellserver. *To reconnect: enter <code>tmux attach</code> ====Help, I can't reconnect to my session!==== *Check if you are on the right shell server and didn't make a typing error. *If everything is correct, your screen may have been stopped by a crash or a reboot of our shellserver. You can check the [http://www.ulyssis.org/status status] section of our website for more information about possible downtimes. *Make sure you use the right program (<code>screen</code> if you started a screen session and <code>tmux</code> if you started a tmux session) ==Using ZNC== Alternatively, if you don't like using terminal-based clients, or just want to run your client locally, you can connect with our [https://znc.ulyssis.org/ ZNC server]. However, to use it, you'll need a ULYSSIS account. ZNC connects to our IRC server in your place (fill in the details at the beginning of this article). You can then connect to ZNC with a client of your choice, and it will send you the history you've missed while you were offline. Log in to our ZNC server. In your settings, create a new network. Fill in the basic details (server name, nickname, set <code>BindHost</code> to <code>0.0.0.0</code>). In the server field, fill in <code>irc.ulyssis.org +6668</code>. Add <code>#ulyssis</code> as a channel. You may want to increase the buffer count. Then save at the bottom of the page. In your IRC client, connect to the server <code>znc.ulyssis.org</code> on port 6666 (with SSL) and set <code>username/network:password</code> as password to the server. Replace <code>username</code> with your ULYSSIS username, <code>network</code> with the name of the network in your znc settings, and <code>password</code> with your ULYSSIS password. ==Using Bitlbee== With [https://www.bitlbee.org/main.php/news.r.html Bitlbee], you can connect to other services as if they were an IRC server. It is available at <code>irc.ulyssis.org</code> on ports 7000 and 7001 (SSL). For documentation on how to use Bitlbee, we refer to the manual on its website. [[Category:Shell]] [[Category:ULYSSIS Public Services]] a230755c4d56703995027875813f81991e113020 1114 1113 2020-07-28T00:46:09Z Pcy 37 /* Using Bitlbee */ wikitext text/x-wiki ULYSSIS hosts its own IRC network. IRC stands for Internet Relay Chat, [https://en.wikipedia.org/wiki/Internet_Relay_Chat IRC on wikipedia]. It is a chat protocol that mainly focuses on group chat, but also allows for private chat. If you have an urgent question, IRC is often the quickest way to contact us. But also if you don't have a question and just want to hang out in our chat, feel free to join! ==Web IRC client== If you won't regularly use our IRC or if you just want to check it out, you can use our web IRC client. You can find it at [https://webirc.ulyssis.org/ webirc.ulyssis.org]. ==IRC network details== Below are specific instructions for some clients, but if you are already familiar with IRC, here are the details you need to connect to our server. We highly recommend using SSL. Server: irc.ulyssis.org Port: 6668 (SSL) Channel: #ulyssis If <code>irc.ulyssis.org</code> is down, you can also try the other server in the same network, hosted at <code>irc2.ulyssis.org</code>. Both are connected to each other and you can use them interchangeably. It is advised to add it as a fallback in your IRC client. ==IRC clients== To use IRC, you'll need an IRC client. We advise the terminal based [https://irssi.org/ irssi] or [https://weechat.org/ weechat] for Linux and [https://hexchat.github.io/ hexchat] or [https://www.mirc.com/ mIRC] for Windows, but there are a lot of other free options. You can only receive messages over IRC while you're connected. Therefore, we advise you to run irssi or weechat in either a screen or a tmux session. With a ULYSSIS account, you can run screen or tmux on our shellservers, as they keep running 24/7 you can use them to keep track of your conversations. Screen and tmux are similar programs. Screen has been around for longer and is more tested, while tmux is more modern with new features and being easier to use for beginners. ===Using irssi on our shell servers=== ====Connect to the shellserver==== Use the ssh command in your Linux or OS X terminal, or use PuTTY to connect on windows. Extensive information on how to do so can be found on [[Accessing shell servers over SSH]]. ====Start irssi in a screen==== *When on the shellserver, enter <code>screen -U</code> to start a screen session, or <code>tmux</code> to start a tmux session. *Enter <code>irssi</code> to start irssi *Connect to the IRC server: <code>/server -ssl irc.ulyssis.org 6668</code> *Connect to the public channel: <code>/join #ulyssis</code> ====Screen usage==== *To exit the screen: press Ctrl-A and press D ('detach') to return to the shellserver. *To reconnect: enter <code>screen -r</code> or <code>screen -DR</code> (the latter will create a new screen if it wasn't already made). ====Tmux usage==== *To exit the tmux session: press Ctrl-B and press D ('detach') to return to the shellserver. *To reconnect: enter <code>tmux attach</code> ====Help, I can't reconnect to my session!==== *Check if you are on the right shell server and didn't make a typing error. *If everything is correct, your screen may have been stopped by a crash or a reboot of our shellserver. You can check the [http://www.ulyssis.org/status status] section of our website for more information about possible downtimes. *Make sure you use the right program (<code>screen</code> if you started a screen session and <code>tmux</code> if you started a tmux session) ==Using ZNC== Alternatively, if you don't like using terminal-based clients, or just want to run your client locally, you can connect with our [https://znc.ulyssis.org/ ZNC server]. However, to use it, you'll need a ULYSSIS account. ZNC connects to our IRC server in your place (fill in the details at the beginning of this article). You can then connect to ZNC with a client of your choice, and it will send you the history you've missed while you were offline. Log in to our ZNC server. In your settings, create a new network. Fill in the basic details (server name, nickname, set <code>BindHost</code> to <code>0.0.0.0</code>). In the server field, fill in <code>irc.ulyssis.org +6668</code>. Add <code>#ulyssis</code> as a channel. You may want to increase the buffer count. Then save at the bottom of the page. In your IRC client, connect to the server <code>znc.ulyssis.org</code> on port 6666 (with SSL) and set <code>username/network:password</code> as password to the server. Replace <code>username</code> with your ULYSSIS username, <code>network</code> with the name of the network in your znc settings, and <code>password</code> with your ULYSSIS password. ==Using Bitlbee== With [https://www.bitlbee.org/main.php/news.r.html Bitlbee], you can connect to other services as if they were an IRC server. It is available at <code>irc.ulyssis.org</code> on ports 7000 and 7001 (SSL). For documentation on how to use Bitlbee, we refer to the manual on its website. This service is only reachable from within the ULYSSIS and KU Leuven networks. [[Category:Shell]] [[Category:ULYSSIS Public Services]] 41dc65209e6bbc7c855950f8ae88a5103c08fcfc 1115 1114 2020-07-28T00:54:04Z Pcy 37 /* Using Bitlbee */ wikitext text/x-wiki ULYSSIS hosts its own IRC network. IRC stands for Internet Relay Chat, [https://en.wikipedia.org/wiki/Internet_Relay_Chat IRC on wikipedia]. It is a chat protocol that mainly focuses on group chat, but also allows for private chat. If you have an urgent question, IRC is often the quickest way to contact us. But also if you don't have a question and just want to hang out in our chat, feel free to join! ==Web IRC client== If you won't regularly use our IRC or if you just want to check it out, you can use our web IRC client. You can find it at [https://webirc.ulyssis.org/ webirc.ulyssis.org]. ==IRC network details== Below are specific instructions for some clients, but if you are already familiar with IRC, here are the details you need to connect to our server. We highly recommend using SSL. Server: irc.ulyssis.org Port: 6668 (SSL) Channel: #ulyssis If <code>irc.ulyssis.org</code> is down, you can also try the other server in the same network, hosted at <code>irc2.ulyssis.org</code>. Both are connected to each other and you can use them interchangeably. It is advised to add it as a fallback in your IRC client. ==IRC clients== To use IRC, you'll need an IRC client. We advise the terminal based [https://irssi.org/ irssi] or [https://weechat.org/ weechat] for Linux and [https://hexchat.github.io/ hexchat] or [https://www.mirc.com/ mIRC] for Windows, but there are a lot of other free options. You can only receive messages over IRC while you're connected. Therefore, we advise you to run irssi or weechat in either a screen or a tmux session. With a ULYSSIS account, you can run screen or tmux on our shellservers, as they keep running 24/7 you can use them to keep track of your conversations. Screen and tmux are similar programs. Screen has been around for longer and is more tested, while tmux is more modern with new features and being easier to use for beginners. ===Using irssi on our shell servers=== ====Connect to the shellserver==== Use the ssh command in your Linux or OS X terminal, or use PuTTY to connect on windows. Extensive information on how to do so can be found on [[Accessing shell servers over SSH]]. ====Start irssi in a screen==== *When on the shellserver, enter <code>screen -U</code> to start a screen session, or <code>tmux</code> to start a tmux session. *Enter <code>irssi</code> to start irssi *Connect to the IRC server: <code>/server -ssl irc.ulyssis.org 6668</code> *Connect to the public channel: <code>/join #ulyssis</code> ====Screen usage==== *To exit the screen: press Ctrl-A and press D ('detach') to return to the shellserver. *To reconnect: enter <code>screen -r</code> or <code>screen -DR</code> (the latter will create a new screen if it wasn't already made). ====Tmux usage==== *To exit the tmux session: press Ctrl-B and press D ('detach') to return to the shellserver. *To reconnect: enter <code>tmux attach</code> ====Help, I can't reconnect to my session!==== *Check if you are on the right shell server and didn't make a typing error. *If everything is correct, your screen may have been stopped by a crash or a reboot of our shellserver. You can check the [http://www.ulyssis.org/status status] section of our website for more information about possible downtimes. *Make sure you use the right program (<code>screen</code> if you started a screen session and <code>tmux</code> if you started a tmux session) ==Using ZNC== Alternatively, if you don't like using terminal-based clients, or just want to run your client locally, you can connect with our [https://znc.ulyssis.org/ ZNC server]. However, to use it, you'll need a ULYSSIS account. ZNC connects to our IRC server in your place (fill in the details at the beginning of this article). You can then connect to ZNC with a client of your choice, and it will send you the history you've missed while you were offline. Log in to our ZNC server. In your settings, create a new network. Fill in the basic details (server name, nickname, set <code>BindHost</code> to <code>0.0.0.0</code>). In the server field, fill in <code>irc.ulyssis.org +6668</code>. Add <code>#ulyssis</code> as a channel. You may want to increase the buffer count. Then save at the bottom of the page. In your IRC client, connect to the server <code>znc.ulyssis.org</code> on port 6666 (with SSL) and set <code>username/network:password</code> as password to the server. Replace <code>username</code> with your ULYSSIS username, <code>network</code> with the name of the network in your znc settings, and <code>password</code> with your ULYSSIS password. ==Using Bitlbee== With [https://www.bitlbee.org/main.php/news.r.html Bitlbee], you can connect to other services as if they were an IRC server. It is available at <code>bitlbee.ulyssis.org</code> on ports 7000 and 7001 (SSL). For documentation on how to use Bitlbee, we refer to the manual on its website. This service is only reachable from within the ULYSSIS and KU Leuven networks. [[Category:Shell]] [[Category:ULYSSIS Public Services]] 9b16352f8cd1e9613376aa489267566d3df30155 0 3 1116 1062 2020-07-29T14:43:00Z Vincenttc 21 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] * [[Secure file permissions]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2020]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Sending email from websites]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL/TLS|Getting SSL/TLS (HTTPS security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Basic authentication|Basic authentication in PHP]] * [[Claiming a port]] * [[ULYSSIS security measures]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] * [[Spam]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up WordPress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] * [[Using PHPPgAdmin]] * [[Using Adminer]] * [[Making Backups]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ afb1af13e2cddde6cd1aa5620fbe8f90f6ed8053 1128 1116 2020-09-17T12:45:31Z Vincenttc 21 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] * [[Secure file permissions]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2020]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Sending email from websites]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL/TLS|Getting SSL/TLS (HTTPS security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Claiming a port]] * [[ULYSSIS security measures]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] * [[Spam]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up WordPress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] * [[Using PHPPgAdmin]] * [[Using Adminer]] * [[Making Backups]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[Subversion]] * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 0ad1266a8a70367fe45c553edb4aaf8a1f9213c6 0 55 1117 871 2020-07-31T14:27:41Z Bert 8 wikitext text/x-wiki == Restricting comments == By default, WordPress allows anyone to comment freely on any post you make on your website. While this makes sense when you maintain a blog, it makes less sense when you're using WordPress as the basis for your student organization's website or for something with little to no reader interaction. We therefore advise those with a WordPress installation to consider restricting comments by following these instructions: * Navigate to the Wordpress admin dashboard and login * Go to Settings and then Discussion * In almost all cases, you will want to disable link notifications, pingbacks and trackbacks, as these are almost exclusively used for spam nowadays * Consider disabling comments all together as well ** If you wish to enable some form of comments, consider restricting to logged in users, or require your approval. You may in that case also want to automate spam detection (see below) * It's possible in WordPress to disable comments as a general setting, but still have it enabled on individual posts or pages. Make sure to delete the default test post and page, as well as to look at the discussion setting on every existing post and page. If you can't find this setting, it may be hidden, but available under the "Screen Options" button at the top of the page. == Detecting spam == As mentioned above, it's better in most cases to simply not allow comments or to restrict them very heavily than having to deal with spam. If you have no other choice, there are some options available to help you out. It's important to keep in mind that both options below rely on external service providers for some aspects of their spam detection. === Akismet === Akismet is a plugin by the main company behind WordPress, Automattic. The plugin sends every comment that is posted to an Akismet server, which uses pattern matching, URL detection and other techniques to evaluate whether it's spam or not. Because of its focus on WordPress comments, it is very accurate and can also block spam that was composed and posted by an actual human, as opposed to CAPTCHA which aims to block automated posting only. Keep in mind that Akismet is only free for non-commercial purposes. To use Akismet follow these instructions: * Navigate to the Wordpress admin dashboard and login * Go to Plugins and select Add New * If Akismet Anti-Spam isn't already on the "Featured" page, then search for "akismet" * Install and activate the plugin * You will then be redirected to a settings page, where you can setup an Akismet account and configure your settings. === Google's reCAPTCHA === CAPTCHA, originally from a complicated acronym, is a term used for different kinds of challenges to prevent automated scripts from trying to comment, register or login on websites. reCAPTCHA is a project owned by google that is quite successful at designing these challenges. You probably know reCAPTCHA as the "I'm not a robot" checkbox you often have to press. More details are available on https://google.com/recaptcha There are several different plugins that make it possible to add reCAPTCHA to WordPress. You can follow these instructions to get started: * Navigate to the Wordpress admin dashboard and login * Go to Plugins and select Add New * Search for "recaptcha" * Many of the plugins you will get are well-suited for this task. At the time of writing, ULYSSIS has been using "ReCaptcha Integration for WordPress" for a while. There is however no reason why other plugins won't be suitable. * Install and activate the plugin of your choice * You will then usually be redirected to a settings page, where you will need to enter the keys to use reCAPTCHA. You can register these on https://www.google.com/recaptcha/admin * Make sure to also check other configuration options, not all plugins will necessarily protect comment forms by default * Usually, you can find settings for your different plugins under the settings menu, if you wish to make changes in the future [[Category:Security & anti-spam]] 578365c3b42de405512243ebc34dcd64619ac2b7 1118 1117 2020-07-31T14:48:20Z Yoa 30 /* Restricting comments */ wikitext text/x-wiki == Restricting comments == By default, WordPress allows anyone to comment freely on any post you make on your website. While this makes sense when you maintain a blog, it makes less sense when you're using WordPress as the basis for your student organization's website or for something with little to no reader interaction. We therefore advise those with a WordPress installation to consider restricting comments by following these instructions: * Navigate to the WordPress admin dashboard and login * Go to Settings and then Discussion * In almost all cases, you will want to disable link notifications, pingbacks and trackbacks, as these are almost exclusively used for spam nowadays * Consider disabling comments altogether as well ** If you wish to enable some form of comments, consider restricting to logged in users, or require your approval. You may in that case also want to automate spam detection (see below). * It's possible in WordPress to disable comments as a general setting, but still have it enabled on individual posts or pages. Make sure to delete the default test post and page, as well as to look at the discussion setting on every existing post and page. If you can't find this setting, it may be hidden, but available under the "Screen Options" button at the top of the page. == Detecting spam == As mentioned above, it's better in most cases to simply not allow comments or to restrict them very heavily than having to deal with spam. If you have no other choice, there are some options available to help you out. It's important to keep in mind that both options below rely on external service providers for some aspects of their spam detection. === Akismet === Akismet is a plugin by the main company behind WordPress, Automattic. The plugin sends every comment that is posted to an Akismet server, which uses pattern matching, URL detection and other techniques to evaluate whether it's spam or not. Because of its focus on WordPress comments, it is very accurate and can also block spam that was composed and posted by an actual human, as opposed to CAPTCHA which aims to block automated posting only. Keep in mind that Akismet is only free for non-commercial purposes. To use Akismet follow these instructions: * Navigate to the Wordpress admin dashboard and login * Go to Plugins and select Add New * If Akismet Anti-Spam isn't already on the "Featured" page, then search for "akismet" * Install and activate the plugin * You will then be redirected to a settings page, where you can setup an Akismet account and configure your settings. === Google's reCAPTCHA === CAPTCHA, originally from a complicated acronym, is a term used for different kinds of challenges to prevent automated scripts from trying to comment, register or login on websites. reCAPTCHA is a project owned by google that is quite successful at designing these challenges. You probably know reCAPTCHA as the "I'm not a robot" checkbox you often have to press. More details are available on https://google.com/recaptcha There are several different plugins that make it possible to add reCAPTCHA to WordPress. You can follow these instructions to get started: * Navigate to the Wordpress admin dashboard and login * Go to Plugins and select Add New * Search for "recaptcha" * Many of the plugins you will get are well-suited for this task. At the time of writing, ULYSSIS has been using "ReCaptcha Integration for WordPress" for a while. There is however no reason why other plugins won't be suitable. * Install and activate the plugin of your choice * You will then usually be redirected to a settings page, where you will need to enter the keys to use reCAPTCHA. You can register these on https://www.google.com/recaptcha/admin * Make sure to also check other configuration options, not all plugins will necessarily protect comment forms by default * Usually, you can find settings for your different plugins under the settings menu, if you wish to make changes in the future [[Category:Security & anti-spam]] 1bd5b4c967a170653be4e7b0a5a73b0214e6280a 1119 1118 2020-07-31T14:51:08Z Yoa 30 /* Google's reCAPTCHA */ wikitext text/x-wiki == Restricting comments == By default, WordPress allows anyone to comment freely on any post you make on your website. While this makes sense when you maintain a blog, it makes less sense when you're using WordPress as the basis for your student organization's website or for something with little to no reader interaction. We therefore advise those with a WordPress installation to consider restricting comments by following these instructions: * Navigate to the WordPress admin dashboard and login * Go to Settings and then Discussion * In almost all cases, you will want to disable link notifications, pingbacks and trackbacks, as these are almost exclusively used for spam nowadays * Consider disabling comments altogether as well ** If you wish to enable some form of comments, consider restricting to logged in users, or require your approval. You may in that case also want to automate spam detection (see below). * It's possible in WordPress to disable comments as a general setting, but still have it enabled on individual posts or pages. Make sure to delete the default test post and page, as well as to look at the discussion setting on every existing post and page. If you can't find this setting, it may be hidden, but available under the "Screen Options" button at the top of the page. == Detecting spam == As mentioned above, it's better in most cases to simply not allow comments or to restrict them very heavily than having to deal with spam. If you have no other choice, there are some options available to help you out. It's important to keep in mind that both options below rely on external service providers for some aspects of their spam detection. === Akismet === Akismet is a plugin by the main company behind WordPress, Automattic. The plugin sends every comment that is posted to an Akismet server, which uses pattern matching, URL detection and other techniques to evaluate whether it's spam or not. Because of its focus on WordPress comments, it is very accurate and can also block spam that was composed and posted by an actual human, as opposed to CAPTCHA which aims to block automated posting only. Keep in mind that Akismet is only free for non-commercial purposes. To use Akismet follow these instructions: * Navigate to the Wordpress admin dashboard and login * Go to Plugins and select Add New * If Akismet Anti-Spam isn't already on the "Featured" page, then search for "akismet" * Install and activate the plugin * You will then be redirected to a settings page, where you can setup an Akismet account and configure your settings. === Google's reCAPTCHA === CAPTCHA, originally from a complicated acronym, is a term used for different kinds of challenges to prevent automated scripts from trying to comment, register or login on websites. reCAPTCHA is a project owned by Google that is quite successful at designing these challenges. You probably know reCAPTCHA as the "I'm not a robot" checkbox you often have to press. More details are available on https://google.com/recaptcha There are several different plugins that make it possible to add reCAPTCHA to WordPress. You can follow these instructions to get started: * Navigate to the WordPress admin dashboard and login * Go to Plugins and select Add New * Search for "recaptcha" * Many of the plugins you will get are well-suited for this task. At the time of writing, ULYSSIS has been using "ReCaptcha Integration for WordPress" for a while. There is however no reason why other plugins won't be suitable. * Install and activate the plugin of your choice * You will then usually be redirected to a settings page, where you will need to enter the keys to use reCAPTCHA. You can register these on https://www.google.com/recaptcha/admin * Make sure to also check other configuration options, not all plugins will necessarily protect comment forms by default * Usually, you can find settings for your different plugins under the settings menu, if you wish to make changes in the future [[Category:Security & anti-spam]] 7e85994a4c418e9e726efa1e5f4ff029e6199b05 0 98 1120 783 2020-08-11T15:12:53Z Vincenttc 21 /* MWSAllowedDegrees */ wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for login through the Central KU Leuven Login (Shibboleth). The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Central KU Leuven Login) enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest/download/MediaWikiShibboleth.zip github]. Unzip the zip file in the <code>extensions/</code> directory in your MediaWiki installation folder. Make sure there is now a <code>MediaWikiShibboleth</code> folder in <code>extensions/</code>. Finally, locate the <code>LocalSettings.php</code> file in your MediaWiki installation folder and add the following lines to it: wfLoadExtension('MediaWikiShibboleth'); $wgGroupPermissions['*']['createaccount'] = false; $wgRevokePermissions['Shibboleth']['editmyprivateinfo'] = true; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. This really defeats the purpose of the extension though. ==Configuration== MediaWikiShibboleth has some configuration options which allow for restricting who can log in to your wiki. These restrictions are cumulative. For example, it is possible to allow only students enrolled in a specific degree or programme to log in. These options work especially well with restricting the access of the wiki to logged-in users only. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code>LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code>LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code>LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow students enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code>LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. === Translations === It's possible to translate and modify all public MediaWikiShibboleth messages. The translations can be found in the <code>extensions/MediaWikiShibboleth/i18n/</code>. Dutch (<code>nl.json</code>) and English (<code>en.json</code>) translations are already provided. Even the provided translations can be customized, and we strongly advise you to do so, in order to match them with your Wiki situation. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Login without Central KU Leuven login" to expand a login menu. The new log in page looks like this with "Login without Central KU Leuven login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] [[Category:Security & anti-spam]] 5d55f39b459df1c949f3b91272cd8df37f385de1 0 5 1121 816 2020-08-28T11:29:43Z Bert 8 wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Connecting== {{notice|Keep in mind|Our automatic security systems may temporarily prevent you from connecting over SSH/SFTP if you try to connect several times with the wrong username and/or password. This will result in the connection being refused. You can switch between sftp://ssh1.ulyssis.org and sftp://ssh2.ulyssis.org if this has happened to you or wait 10 minutes. More information on our security measures is available on [[ULYSSIS security measures]]}} ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. If your distribution does not contain an option to connect to a server, you can use [https://filezilla-project.org/ FileZilla], which is completely free. See the instructions under [[Accessing_your_files#Windows|Windows]]. [[File:UbuntuConnectToServer.png]] ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ===Mac=== ''[https://filezilla-project.org/ FileZilla], which was mentioned above, is also available for Mac. To use it, follow [[#Windows|the instructions for Windows]]. You can also opt for [http://cyberduck.io/ Cyberduck], though. In that case, follow the instructions below.'' Download the free and open source program [http://cyberduck.io/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> [[File:maccyberduck3.png]] Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. If you want to connect again later on, you can just click the Bookmarks icon on the top left. Next you click on History. And then you can double click to re-open the connection. ==Using FileZilla== When you connect to a server using FileZilla, the following layout will appear: [[File:Base_layout.png|700px|Right]] As you can see, the local files are located on the left-hand side, while the remote (server) files are located on the right-hand side. File navigation and paths are also present. [[File:Layout.png|700px|Right]] To transfer a file or folder, you can drag and drop it, either from the local side to the remote side, or from the remote side to the local side. These operations represent uploading and downloading respectively. [[File:Transfer.png|700px|Right]] You can also press enter while selecting a file, or double-click a file, to transfer it. [[File:Transfer2.png|700px|Right]] To open a folder, you can double-click it, or press enter while selecting it. [[File:Open.png|700px|Right]] You can delete files or folders by pressing the delete button while selecting them, or by right-clicking and clicking 'delete'. [[File:Delete.png|700px|Right]] To create files or folders remotely, you can right-click the remote window and click 'create directory' or 'create new file'. [[File:Create_directory.png|700px|Right]] [[File:Create_file.png|700px|Right]] As you can see, the menu has some more interesting options, for example 'rename' or 'view/edit'. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): scp file.txt username@ssh1.ulyssis.org:/home/user/username For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. [[Category:Files]] [[Category:Shell]] 76ae07af31d6c074bf019397142f04f3868ad9b4 1122 1121 2020-08-28T11:31:07Z Bert 8 wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Connecting== {{notice|Keep in mind|Our automatic security systems may temporarily prevent you from connecting over SSH/SFTP if you try to connect several times with the wrong username and/or password. This will result in the connection being refused. You can switch between sftp://ssh1.ulyssis.org and sftp://ssh2.ulyssis.org when this happens or wait 10 minutes. More information on our security measures is available on [[ULYSSIS security measures]]}} ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. If your distribution does not contain an option to connect to a server, you can use [https://filezilla-project.org/ FileZilla], which is completely free. See the instructions under [[Accessing_your_files#Windows|Windows]]. [[File:UbuntuConnectToServer.png]] ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png|Right]] ===Mac=== ''[https://filezilla-project.org/ FileZilla], which was mentioned above, is also available for Mac. To use it, follow [[#Windows|the instructions for Windows]]. You can also opt for [http://cyberduck.io/ Cyberduck], though. In that case, follow the instructions below.'' Download the free and open source program [http://cyberduck.io/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> [[File:maccyberduck3.png]] Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. If you want to connect again later on, you can just click the Bookmarks icon on the top left. Next you click on History. And then you can double click to re-open the connection. ==Using FileZilla== When you connect to a server using FileZilla, the following layout will appear: [[File:Base_layout.png|700px|Right]] As you can see, the local files are located on the left-hand side, while the remote (server) files are located on the right-hand side. File navigation and paths are also present. [[File:Layout.png|700px|Right]] To transfer a file or folder, you can drag and drop it, either from the local side to the remote side, or from the remote side to the local side. These operations represent uploading and downloading respectively. [[File:Transfer.png|700px|Right]] You can also press enter while selecting a file, or double-click a file, to transfer it. [[File:Transfer2.png|700px|Right]] To open a folder, you can double-click it, or press enter while selecting it. [[File:Open.png|700px|Right]] You can delete files or folders by pressing the delete button while selecting them, or by right-clicking and clicking 'delete'. [[File:Delete.png|700px|Right]] To create files or folders remotely, you can right-click the remote window and click 'create directory' or 'create new file'. [[File:Create_directory.png|700px|Right]] [[File:Create_file.png|700px|Right]] As you can see, the menu has some more interesting options, for example 'rename' or 'view/edit'. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): scp file.txt username@ssh1.ulyssis.org:/home/user/username For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. [[Category:Files]] [[Category:Shell]] f51cb0dcc9f64ea360632b433189b8c93607104f 0 20 1123 1020 2020-09-12T15:46:07Z Alexander 38 wikitext text/x-wiki ==How to install WordPress for your account== First you need to download WordPress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your webroot directory on our servers. Mostly this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install WordPress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there.<br> '''Warning:''' Postgresql databases are not supported by WordPress, only use MySQL databases. Now we are ready to install WordPress, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. The setup will ask you for your database configuration: *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Table Prefix:''' only change this if you have multiple installations of WordPress in your database<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]] In the next step you need to fill in your own preferences. Finally you will be prompted to log into your WordPress website. Now the installation is finished. To help you design your website, there are a few guides from WordPress that can help you: *https://wordpress.org/support/article/first-steps-with-wordpress-b/ *https://wordpress.org/support/article/using-themes/#get-new-themes *https://wordpress.org/support/article/managing-plugins/ ==Setting up multiple instances of WordPress== If you want to have multiple instances of a WordPress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular WordPress installation, i.e. the steps in the section above. You can also use WordPress' [https://wordpress.org/support/article/create-a-network/ multisite] option. If you need more help with this, you can find it [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 115e2d5bbb875f60b486bfa2e59841a8ae4ae5bf 6 148 1125 2020-09-12T16:33:21Z Alexander 38 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 149 1126 2020-09-12T16:37:17Z Alexander 38 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 78 1127 1012 2020-09-12T16:43:37Z Alexander 38 wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. = Set up agenda sync on KU Loket = ## Visit [http://kuloket.be/ KU Loket] ## Go to the '''Agenda''' tab [[File:KUL-Agenda-Step1.PNG|thumb|190px]] ## Click '''Agenda sync''' ## Click '''Configure agenda''' (''Agenda instellen'') [[File:KUL-Agenda-Step2.PNG|thumb|190px]] ## Change the switch '''Show schedule in my agenda''' (''Toon uurrooster in mijn agenda'') to '''On'''. [[File:KUL-Agenda-Step3.PNG|thumb|190px]] You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (''Agenda'') [[File:agenda4.png|thumb|190px]] # On the top right (below the menu bar), click the '''Share''' (''Delen'') button. A side-panel appears. # Enter a non-KU Leuven email address in the '''Share with''' (''Delen met'') textfield. After filling the email address, press the enter key. [[File:agenda5.png|thumb|190px]] # Make sure '''Full details''' (''Volledige informatie'') is selected in the dropdown next to your email address # Click the '''Send''' (''Verzenden'') button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> [[Category:Tutorials]] 1d8e69de1aa10ad384b2e5741be2f22de99c9b9f 1130 1127 2020-09-18T11:59:04Z Alexander 38 wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. = Set up agenda sync on KU Loket = ## Visit [http://kuloket.be/ KU Loket] ## Go to the '''Agenda''' tab [[File:KUL-Agenda-Step1.PNG|thumb|190px]] ## Click '''Agenda sync''' ## Click '''Configure agenda''' (''Agenda instellen'') [[File:KUL-Agenda-Step2.PNG|thumb|190px]] ## Change the switch '''Show schedule in my agenda''' (''Toon uurrooster in mijn agenda'') to '''On'''. [[File:KUL-Agenda-Step3.PNG|thumb|190px]] You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (''Agenda'') [[File:agenda4.png|thumb|190px]] # On the top right (below the menu bar), click the '''Share''' (''Delen'') button. A side-panel appears. # Enter a '''non-KU Leuven email address''' in the '''Share with''' (''Delen met'') textfield. After filling the email address, press the enter key. [[File:agenda5.png|thumb|190px]] # Make sure '''Full details''' (''Volledige informatie'') is selected in the dropdown next to your email address # Click the '''Send''' (''Verzenden'') button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> [[Category:Tutorials]] 7c067db740131dc4e601ea2df132abf2bc8a89a9 1131 1130 2020-09-18T12:05:58Z Alexander 38 wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. = Set up agenda sync on KU Loket = ## Visit [http://kuloket.be/ KU Loket] ## Go to the '''Agenda''' tab [[File:KUL-Agenda-Step1.PNG|thumb|190px]] ## Click '''Agenda sync''' ## Click '''Configure agenda''' (''Agenda instellen'') [[File:KUL-Agenda-Step2.PNG|thumb|190px]] ## Change the switch '''Show schedule in my agenda''' (''Toon uurrooster in mijn agenda'') to '''On'''. [[File:KUL-Agenda-Step3.PNG|thumb|190px]] You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (''Agenda'') [[File:agenda4.png|thumb|190px]] # On the top right (below the menu bar), click the '''Share''' (''Delen'') button. A side-panel appears. # Enter a '''non-KU Leuven email address''' in the '''Share with''' (''Delen met'') textfield. After filling the email address, press the enter key. [[File:agenda5.png|thumb|190px]] # Make sure '''Full details''' (''Volledige informatie'') is selected in the dropdown next to your email address # Click the '''Send''' (''Verzenden'') button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. # Normally your schedule will now be showed in your agenda. If this is not the case, go back to step 4 and click "reload schedule" (''Uurrooster herladen''). Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> [[Category:Tutorials]] 9cda4c59be386fba4664436b77c1ed5f5502480d 1132 1131 2020-09-18T12:06:21Z Alexander 38 wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. = Set up agenda sync on KU Loket = ## Visit [http://kuloket.be/ KU Loket] ## Go to the '''Agenda''' tab [[File:KUL-Agenda-Step1.PNG|thumb|190px]] ## Click '''Agenda sync''' ## Click '''Configure agenda''' (''Agenda instellen'') [[File:KUL-Agenda-Step2.PNG|thumb|190px]] ## Change the switch '''Show schedule in my agenda''' (''Toon uurrooster in mijn agenda'') to '''On'''. [[File:KUL-Agenda-Step3.PNG|thumb|190px]] You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (''Agenda'') [[File:agenda4.png|thumb|190px]] # On the top right (below the menu bar), click the '''Share''' (''Delen'') button. A side-panel appears. # Enter a '''non-KU Leuven email address''' in the '''Share with''' (''Delen met'') textfield. After filling the email address, press the enter key. [[File:agenda5.png|thumb|190px]] # Make sure '''Full details''' (''Volledige informatie'') is selected in the dropdown next to your email address # Click the '''Send''' (''Verzenden'') button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. # Normally your schedule will now be showed in your agenda. If this is not the case, go back to step 1.4 and click "reload schedule" (''Uurrooster herladen''). Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> [[Category:Tutorials]] b591be5b3062940a63a770c9449378c7b584765d 0 78 1133 1132 2020-09-18T12:08:12Z Alexander 38 wikitext text/x-wiki While relatively unknown, it is possible to create an automatically updating iCal feed of your KULoket agenda without using external services. = Set up agenda sync on KU Loket = ## Visit [http://kuloket.be/ KU Loket] ## Go to the '''Agenda''' tab [[File:KUL-Agenda-Step1.PNG|thumb|190px]] ## Click '''Agenda sync''' ## Click '''Configure agenda''' (''Agenda instellen'') [[File:KUL-Agenda-Step2.PNG|thumb|190px]] ## Change the switch '''Show schedule in my agenda''' (''Toon uurrooster in mijn agenda'') to '''On'''. [[File:KUL-Agenda-Step3.PNG|thumb|190px]] You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (''Agenda'') [[File:agenda4.png|thumb|190px]] # On the top right (below the menu bar), click the '''Share''' (''Delen'') button. A side-panel appears. # Enter a '''non-KU Leuven email address''' in the '''Share with''' (''Delen met'') textfield. After filling the email address, press the enter key. [[File:agenda5.png|thumb|190px]] # Make sure '''Full details''' (''Volledige informatie'') is selected in the dropdown next to your email address # Click the '''Send''' (''Verzenden'') button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. # Normally your schedule will now be showed in your agenda. If this is not the case, go back to step 1.4 and click '''reload schedule''' (''Uurrooster herladen''). Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> [[Category:Tutorials]] 2c4aa99fa9e518c4dc706f2a638131cab5a30823 0 36 1134 861 2020-09-23T07:05:58Z Alexander 38 wikitext text/x-wiki ULYSSIS doesn't support ftp, because it is insecure. However, we support sftp (ftp over ssh). This works similar as ssh. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Non-graphical methods== The most common way to transfer files is with a terminal by using the <code>scp</code> command. Copying file to host: scp SourceFile user@host:directory/TargetFile If you want to copy a file, you have to add -r, for example: scp -r SourceFile user@host:directory/TargetFile Copying file from host: scp user@host:directory/SourceFile TargetFile scp -r user@host:directory/SourceFolder TargetFolder You don't need to use the full path to your file. You may you the relative path, starting from your home directory. For example: scp index.html user@ssh1.ulyssis.org:www/index.html ==Graphical methods== The graphical methods are explained in [[Accessing your files]]. [[Category:Files]] [[Category:Shell]] 8ab8ccefea698d248caf886cfb496cc6164d6020 1135 1134 2020-09-23T07:11:40Z Alexander 38 wikitext text/x-wiki ULYSSIS doesn't support ftp, because it is insecure. However, we support sftp (ftp over ssh). This works similar as ssh. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Non-graphical methods== The most common way to transfer files is with a terminal by using the <code>scp</code> command. Copying file to host: scp SourceFile user@host:directory/TargetFile If you want to copy an '''empty''' file, you have to add -r, for example: scp -r SourceFile user@host:directory/TargetFile Copying file from host: scp user@host:directory/SourceFile TargetFile scp -r user@host:directory/SourceFolder TargetFolder You don't need to use the full path to your file. You may you the relative path, starting from your home directory. For example: scp index.html user@ssh1.ulyssis.org:www/index.html ==Graphical methods== The graphical methods are explained in [[Accessing your files]]. [[Category:Files]] [[Category:Shell]] 94d3ca6f372addbbe5bc40e4c5a3c69b99af0b69 1136 1135 2020-09-23T07:20:05Z Alexander 38 wikitext text/x-wiki ULYSSIS doesn't support ftp, because it is insecure. However, we support sftp (ftp over ssh). This works similar as ssh. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Non-graphical methods== The most common way to transfer files is with a terminal by using the <code>scp</code> command. Copying file to host: scp SourceFile user@host:directory/TargetFile If you want to copy an '''empty''' file, you have to add -r, for example: scp -r SourceFile user@host:directory/TargetFile Copying file from host: scp user@host:directory/SourceFile TargetFile If you want to copy an '''empty''' file, you have to add -r, for example: scp -r user@host:directory/SourceFolder TargetFolder You don't need to use the full path to your file. You may you the relative path, starting from your home directory. For example: scp index.html user@ssh1.ulyssis.org:www/index.html ==Graphical methods== The graphical methods are explained in [[Accessing your files]]. [[Category:Files]] [[Category:Shell]] e06f5dade1ee28a9cfb90fc6fe3b20bc9b05dccb 1137 1136 2020-09-23T07:21:03Z Alexander 38 wikitext text/x-wiki ULYSSIS doesn't support ftp, because it is insecure. However, we support sftp (ftp over ssh). This works similar as ssh. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Non-graphical methods== The most common way to transfer files is with a terminal by using the <code>scp</code> command. Copying file to host: scp SourceFile user@host:directory/TargetFile If you want to copy an '''empty''' folder, you have to add -r, for example: scp -r SourceFolder user@host:directory/TargetFolder Copying file from host: scp user@host:directory/SourceFile TargetFile If you want to copy an '''empty''' folder, you have to add -r, for example: scp -r user@host:directory/SourceFolder TargetFolder You don't need to use the full path to your file. You may you the relative path, starting from your home directory. For example: scp index.html user@ssh1.ulyssis.org:www/index.html ==Graphical methods== The graphical methods are explained in [[Accessing your files]]. [[Category:Files]] [[Category:Shell]] 778f700acbf2515241c1f839259b49633fe6a8fe 1138 1137 2020-09-23T07:22:38Z Alexander 38 wikitext text/x-wiki ULYSSIS doesn't support ftp, because it is insecure. However, we support sftp (ftp over ssh). This works similar as ssh. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Non-graphical methods== The most common way to transfer files is with a terminal by using the <code>scp</code> command. Copying file to host: scp SourceFile user@host:directory/TargetFile If you want to copy an '''empty''' folder, you have to add -r, for example: scp -r SourceFolder user@host:directory/TargetFolder Copying file from host: scp user@host:directory/SourceFile TargetFile If you want to copy an '''empty''' folder, you have to add -r, for example: scp -r user@host:directory/SourceFolder TargetFolder You don't need to use the full path to your file. You may you the relative path, starting from your home directory. For example: scp index.html user@ssh1.ulyssis.org:www/index.html You can find more info on the scp commands by using: man scp ==Graphical methods== The graphical methods are explained in [[Accessing your files]]. [[Category:Files]] [[Category:Shell]] daf82103b192cc4498d12bd4ec9b86d87d2cb6bb 1139 1138 2020-09-23T07:26:31Z Alexander 38 wikitext text/x-wiki ULYSSIS doesn't support ftp, because it is insecure. However, we support sftp (ftp over ssh). This works similar as ssh. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Non-graphical methods== The most common way to transfer files is with a terminal by using the <code>scp</code> command. -Copying file to host:- scp SourceFile user@host:directory/TargetFile If you want to copy an '''empty''' folder, you have to add -r, for example: scp -r SourceFolder user@host:directory/TargetFolder -Copying file from host:- scp user@host:directory/SourceFile TargetFile If you want to copy an '''empty''' folder, you have to add -r, for example: scp -r user@host:directory/SourceFolder TargetFolder You don't need to use the full path to your file. You may you the relative path, starting from your home directory. For example: scp index.html user@ssh1.ulyssis.org:www/index.html You can find more info on the scp commands by using: man scp ==Graphical methods== The graphical methods are explained in [[Accessing your files]]. [[Category:Files]] [[Category:Shell]] cc62aada3ab8925b77cda998733cca0ea95d6330 1140 1139 2020-09-23T07:26:48Z Alexander 38 wikitext text/x-wiki ULYSSIS doesn't support ftp, because it is insecure. However, we support sftp (ftp over ssh). This works similar as ssh. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Non-graphical methods== The most common way to transfer files is with a terminal by using the <code>scp</code> command. =Copying file to host:= scp SourceFile user@host:directory/TargetFile If you want to copy an '''empty''' folder, you have to add -r, for example: scp -r SourceFolder user@host:directory/TargetFolder =Copying file from host:= scp user@host:directory/SourceFile TargetFile If you want to copy an '''empty''' folder, you have to add -r, for example: scp -r user@host:directory/SourceFolder TargetFolder You don't need to use the full path to your file. You may you the relative path, starting from your home directory. For example: scp index.html user@ssh1.ulyssis.org:www/index.html You can find more info on the scp commands by using: man scp ==Graphical methods== The graphical methods are explained in [[Accessing your files]]. [[Category:Files]] [[Category:Shell]] 7d3d5dc4419651a69bef45c70d4c3afb33abddfe 1141 1140 2020-09-23T07:27:19Z Alexander 38 wikitext text/x-wiki ULYSSIS doesn't support ftp, because it is insecure. However, we support sftp (ftp over ssh). This works similar as ssh. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Non-graphical methods== The most common way to transfer files is with a terminal by using the <code>scp</code> command. =Copying file to host:= scp SourceFile user@host:directory/TargetFile If you want to copy an '''empty''' folder, you have to add -r, for example: scp -r SourceFolder user@host:directory/TargetFolder =Copying file from host:= scp user@host:directory/SourceFile TargetFile If you want to copy an '''empty''' folder, you have to add -r, for example: scp -r user@host:directory/SourceFolder TargetFolder You don't need to use the full path to your file. You may you the relative path, starting from your home directory. For example: scp index.html user@ssh1.ulyssis.org:www/index.html You can find '''more info''' on the '''scp commands''' by using: man scp ==Graphical methods== The graphical methods are explained in [[Accessing your files]]. [[Category:Files]] [[Category:Shell]] 4f7715dde8cbfa1e2ec309edfec583a765543768 0 49 1142 733 2020-10-07T20:51:00Z Casper 39 wikitext text/x-wiki ==How to install WordPress for your account== First you need to download Joomla from their website, https://downloads.joomla.org/. After you've received a zip file, you have to extract it using your file manager (Windows: use right-click and select "extract all"; OSX: double-click the zip, it automatically extracts; Linux: right-click the file, and select "extract here"). This will give you some files and directories so preferably, you want to extract this zip in a new empty directory. Next, you have to move the '''extracted contents''' of the zip to your webroot directory on our servers. Mostly this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Joomla on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there.<br> Now we are ready to install Joomla, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. On the first tab you have to create a name and an optional description for your Joomla website. Besides that, you also have to fill in the information of the "Super User Account", this is the administrator account of your website. At last there is also a switch if you'd want your site to be offline after the installation (this can be changed later), but it's better to leave the switch on NO by default. When you are done with the configuration, you click on next. Moving to the second tab, this is where we will select what database the website will use. You will need to follow our configuration here: *'''Database Type:''' select MySQL in the drop-down menu *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Table Prefix:''' only change this if you have multiple installations of WordPress in your database<br> Any other settings you leave on default. Now we are done configuring the database and we can click next.<br> '''Warning:''' it is possible that you get the error: <code>To confirm that you are the owner of this website please delete the file named "_JoomlaXXXXXXXXXXXXXXX.txt" we have created in the "installation" folder of your Joomla site.</code> This means you need to go back to one of our shell servers and delete that file inside the directory <code>installation</code> in the www folder. (For information about going to our webservers, you can use this guide: [[Accessing your files]].) After doing this you can just click next again and it will continue to the last tab. The last tab will give you an overview of the installation. We will leave anything here by default and scroll down to the button 'install' and click it. Congratulations, you have installed your own Joomla website. There are just a few small things that need to be done. Optionally you can install extra languages using the button on the page after the installation.<br> If you are done setting up the configurations, you can go to your website at <code>username.ulyssis.be</code> where you will be welcomed with a standard Joomla webpage. To start building your own website, it can be very interesting to check https://docs.joomla.org/Special:MyLanguage/Tutorials:Beginners for some beginner tutorials. If you have any problems regarding your installation, feel free to contact us at ulyssis@ulyssis.org ==Setting up multiple instances of Joomla== If you want to have multiple instances of a Joomla site then you the create a new folder in your homedir from your shell account. You need a new virtual host, you can send us an [mailto:ulyssis@ulyssis.org email] and we will create one for you. After your new virtual host is ready, you need to do all the same steps as for a regular Joomla installation. Another option is to use the Joomla [https://docs.joomla.org/Multiple_Domains_and_Web_Sites_in_a_single_Joomla!_installation multisite] option. [[Category:CMSs]] 8114f84a617325dae1110f3fec60030739dafe5c 1143 1142 2020-10-07T20:51:55Z Casper 39 /* How to install WordPress for your account */ wikitext text/x-wiki ==How to install Joomla for your account== First you need to download Joomla from their website, https://downloads.joomla.org/. After you've received a zip file, you have to extract it using your file manager (Windows: use right-click and select "extract all"; OSX: double-click the zip, it automatically extracts; Linux: right-click the file, and select "extract here"). This will give you some files and directories so preferably, you want to extract this zip in a new empty directory. Next, you have to move the '''extracted contents''' of the zip to your webroot directory on our servers. Mostly this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Joomla on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there.<br> Now we are ready to install Joomla, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. On the first tab you have to create a name and an optional description for your Joomla website. Besides that, you also have to fill in the information of the "Super User Account", this is the administrator account of your website. At last there is also a switch if you'd want your site to be offline after the installation (this can be changed later), but it's better to leave the switch on NO by default. When you are done with the configuration, you click on next. Moving to the second tab, this is where we will select what database the website will use. You will need to follow our configuration here: *'''Database Type:''' select MySQL in the drop-down menu *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Table Prefix:''' only change this if you have multiple installations of WordPress in your database<br> Any other settings you leave on default. Now we are done configuring the database and we can click next.<br> '''Warning:''' it is possible that you get the error: <code>To confirm that you are the owner of this website please delete the file named "_JoomlaXXXXXXXXXXXXXXX.txt" we have created in the "installation" folder of your Joomla site.</code> This means you need to go back to one of our shell servers and delete that file inside the directory <code>installation</code> in the www folder. (For information about going to our webservers, you can use this guide: [[Accessing your files]].) After doing this you can just click next again and it will continue to the last tab. The last tab will give you an overview of the installation. We will leave anything here by default and scroll down to the button 'install' and click it. Congratulations, you have installed your own Joomla website. There are just a few small things that need to be done. Optionally you can install extra languages using the button on the page after the installation.<br> If you are done setting up the configurations, you can go to your website at <code>username.ulyssis.be</code> where you will be welcomed with a standard Joomla webpage. To start building your own website, it can be very interesting to check https://docs.joomla.org/Special:MyLanguage/Tutorials:Beginners for some beginner tutorials. If you have any problems regarding your installation, feel free to contact us at ulyssis@ulyssis.org ==Setting up multiple instances of Joomla== If you want to have multiple instances of a Joomla site then you the create a new folder in your homedir from your shell account. You need a new virtual host, you can send us an [mailto:ulyssis@ulyssis.org email] and we will create one for you. After your new virtual host is ready, you need to do all the same steps as for a regular Joomla installation. Another option is to use the Joomla [https://docs.joomla.org/Multiple_Domains_and_Web_Sites_in_a_single_Joomla!_installation multisite] option. [[Category:CMSs]] f867dbcef389ae919b27b2b608568facb3a64a80 1144 1143 2020-10-07T20:56:36Z Casper 39 wikitext text/x-wiki ==How to install Joomla for your account== First you need to download Joomla from their website, https://downloads.joomla.org/. After you've received a zip file, you have to extract it using your file manager (Windows: use right-click and select "extract all"; OSX: double-click the zip, it automatically extracts; Linux: right-click the file, and select "extract here"). This will give you some files and directories so preferably, you want to extract this zip in a new empty directory. Next, you have to move the '''extracted contents''' of the zip to your webroot directory on our servers. Mostly this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Joomla on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there.<br> Now we are ready to install Joomla, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. On the first tab you have to create a name and an optional description for your Joomla website. Besides that, you also have to fill in the information of the "Super User Account", this is the administrator account of your website. At last there is also a switch if you'd want your site to be offline after the installation (this can be changed later), but it's better to leave the switch on NO by default. When you are done with the configuration, you click on next. Moving to the second tab, this is where we will select what database the website will use. You will need to follow our configuration here: *'''Database Type:''' select MySQL in the drop-down menu *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Table Prefix:''' only change this if you have multiple installations of Joomla in your database<br> Any other settings you leave on default. Now we are done configuring the database and we can click next.<br> '''Warning:''' it is possible that you get the error: <code>To confirm that you are the owner of this website please delete the file named "_JoomlaXXXXXXXXXXXXXXX.txt" we have created in the "installation" folder of your Joomla site.</code> This means you need to go back to one of our shell servers and delete that file inside the directory <code>installation</code> in the www folder. (For information about going to our webservers, you can use this guide: [[Accessing your files]].) After doing this you can just click next again and it will continue to the last tab. The last tab will give you an overview of the installation. We will leave anything here by default and scroll down to the button 'install' and click it. Congratulations, you have installed your own Joomla website. There are just a few small things that need to be done. Optionally you can install extra languages using the button on the page after the installation.<br> If you are done setting up the configurations, you can go to your website at <code>username.ulyssis.be</code> where you will be welcomed with a standard Joomla webpage. To start building your own website, it can be very interesting to check https://docs.joomla.org/Special:MyLanguage/Tutorials:Beginners for some beginner tutorials. If you have any problems regarding your installation, feel free to contact us at ulyssis@ulyssis.org ==Setting up multiple instances of Joomla== If you want to have multiple instances of a Joomla site then you the create a new folder in your homedir from your shell account. You need a new virtual host, you can send us an [mailto:ulyssis@ulyssis.org email] and we will create one for you. After your new virtual host is ready, you need to do all the same steps as for a regular Joomla installation. Another option is to use the Joomla [https://docs.joomla.org/Multiple_Domains_and_Web_Sites_in_a_single_Joomla!_installation multisite] option. [[Category:CMSs]] 47dcc6206093e9568f8ab5beb2c7c8f4eeeeb054 1145 1144 2020-10-07T21:11:04Z Casper 39 /* How to install Joomla for your account */ wikitext text/x-wiki ==How to install Joomla for your account== First you need to download Joomla from their website, https://downloads.joomla.org/. After you've received a zip file, you have to extract it using your file manager (Windows: use right-click and select "extract all"; OSX: double-click the zip, it automatically extracts; Linux: right-click the file, and select "extract here"). This will give you some files and directories so preferably, you want to extract this zip in a new empty directory. Next, you have to move the '''extracted contents''' of the zip to your webroot directory on our servers. Mostly this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Joomla on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there.<br> Warning: Postgresql databases can be used for Joomla as well, but they often bring many different issues, so we recommend to use MySQL instead. Now we are ready to install Joomla, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. On the first tab you have to create a name and an optional description for your Joomla website. Besides that, you also have to fill in the information of the "Super User Account", this is the administrator account of your website. Finally, there is also a switch if you'd want your site to be offline after the installation (this can be changed later), but it's better to leave the switch on NO by default. When you are done with the configuration, you click on next. Moving to the second tab, this is where we will select what database the website will use. You will need to follow our configuration here: *'''Database Type:''' select MySQL in the drop-down menu *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Table Prefix:''' only change this if you have multiple installations of Joomla in your database<br> Any other settings you leave on default. Now we are done configuring the database and we can click next.<br> '''Warning:''' it is possible that you get the error: <code>To confirm that you are the owner of this website please delete the file named "_JoomlaXXXXXXXXXXXXXXX.txt" we have created in the "installation" folder of your Joomla site.</code> This means you need to go back to one of our shell servers and delete that file inside the directory <code>installation</code> in the www folder. (For information about going to our webservers, you can use this guide: [[Accessing your files]].) After doing this you can just click next again and it will continue to the last tab. The last tab will give you an overview of the installation. We will leave anything here by default and scroll down to the button 'install' and click it. Congratulations, you have installed your own Joomla website. There are just a few small things that need to be done. Optionally you can install extra languages using the button on the page after the installation.<br> If you are done setting up the configurations, you can go to your website at <code>username.ulyssis.be</code> where you will be welcomed with a standard Joomla webpage. To start building your own website, it can be very interesting to check https://docs.joomla.org/Special:MyLanguage/Tutorials:Beginners for some beginner tutorials. If you have any problems regarding your installation, feel free to contact us at ulyssis@ulyssis.org ==Setting up multiple instances of Joomla== If you want to have multiple instances of a Joomla site then you the create a new folder in your homedir from your shell account. You need a new virtual host, you can send us an [mailto:ulyssis@ulyssis.org email] and we will create one for you. After your new virtual host is ready, you need to do all the same steps as for a regular Joomla installation. Another option is to use the Joomla [https://docs.joomla.org/Multiple_Domains_and_Web_Sites_in_a_single_Joomla!_installation multisite] option. [[Category:CMSs]] ace249dc011075cc8ce061c510fa71ecaa8da3a0 1146 1145 2020-10-07T21:14:12Z Casper 39 /* How to install Joomla for your account */ wikitext text/x-wiki ==How to install Joomla for your account== First you need to download Joomla from their website, https://downloads.joomla.org/. After you've received a zip file, you have to extract it using your file manager (Windows: use right-click and select "extract all"; OSX: double-click the zip, it automatically extracts; Linux: right-click the file, and select "extract here"). This will give you some files and directories so preferably, you want to extract this zip in a new empty directory. Next, you have to move the '''extracted contents''' of the zip to your webroot directory on our servers. Mostly this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Joomla on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there.<br> Warning: Postgresql databases can be used for Joomla as well, but they often bring many different issues, so we recommend to use MySQL instead. Now we are ready to install Joomla, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. On the first tab you have to create a name and an optional description for your Joomla website. Besides that, you also have to fill in the information of the "Super User Account", this is the administrator account of your website. Finally, there is also a switch if you'd want your site to be offline after the installation (this can be changed later), but it's better to leave the switch on NO by default. When you are done with the configuration, you click on next. Moving to the second tab, this is where we will select what database the website will use. You will need to follow our configuration here: *'''Database Type:''' select MySQL in the drop-down menu *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Table Prefix:''' only change this if you have multiple installations of Joomla in your database<br> Any other settings you leave on default. Now we are done configuring the database and we can click next.<br> {{Warning| It is possible that you get the error: <code>To confirm that you are the owner of this website please delete the file named "_JoomlaXXXXXXXXXXXXXXX.txt" we have created in the "installation" folder of your Joomla site.</code> This means you need to go back to one of our shell servers and delete that file inside the directory <code>installation</code> in the www folder. (For information about going to our webservers, you can use this guide: [[Accessing your files]].) After doing this you can just click next again and it will continue to the last tab.}} The last tab will give you an overview of the installation. We will leave anything here by default and scroll down to the button 'install' and click it. Congratulations, you have installed your own Joomla website. There are just a few small things that need to be done. Optionally you can install extra languages using the button on the page after the installation.<br> If you are done setting up the configurations, you can go to your website at <code>username.ulyssis.be</code> where you will be welcomed with a standard Joomla webpage. To start building your own website, it can be very interesting to check https://docs.joomla.org/Special:MyLanguage/Tutorials:Beginners for some beginner tutorials. If you have any problems regarding your installation, feel free to contact us at ulyssis@ulyssis.org ==Setting up multiple instances of Joomla== If you want to have multiple instances of a Joomla site then you the create a new folder in your homedir from your shell account. You need a new virtual host, you can send us an [mailto:ulyssis@ulyssis.org email] and we will create one for you. After your new virtual host is ready, you need to do all the same steps as for a regular Joomla installation. Another option is to use the Joomla [https://docs.joomla.org/Multiple_Domains_and_Web_Sites_in_a_single_Joomla!_installation multisite] option. [[Category:CMSs]] 26644bfdd102c7db9c5ab0b37760692a543e78f0 1147 1146 2020-10-07T21:14:30Z Casper 39 /* How to install Joomla for your account */ wikitext text/x-wiki ==How to install Joomla for your account== First you need to download Joomla from their website, https://downloads.joomla.org/. After you've received a zip file, you have to extract it using your file manager (Windows: use right-click and select "extract all"; OSX: double-click the zip, it automatically extracts; Linux: right-click the file, and select "extract here"). This will give you some files and directories so preferably, you want to extract this zip in a new empty directory. Next, you have to move the '''extracted contents''' of the zip to your webroot directory on our servers. Mostly this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Joomla on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there.<br> Warning: Postgresql databases can be used for Joomla as well, but they often bring many different issues, so we recommend to use MySQL instead. Now we are ready to install Joomla, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. On the first tab you have to create a name and an optional description for your Joomla website. Besides that, you also have to fill in the information of the "Super User Account", this is the administrator account of your website. Finally, there is also a switch if you'd want your site to be offline after the installation (this can be changed later), but it's better to leave the switch on NO by default. When you are done with the configuration, you click on next. Moving to the second tab, this is where we will select what database the website will use. You will need to follow our configuration here: *'''Database Type:''' select MySQL in the drop-down menu *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Table Prefix:''' only change this if you have multiple installations of Joomla in your database<br> Any other settings you leave on default. Now we are done configuring the database and we can click next.<br> {{notice| It is possible that you get the error: <code>To confirm that you are the owner of this website please delete the file named "_JoomlaXXXXXXXXXXXXXXX.txt" we have created in the "installation" folder of your Joomla site.</code> This means you need to go back to one of our shell servers and delete that file inside the directory <code>installation</code> in the www folder. (For information about going to our webservers, you can use this guide: [[Accessing your files]].) After doing this you can just click next again and it will continue to the last tab.}} The last tab will give you an overview of the installation. We will leave anything here by default and scroll down to the button 'install' and click it. Congratulations, you have installed your own Joomla website. There are just a few small things that need to be done. Optionally you can install extra languages using the button on the page after the installation.<br> If you are done setting up the configurations, you can go to your website at <code>username.ulyssis.be</code> where you will be welcomed with a standard Joomla webpage. To start building your own website, it can be very interesting to check https://docs.joomla.org/Special:MyLanguage/Tutorials:Beginners for some beginner tutorials. If you have any problems regarding your installation, feel free to contact us at ulyssis@ulyssis.org ==Setting up multiple instances of Joomla== If you want to have multiple instances of a Joomla site then you the create a new folder in your homedir from your shell account. You need a new virtual host, you can send us an [mailto:ulyssis@ulyssis.org email] and we will create one for you. After your new virtual host is ready, you need to do all the same steps as for a regular Joomla installation. Another option is to use the Joomla [https://docs.joomla.org/Multiple_Domains_and_Web_Sites_in_a_single_Joomla!_installation multisite] option. [[Category:CMSs]] a1dff559829c90513045e599dbadfc2d2a8bd514 1148 1147 2020-10-07T21:15:04Z Casper 39 /* How to install Joomla for your account */ wikitext text/x-wiki ==How to install Joomla for your account== First you need to download Joomla from their website, https://downloads.joomla.org/. After you've received a zip file, you have to extract it using your file manager (Windows: use right-click and select "extract all"; OSX: double-click the zip, it automatically extracts; Linux: right-click the file, and select "extract here"). This will give you some files and directories so preferably, you want to extract this zip in a new empty directory. Next, you have to move the '''extracted contents''' of the zip to your webroot directory on our servers. Mostly this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Joomla on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there.<br> Warning: Postgresql databases can be used for Joomla as well, but they often bring many different issues, so we recommend to use MySQL instead. Now we are ready to install Joomla, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. On the first tab you have to create a name and an optional description for your Joomla website. Besides that, you also have to fill in the information of the "Super User Account", this is the administrator account of your website. Finally, there is also a switch if you'd want your site to be offline after the installation (this can be changed later), but it's better to leave the switch on NO by default. When you are done with the configuration, you click on next. Moving to the second tab, this is where we will select what database the website will use. You will need to follow our configuration here: *'''Database Type:''' select MySQL in the drop-down menu *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Table Prefix:''' only change this if you have multiple installations of Joomla in your database<br> Any other settings you leave on default. Now we are done configuring the database and we can click next.<br> {{notice| It is possible that you get the error: <code>To confirm that you are the owner of this website please delete the file named "_JoomlaXXXXXXXXXXXXXXX.txt" we have created in the "installation" folder of your Joomla site.</code> This means you need to go back to one of our shell servers and delete that file inside the directory <code>installation</code> in the <code>www</code> folder. (For information about going to our webservers, you can use this guide: [[Accessing your files]].) After doing this you can just click next again and it will continue to the last tab.}} The last tab will give you an overview of the installation. We will leave anything here by default and scroll down to the button 'install' and click it. Congratulations, you have installed your own Joomla website. There are just a few small things that need to be done. Optionally you can install extra languages using the button on the page after the installation.<br> If you are done setting up the configurations, you can go to your website at <code>username.ulyssis.be</code> where you will be welcomed with a standard Joomla webpage. To start building your own website, it can be very interesting to check https://docs.joomla.org/Special:MyLanguage/Tutorials:Beginners for some beginner tutorials. If you have any problems regarding your installation, feel free to contact us at ulyssis@ulyssis.org ==Setting up multiple instances of Joomla== If you want to have multiple instances of a Joomla site then you the create a new folder in your homedir from your shell account. You need a new virtual host, you can send us an [mailto:ulyssis@ulyssis.org email] and we will create one for you. After your new virtual host is ready, you need to do all the same steps as for a regular Joomla installation. Another option is to use the Joomla [https://docs.joomla.org/Multiple_Domains_and_Web_Sites_in_a_single_Joomla!_installation multisite] option. [[Category:CMSs]] f2fd2dc676ff0a38581be30ec12bdccb7df4d0b9 1149 1148 2020-10-07T21:17:00Z Casper 39 /* How to install Joomla for your account */ wikitext text/x-wiki ==How to install Joomla for your account== First you need to download Joomla from their website, https://downloads.joomla.org/. After you've received a zip file, you have to extract it using your file manager (Windows: use right-click and select "extract all"; OSX: double-click the zip, it automatically extracts; Linux: right-click the file, and select "extract here"). This will give you some files and directories so preferably, you want to extract this zip in a new empty directory. Next, you have to move the '''extracted contents''' of the zip to your webroot directory on our servers. Mostly this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Joomla on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there.<br> Warning: Postgresql databases can be used for Joomla as well, but they often bring many different issues, so we recommend to use MySQL instead. Now we are ready to install Joomla, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. On the first tab you have to create a name and an optional description for your Joomla website. Besides that, you also have to fill in the information of the "Super User Account", this is the administrator account of your website. Finally, there is also a switch if you'd want your site to be offline after the installation (this can be changed later), but it's better to leave the switch on NO by default. When you are done with the configuration, you click on next. Moving to the second tab, this is where we will select what database the website will use. You will need to follow our configuration here: *'''Database Type:''' select MySQL in the drop-down menu *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Table Prefix:''' only change this if you have multiple installations of Joomla in your database<br> Any other settings you leave on default. Now we are done configuring the database and we can click next.<br> {{notice| Warning | It is possible that you get the error: <code>To confirm that you are the owner of this website please delete the file named "_JoomlaXXXXXXXXXXXXXXX.txt" we have created in the "installation" folder of your Joomla site.</code> This means you need to go back to one of our shell servers and delete that file inside the directory <code>installation</code> in the <code>www</code> folder. (For information about going to our webservers, you can use this guide: [[Accessing your files]].) After doing this you can just click next again and it will continue to the last tab.}} The last tab will give you an overview of the installation. We will leave anything here by default and scroll down to the button 'install' and click it. Congratulations, you have installed your own Joomla website. There are just a few small things that need to be done. Optionally you can install extra languages using the button on the page after the installation.<br> If you are done setting up the configurations, you can go to your website at <code>username.ulyssis.be</code> where you will be welcomed with a standard Joomla webpage. To start building your own website, it can be very interesting to check https://docs.joomla.org/Special:MyLanguage/Tutorials:Beginners for some beginner tutorials. If you have any problems regarding your installation, feel free to contact us at ulyssis@ulyssis.org ==Setting up multiple instances of Joomla== If you want to have multiple instances of a Joomla site then you the create a new folder in your homedir from your shell account. You need a new virtual host, you can send us an [mailto:ulyssis@ulyssis.org email] and we will create one for you. After your new virtual host is ready, you need to do all the same steps as for a regular Joomla installation. Another option is to use the Joomla [https://docs.joomla.org/Multiple_Domains_and_Web_Sites_in_a_single_Joomla!_installation multisite] option. [[Category:CMSs]] b9dfb56d4507592547f36bf70214ada9742cc945 1150 1149 2020-10-07T21:19:07Z Casper 39 /* How to install Joomla for your account */ wikitext text/x-wiki ==How to install Joomla for your account== First you need to download Joomla from their website, https://downloads.joomla.org/. After you've received a zip file, you have to extract it using your file manager (Windows: use right-click and select "extract all"; OSX: double-click the zip, it automatically extracts; Linux: right-click the file, and select "extract here"). This will give you some files and directories so preferably, you want to extract this zip in a new empty directory. Next, you have to move the '''extracted contents''' of the zip to your webroot directory on our servers. Mostly this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Joomla on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there.<br> Warning: Postgresql databases can be used for Joomla as well, but they often bring many different issues, so we recommend to use MySQL instead. Now we are ready to install Joomla, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. On the first tab you have to create a name and an optional description for your Joomla website. Besides that, you also have to fill in the information of the "Super User Account", this is the administrator account of your website. Finally, there is also a switch if you'd want your site to be offline after the installation (this can be changed later), but it's better to leave the switch on NO by default. When you are done with the configuration, you click on next. Moving to the second tab, this is where we will select what database the website will use. You will need to follow our configuration here: *'''Database Type:''' select MySQL in the drop-down menu *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Table Prefix:''' only change this if you have multiple installations of Joomla in your database<br> Any other settings you leave on default. Now we are done configuring the database and we can click next.<br> {{notice| Warning | It is possible that you get the error: <code>To confirm that you are the owner of this website please delete the file named "_JoomlaXXXXXXXXXXXXXXX.txt" we have created in the "installation" folder of your Joomla site.</code> This means you need to go back to one of our shell servers and delete that file inside the directory <code>installation</code> in the <code>www</code> folder. (For information about going to our webservers, you can use this guide: [[Accessing your files]].) After doing this you can just click next again and it will continue to the last tab.}} The last tab will give you an overview of the installation. We can leave anything here by default and scroll down to the button 'install' and click it. Congratulations, you have installed your own Joomla website. There are just a few small things that need to be done. Optionally you can install extra languages using the button on the page after the installation.<br> If you are done setting up the configurations, you can go to your website at <code>username.ulyssis.be</code> where you will be welcomed with a standard Joomla webpage. To start building your own website, it can be very interesting to check https://docs.joomla.org/Special:MyLanguage/Tutorials:Beginners for some beginner tutorials. If you have any problems regarding your installation, feel free to contact us at ulyssis@ulyssis.org ==Setting up multiple instances of Joomla== If you want to have multiple instances of a Joomla site then you the create a new folder in your homedir from your shell account. You need a new virtual host, you can send us an [mailto:ulyssis@ulyssis.org email] and we will create one for you. After your new virtual host is ready, you need to do all the same steps as for a regular Joomla installation. Another option is to use the Joomla [https://docs.joomla.org/Multiple_Domains_and_Web_Sites_in_a_single_Joomla!_installation multisite] option. [[Category:CMSs]] 894cfb54df8504e664ee85d1e7d330ad2c023a92 1151 1150 2020-10-08T15:36:08Z Casper 39 wikitext text/x-wiki ==How to install Joomla for your account== First you need to download Joomla from their website, https://downloads.joomla.org/. After you've received a zip file, you have to extract it using your file manager (Windows: use right-click and select "extract all"; OSX: double-click the zip, it automatically extracts; Linux: right-click the file, and select "extract here"). This will give you some files and directories so preferably, you want to extract this zip in a new empty directory. Next, you have to move the '''extracted contents''' of the zip to your webroot directory on our servers. Mostly this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Joomla on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there.<br> {{notice| Warning| Postgresql databases can be used for Joomla as well, but they often bring many different issues, so we recommend to use MySQL instead.}} Now we are ready to install Joomla, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. On the first tab you have to create a name and an optional description for your Joomla website. Besides that, you also have to fill in the information of the "Super User Account", this is the administrator account of your website. Finally, there is also a switch if you'd want your site to be offline after the installation (this can be changed later), but it's better to leave the switch on NO by default. When you are done with the configuration, you click on next. Moving to the second tab, this is where we will select what database the website will use. You will need to follow our configuration here: *'''Database Type:''' select MySQL in the drop-down menu *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Table Prefix:''' only change this if you have multiple installations of Joomla in your database<br> Any other settings you leave on default. Now we are done configuring the database and we can click next.<br> {{notice| Warning | It is possible that you get the error: <code>To confirm that you are the owner of this website please delete the file named "_JoomlaXXXXXXXXXXXXXXX.txt" we have created in the "installation" folder of your Joomla site.</code> This means you need to go back to one of our shell servers and delete that file inside the directory <code>installation</code> in the <code>www</code> folder. (For information about going to our webservers, you can use this guide: [[Accessing your files]].) After doing this you can just click next again and it will continue to the last tab.}} The last tab will give you an overview of the installation. We can leave anything here by default and scroll down to the button 'install' and click it. Congratulations, you have installed your own Joomla website. There are just a few small things that need to be done. Optionally you can install extra languages using the button on the page after the installation.<br> If you are done setting up the configurations, you can go to your website at <code>username.ulyssis.be</code> where you will be welcomed with a standard Joomla webpage. To start building your own website, it can be very interesting to check https://docs.joomla.org/Special:MyLanguage/Tutorials:Beginners for some beginner tutorials. If you have any problems regarding your installation, feel free to contact us at ulyssis@ulyssis.org ==Setting up multiple instances of Joomla== If you want to have multiple instances of a Joomla site then you the create a new folder in your homedir from your shell account. You need a new virtual host, you can send us an [mailto:ulyssis@ulyssis.org email] and we will create one for you. After your new virtual host is ready, you need to do all the same steps as for a regular Joomla installation. Another option is to use the Joomla [https://docs.joomla.org/Multiple_Domains_and_Web_Sites_in_a_single_Joomla!_installation multisite] option. [[Category:CMSs]] 1c84b21f2eb7260a995ee8293ae2caf53716d339 1154 1151 2020-10-08T15:47:17Z Casper 39 wikitext text/x-wiki ==How to install Joomla for your account== First you need to download Joomla from their website, https://downloads.joomla.org/. After you've received a zip file, you have to extract it using your file manager (Windows: use right-click and select "extract all"; OSX: double-click the zip, it automatically extracts; Linux: right-click the file, and select "extract here"). This will give you some files and directories so preferably, you want to extract this zip in a new empty directory. Next, you have to move the '''extracted contents''' of the zip to your webroot directory on our servers. Mostly this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Joomla on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there.<br> {{notice| Warning| Postgresql databases can be used for Joomla as well, but they often bring many different issues, so we recommend to use MySQL instead.}} Now we are ready to install Joomla, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. On the first tab you have to create a name and an optional description for your Joomla website. Besides that, you also have to fill in the information of the "Super User Account", this is the administrator account of your website. Finally, there is also a switch if you'd want your site to be offline after the installation (this can be changed later), but it's better to leave the switch on NO by default. When you are done with the configuration, you click on next.<br> The following image is an example screenshot of the configuration, so you will need to replace this with your own settings: [[File:Joomla_wizard.png|thumb|left|600px]] Moving to the second tab, this is where we will select what database the website will use. You will need to follow our configuration here: *'''Database Type:''' select MySQL in the drop-down menu *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Table Prefix:''' only change this if you have multiple installations of Joomla in your database<br> Any other settings you leave on default.<br> So it will look something like this: [[File:Joomla_databaseconfig.png|thumb|left|600px]] Now we are done configuring the database and we can click next.<br> {{notice| Warning | It is possible that you get the error: <code>To confirm that you are the owner of this website please delete the file named "_JoomlaXXXXXXXXXXXXXXX.txt" we have created in the "installation" folder of your Joomla site.</code> This means you need to go back to one of our shell servers and delete that file inside the directory <code>installation</code> in the <code>www</code> folder. (For information about going to our webservers, you can use this guide: [[Accessing your files]].) After doing this you can just click next again and it will continue to the last tab.}} The last tab will give you an overview of the installation. We can leave anything here by default and scroll down to the button 'install' and click it. Congratulations, you have installed your own Joomla website. There are just a few small things that need to be done. Optionally you can install extra languages using the button on the page after the installation.<br> If you are done setting up the configurations, you can go to your website at <code>username.ulyssis.be</code> where you will be welcomed with a standard Joomla webpage. To start building your own website, it can be very interesting to check https://docs.joomla.org/Special:MyLanguage/Tutorials:Beginners for some beginner tutorials. If you have any problems regarding your installation, feel free to contact us at ulyssis@ulyssis.org ==Setting up multiple instances of Joomla== If you want to have multiple instances of a Joomla site then you the create a new folder in your homedir from your shell account. You need a new virtual host, you can send us an [mailto:ulyssis@ulyssis.org email] and we will create one for you. After your new virtual host is ready, you need to do all the same steps as for a regular Joomla installation. Another option is to use the Joomla [https://docs.joomla.org/Multiple_Domains_and_Web_Sites_in_a_single_Joomla!_installation multisite] option. [[Category:CMSs]] 0a7c8695d92a96619edbc28f270313758d845110 1155 1154 2020-10-08T15:50:55Z Casper 39 wikitext text/x-wiki ==How to install Joomla for your account== First you need to download Joomla from their website, https://downloads.joomla.org/. After you've received a zip file, you have to extract it using your file manager (Windows: use right-click and select "extract all"; OSX: double-click the zip, it automatically extracts; Linux: right-click the file, and select "extract here"). This will give you some files and directories so preferably, you want to extract this zip in a new empty directory. Next, you have to move the '''extracted contents''' of the zip to your webroot directory on our servers. Mostly this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Joomla on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there.<br> {{notice| Warning| Postgresql databases can be used for Joomla as well, but they often bring many different issues, so we recommend to use MySQL instead.}} Now we are ready to install Joomla, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. On the first tab you have to create a name and an optional description for your Joomla website. Besides that, you also have to fill in the information of the "Super User Account", this is the administrator account of your website. Finally, there is also a switch if you'd want your site to be offline after the installation (this can be changed later), but it's better to leave the switch on NO by default. When you are done with the configuration, you click on next.<br> The following image is an example screenshot of the configuration, so you will need to replace this with your own settings: [[File:Joomla_wizard.png|thumb|left|600px]] Moving to the second tab, this is where we will select what database the website will use. You will need to follow our configuration here: *'''Database Type:''' select MySQL in the drop-down menu *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Table Prefix:''' only change this if you have multiple installations of Joomla in your database<br> Any other settings you leave on default.<br> So it will look something like this: [[File:Joomla_databaseconfig.png|thumb|left|600px]] Now we are done configuring the database and we can click next.<br> {{notice| Warning | It is possible that you get the error: <code>To confirm that you are the owner of this website please delete the file named "_JoomlaXXXXXXXXXXXXXXX.txt" we have created in the "installation" folder of your Joomla site.</code> This means you need to go back to one of our shell servers and delete that file inside the directory <code>installation</code> in the <code>www</code> folder. (For information about going to our webservers, you can use this guide: [[Accessing your files]].) After doing this you can just click next again and it will continue to the last tab.}} The last tab will give you an overview of the installation. We can leave anything here by default and scroll down to the button 'install' and click it. Congratulations, you have installed your own Joomla website. There are just a few small things that need to be done. Optionally you can install extra languages using the button on the page after the installation.<br> If you are done setting up the configurations, you can go to your website at <code>username.ulyssis.be</code> where you will be welcomed with a standard Joomla webpage. To start building your own website, it can be very interesting to check https://docs.joomla.org/Special:MyLanguage/Tutorials:Beginners for some beginner tutorials. If you have any problems regarding your installation, feel free to contact us at ulyssis@ulyssis.org ==Setting up multiple instances of Joomla== If you want to have multiple instances of a Joomla site then you the create a new folder in your homedir from your shell account. You need a new virtual host, you can send us an [mailto:ulyssis@ulyssis.org email] and we will create one for you. After your new virtual host is ready, you need to do all the same steps as for a regular Joomla installation. Another option is to use the Joomla [https://docs.joomla.org/Multiple_Domains_and_Web_Sites_in_a_single_Joomla!_installation multisite] option. [[Category:CMSs]] 6c4cb9fb50645897d6c257919de1fba3daf5f93b 1156 1155 2020-10-08T16:56:11Z Yoa 30 /* How to install Joomla for your account */ wikitext text/x-wiki ==How to install Joomla for your account== First you need to download Joomla from their website, https://downloads.joomla.org/. After you've received a zip file, you have to extract it using your file manager (Windows: use right-click and select "extract all"; OSX: double-click the zip, it automatically extracts; Linux: right-click the file, and select "extract here"). This will give you some files and directories so preferably, you want to extract this zip in a new empty directory. Next, you have to move the '''extracted contents''' of the zip to your webroot directory on our servers. In most cases this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Joomla on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there.<br> {{notice| Warning| Postgresql databases can be used for Joomla as well, but they often bring many different issues, so we recommend to use MySQL instead.}} Now we are ready to install Joomla, so we need to go to the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. On the first tab you have to create a name and optionally a description for your Joomla website. Besides that, you also have to fill in the information of the "Super User Account", this is the administrator account of your website. Finally, there is also a switch if you'd want your site to be offline after the installation (this can be changed later), but it's better to leave the switch on "NO" by default. When you are done with the configuration, you click on next.<br> The following image is an example screenshot of the configuration, so you will need to replace this with your own settings: [[File:Joomla_wizard.png|thumb|left|600px]] Moving to the second tab, this is where we will select what database the website will use. You will need to follow our configuration here: *'''Database Type:''' select MySQL in the drop-down menu *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Table Prefix:''' only change this if you have multiple installations of Joomla in your database<br> Any other settings you leave on default.<br> So it will look something like this: [[File:Joomla_databaseconfig.png|thumb|left|600px]] Now we are done configuring the database and we can click next.<br> {{notice| Warning | It is possible that you get the error: <code>To confirm that you are the owner of this website please delete the file named "_JoomlaXXXXXXXXXXXXXXX.txt" we have created in the "installation" folder of your Joomla site.</code> This means you need to go back to one of our shell servers and delete that file inside the directory <code>installation</code> in the <code>www</code> folder. (For information about going to our webservers, you can use this guide: [[Accessing your files]].) After doing this you can just click next again and it will continue to the last tab.}} The last tab will give you an overview of the installation. We can leave anything here by default and scroll down to the button 'install' and click it. Congratulations, you have installed your own Joomla website. There are just a few small things that need to be done. For example, you can install extra languages using the button on the page after the installation if you want.<br> If you are done setting up the configurations, you can go to your website at <code>username.ulyssis.be</code> where you will be welcomed by a standard Joomla webpage. To start building your own website, it can be very interesting to check https://docs.joomla.org/Special:MyLanguage/Tutorials:Beginners for some beginner tutorials. If you have any problems regarding your installation, feel free to contact us at ulyssis@ulyssis.org ==Setting up multiple instances of Joomla== If you want to have multiple instances of a Joomla site then you the create a new folder in your homedir from your shell account. You need a new virtual host, you can send us an [mailto:ulyssis@ulyssis.org email] and we will create one for you. After your new virtual host is ready, you need to do all the same steps as for a regular Joomla installation. Another option is to use the Joomla [https://docs.joomla.org/Multiple_Domains_and_Web_Sites_in_a_single_Joomla!_installation multisite] option. [[Category:CMSs]] 8589aa5d76a9c7352f76962b63ac40e0f85b5f5e 6 150 1152 2020-10-08T15:40:23Z Casper 39 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 151 1153 2020-10-08T15:45:05Z Casper 39 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 7 1157 1115 2020-10-13T16:15:49Z Joachim 23 wikitext text/x-wiki ULYSSIS hosts its own IRC network. IRC stands for Internet Relay Chat, [https://en.wikipedia.org/wiki/Internet_Relay_Chat IRC on wikipedia]. It is a chat protocol that mainly focuses on group chat, but also allows for private chat. If you have an urgent question, IRC is often the quickest way to contact us. But also if you don't have a question and just want to hang out in our chat, feel free to join! ==Web IRC client== If you won't regularly use our IRC or if you just want to check it out, you can use our web IRC client. You can find it at [https://webirc.ulyssis.org/ webirc.ulyssis.org]. ==IRC network details== Below are specific instructions for some clients, but if you are already familiar with IRC, here are the details you need to connect to our server. We highly recommend using SSL. Server: irc.ulyssis.org Port: 6668 (SSL) Channel: #ulyssis If <code>irc.ulyssis.org</code> is down, you can also try the other server in the same network, hosted at <code>irc2.ulyssis.org</code>. Both are connected to each other and you can use them interchangeably. It is advised to add it as a fallback in your IRC client. ==IRC clients== To use IRC, you'll need an IRC client. We advise the terminal based [https://irssi.org/ irssi] or [https://weechat.org/ weechat] for Linux and [https://hexchat.github.io/ hexchat] or [https://www.mirc.com/ mIRC] for Windows, but there are a lot of other free options. You can only receive messages over IRC while you're connected. Therefore, we advise you to run irssi or weechat in either a screen or a tmux session. With a ULYSSIS account, you can run screen or tmux on our shellservers, as they keep running 24/7 you can use them to keep track of your conversations. Screen and tmux are similar programs. Screen has been around for longer and is more tested, while tmux is more modern with new features and being easier to use for beginners. ===Using irssi on our shell servers=== ====Connect to the shellserver==== Use the ssh command in your Linux or OS X terminal, or use PuTTY to connect on windows. Extensive information on how to do so can be found on [[Accessing shell servers over SSH]]. ====Start irssi in a screen==== *When on the shellserver, enter <code>screen -U</code> to start a screen session, or <code>tmux</code> to start a tmux session. *Enter <code>irssi</code> to start irssi *Connect to the IRC server: <code>/server -ssl irc.ulyssis.org 6668</code> *Connect to the public channel: <code>/join #ulyssis</code> ====Screen usage==== *To exit the screen: press Ctrl-A and press D ('detach') to return to the shellserver. *To reconnect: enter <code>screen -r</code> or <code>screen -DR</code> (the latter will create a new screen if it wasn't already made). ====Tmux usage==== *To exit the tmux session: press Ctrl-B and press D ('detach') to return to the shellserver. *To reconnect: enter <code>tmux attach</code> ====Help, I can't reconnect to my session!==== *Check if you are on the right shell server and didn't make a typing error. *If everything is correct, your screen may have been stopped by a crash or a reboot of our shellserver. You can check the [http://status.ulyssis.org status] section of our website for more information about possible downtimes. *Make sure you use the right program (<code>screen</code> if you started a screen session and <code>tmux</code> if you started a tmux session) ==Using ZNC== Alternatively, if you don't like using terminal-based clients, or just want to run your client locally, you can connect with our [https://znc.ulyssis.org/ ZNC server]. However, to use it, you'll need a ULYSSIS account. ZNC connects to our IRC server in your place (fill in the details at the beginning of this article). You can then connect to ZNC with a client of your choice, and it will send you the history you've missed while you were offline. Log in to our ZNC server. In your settings, create a new network. Fill in the basic details (server name, nickname, set <code>BindHost</code> to <code>0.0.0.0</code>). In the server field, fill in <code>irc.ulyssis.org +6668</code>. Add <code>#ulyssis</code> as a channel. You may want to increase the buffer count. Then save at the bottom of the page. In your IRC client, connect to the server <code>znc.ulyssis.org</code> on port 6666 (with SSL) and set <code>username/network:password</code> as password to the server. Replace <code>username</code> with your ULYSSIS username, <code>network</code> with the name of the network in your znc settings, and <code>password</code> with your ULYSSIS password. ==Using Bitlbee== With [https://www.bitlbee.org/main.php/news.r.html Bitlbee], you can connect to other services as if they were an IRC server. It is available at <code>bitlbee.ulyssis.org</code> on ports 7000 and 7001 (SSL). For documentation on how to use Bitlbee, we refer to the manual on its website. This service is only reachable from within the ULYSSIS and KU Leuven networks. [[Category:Shell]] [[Category:ULYSSIS Public Services]] c5ac6e43094158961e8cc3d58440d36b7882fa7e 0 3 1158 1128 2020-10-19T18:33:35Z Vincenttc 21 /* Versioning */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] * [[Secure file permissions]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2020]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Sending email from websites]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL/TLS|Getting SSL/TLS (HTTPS security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Claiming a port]] * [[ULYSSIS security measures]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] * [[Spam]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up WordPress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] * [[Using PHPPgAdmin]] * [[Using Adminer]] * [[Making Backups]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 7dec8cfca08625bf6883466fab1f1497428a3943 0 10 1159 1129 2020-10-22T14:24:49Z Operand 34 Verwijder referentie naar .ac.be domeinen wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty consultative bodies (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request, the following steps have to be performed: * Set up the site that needs SSL if that's not already the case * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Make sure our nameservers are being used for the involved domain(s), as explained on [[Adding domain names]] * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, download the <code>acme.sh</code> script as explained in the documentation: https://github.com/acmesh-official/acme.sh#1-how-to-install Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be If we provide an email address, for example "email@example.com", Let's Encrypt will remind us to renew our certificates when necessary. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew -d mydomain.be The renewed certificates will automatically be copied to the path specified in the <code>--issue</code> command. '''After renewing certificates, you have to email us to install your renewed certificate.''' ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. [[Category:Webserver]] cb294f2bf3c2ec9d22f90bbafd063c98e8308c7f 1180 1159 2020-11-13T14:53:29Z Alexander 38 wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty consultative bodies (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request, the following steps have to be performed: * Set up the site that needs SSL if that's not already the case * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Make sure our nameservers are being used for the involved domain(s), as explained on [[Adding domain names]] * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Certificate file structure ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir letsencrypt mkdir letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain ├── mydomain.be.crt └── mydomain.be.key If you already possess the necessary files, renaming and copying them accordingly is sufficient. Otherwise, you can generate or renew your certificates using '''acme.sh''': ==== Using acme.sh ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> ===== Generating the certificates ===== Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll be using the '''acme.sh''' program to generate our certificates on the ULYSSIS servers. First of all, in your home directory, download the <code>acme.sh</code> script as explained in the documentation: https://github.com/acmesh-official/acme.sh#1-how-to-install Next we actually generate the certificates. Make sure to replace the necessary parts (email, webroot, domain name): ./acme.sh --issue --cert-file letsencrypt/mydomain.be/mydomain.be.crt --key-file letsencrypt/mydomain.be/mydomain.be.key --ca-file letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@example.com" -w /home/user/myusername/path/to/webroot -d mydomain.be -d www.mydomain.be If we provide an email address, for example "email@example.com", Let's Encrypt will remind us to renew our certificates when necessary. <code>/home/user/myusername/path/to/webroot</code> is the path to the '''webroot of the domain name'''. Note that we are issuing certificates for "mydomain.be" here. We also want to add the subdomain "www.mydomain.be" to the certificate, so we also pass it to the script. You can add additional subdomains if needed. ===== Renewing the certificates ===== To renew our certificates, we just execute: ./acme.sh --renew -d mydomain.be The renewed certificates will automatically be copied to the path specified in the <code>--issue</code> command. '''After renewing certificates, you have to email us to install your renewed certificate.''' ==== Installing the certificates ==== We can check whether everything is stored correctly by executing: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL. So make sure you follow this procedure carefully. [[Category:Webserver]] 408147d0c0ae3584d4c1f39241f10525c9630e4d 1181 1180 2020-11-19T00:06:05Z Yoa 30 /* Let's Encrypt */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty consultative bodies (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request, the following steps have to be performed: * Set up the site that needs SSL if that's not already the case * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Make sure our nameservers are being used for the involved domain(s), as explained on [[Adding domain names]] * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Introduction ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir -p ~/letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain (the CA file) ├── mydomain.be.crt (the cert file; "public key") └── mydomain.be.key (the key file; "private key") If you already possess the necessary files, renaming and copying them accordingly is sufficient. '''You still have to email us to install your certificate.''' More information in the last section on this page. Otherwise, you can generate or renew your certificates using acme.sh. This is explained in the next section. ==== Generating certificates ==== <div style="background: #f2dede; color: #a94442; border: 1px solid #a94442; border-radius: 5px; padding: 5px">'''Warning:''' If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''': <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule> </div> Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll show how to use the acme.sh program to generate certificates on the ULYSSIS servers. Firstly, execute the following commands to download the acme.sh script in your home directory and make it executable: curl -o ~/acme.sh https://raw.githubusercontent.com/acmesh-official/acme.sh/master/acme.sh chmod +x ~/acme.sh Next, determine for which domains and subdomains you want to generate a certificate. You will need to generate a single certificate for each domain and subdomain which points to the same folder on your account (in most cases this is <code>www</code> in your home directory). The following example command will generate a certificate for <code>mydomain.be</code> and <code>www.mydomain.be</code> which points to the <code>www</code> folder in the home directory. '''Change the parameters''' as explained below before executing this command! ~/acme.sh --issue --cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt --key-file ~/letsencrypt/mydomain.be/mydomain.be.key --ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@mydomain.be" -w ~/www -d mydomain.be -d www.mydomain.be The explanation of these many parameters is as follows: * <code>--issue</code> tells acme.sh to generate a new certificate. * <code>--cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt</code> tells acme.sh to store the certificate file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. '''This folder should already exist''', please refer to the previous section if you have not created this folder yet. * <code>--key-file ~/letsencrypt/mydomain.be/mydomain.be.key</code> tells acme.sh to store the key file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>--ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain</code> tells acme.sh to store the CA file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>-m "email@mydomain.be"</code> tells acme.sh the email address associated with the certificate. Let's Encrypt will remind this email address (if provided) when the certificate is close to expiring. * <code>-w ~/www</code> tells acme.sh where the domains in this certificate point to. Make sure to change the <code>www</code> part if the domains point to a different folder in your home directory. * <code>-d mydomain.be</code> and <code>-d www.mydomain.be</code> tell acme.sh that the certificate should protect <code>mydomain.be</code> and <code>www.mydomain.be</code>. You should '''add all domain names''' pointing to the <code>-w</code> folder. '''After generating the certificate, you have to email us to install your new certificate.''' More information in the last section on this page. ==== Renewing certificates ==== To renew the certificates of <code>mydomain.be</code>, just execute: ~/acme.sh --renew -d mydomain.be The renewed certificates will automatically be copied to the files you provided in the command to generate the certificates (see previous section). '''After renewing the certificate, you have to email us to install your certificate.''' More information in the last section on this page. ==== Installing the certificates ==== Check whether everything is stored correctly by executing the following command: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL, so make sure you follow this procedure carefully. [[Category:Webserver]] bbc38a9a54d4fa3a383a634fbfbc617aad307f7c 1182 1181 2020-11-19T00:11:09Z Yoa 30 /* Generating certificates */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty consultative bodies (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request, the following steps have to be performed: * Set up the site that needs SSL if that's not already the case * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Make sure our nameservers are being used for the involved domain(s), as explained on [[Adding domain names]] * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Introduction ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir -p ~/letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain (the CA file) ├── mydomain.be.crt (the cert file; "public key") └── mydomain.be.key (the key file; "private key") If you already possess the necessary files, renaming and copying them accordingly is sufficient. '''You still have to email us to install your certificate.''' More information in the last section on this page. Otherwise, you can generate or renew your certificates using acme.sh. This is explained in the next section. ==== Generating certificates ==== {{notice|If you use a <code>.htaccess</code> file in the '''webroot of the domain name''', make sure to add the following lines at '''the top of the file''':|<pre> <IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule></pre>}} Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll show how to use the acme.sh program to generate certificates on the ULYSSIS servers. Firstly, execute the following commands to download the acme.sh script in your home directory and make it executable: curl -o ~/acme.sh https://raw.githubusercontent.com/acmesh-official/acme.sh/master/acme.sh chmod +x ~/acme.sh Next, determine for which domains and subdomains you want to generate a certificate. You will need to generate a single certificate for each domain and subdomain which points to the same folder on your account (in most cases this is <code>www</code> in your home directory). The following example command will generate a certificate for <code>mydomain.be</code> and <code>www.mydomain.be</code> which points to the <code>www</code> folder in the home directory. '''Change the parameters''' as explained below before executing this command! ~/acme.sh --issue --cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt --key-file ~/letsencrypt/mydomain.be/mydomain.be.key --ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@mydomain.be" -w ~/www -d mydomain.be -d www.mydomain.be The explanation of these many parameters is as follows: * <code>--issue</code> tells acme.sh to generate a new certificate. * <code>--cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt</code> tells acme.sh to store the certificate file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. '''This folder should already exist''', please refer to the previous section if you have not created this folder yet. * <code>--key-file ~/letsencrypt/mydomain.be/mydomain.be.key</code> tells acme.sh to store the key file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>--ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain</code> tells acme.sh to store the CA file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>-m "email@mydomain.be"</code> tells acme.sh the email address associated with the certificate. Let's Encrypt will remind this email address (if provided) when the certificate is close to expiring. * <code>-w ~/www</code> tells acme.sh where the domains in this certificate point to. Make sure to change the <code>www</code> part if the domains point to a different folder in your home directory. * <code>-d mydomain.be</code> and <code>-d www.mydomain.be</code> tell acme.sh that the certificate should protect <code>mydomain.be</code> and <code>www.mydomain.be</code>. You should '''add all domain names''' pointing to the <code>-w</code> folder. '''After generating the certificate, you have to email us to install your new certificate.''' More information in the last section on this page. ==== Renewing certificates ==== To renew the certificates of <code>mydomain.be</code>, just execute: ~/acme.sh --renew -d mydomain.be The renewed certificates will automatically be copied to the files you provided in the command to generate the certificates (see previous section). '''After renewing the certificate, you have to email us to install your certificate.''' More information in the last section on this page. ==== Installing the certificates ==== Check whether everything is stored correctly by executing the following command: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL, so make sure you follow this procedure carefully. [[Category:Webserver]] b3459e4a068c3aab6c6d47096a76c52c9c85cad8 1183 1182 2020-11-19T00:11:42Z Yoa 30 /* Generating certificates */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty consultative bodies (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request, the following steps have to be performed: * Set up the site that needs SSL if that's not already the case * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Make sure our nameservers are being used for the involved domain(s), as explained on [[Adding domain names]] * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== ==== Introduction ==== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir -p ~/letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain (the CA file) ├── mydomain.be.crt (the cert file; "public key") └── mydomain.be.key (the key file; "private key") If you already possess the necessary files, renaming and copying them accordingly is sufficient. '''You still have to email us to install your certificate.''' More information in the last section on this page. Otherwise, you can generate or renew your certificates using acme.sh. This is explained in the next section. ==== Generating certificates ==== {{notice|If you use a <code>.htaccess</code> file in the webroot of the domain name, make sure to add the following lines at the top of the file:|<pre><IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule></pre>}} Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll show how to use the acme.sh program to generate certificates on the ULYSSIS servers. Firstly, execute the following commands to download the acme.sh script in your home directory and make it executable: curl -o ~/acme.sh https://raw.githubusercontent.com/acmesh-official/acme.sh/master/acme.sh chmod +x ~/acme.sh Next, determine for which domains and subdomains you want to generate a certificate. You will need to generate a single certificate for each domain and subdomain which points to the same folder on your account (in most cases this is <code>www</code> in your home directory). The following example command will generate a certificate for <code>mydomain.be</code> and <code>www.mydomain.be</code> which points to the <code>www</code> folder in the home directory. '''Change the parameters''' as explained below before executing this command! ~/acme.sh --issue --cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt --key-file ~/letsencrypt/mydomain.be/mydomain.be.key --ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain --accountemail "email@mydomain.be" -w ~/www -d mydomain.be -d www.mydomain.be The explanation of these many parameters is as follows: * <code>--issue</code> tells acme.sh to generate a new certificate. * <code>--cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt</code> tells acme.sh to store the certificate file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. '''This folder should already exist''', please refer to the previous section if you have not created this folder yet. * <code>--key-file ~/letsencrypt/mydomain.be/mydomain.be.key</code> tells acme.sh to store the key file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>--ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain</code> tells acme.sh to store the CA file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>-m "email@mydomain.be"</code> tells acme.sh the email address associated with the certificate. Let's Encrypt will remind this email address (if provided) when the certificate is close to expiring. * <code>-w ~/www</code> tells acme.sh where the domains in this certificate point to. Make sure to change the <code>www</code> part if the domains point to a different folder in your home directory. * <code>-d mydomain.be</code> and <code>-d www.mydomain.be</code> tell acme.sh that the certificate should protect <code>mydomain.be</code> and <code>www.mydomain.be</code>. You should '''add all domain names''' pointing to the <code>-w</code> folder. '''After generating the certificate, you have to email us to install your new certificate.''' More information in the last section on this page. ==== Renewing certificates ==== To renew the certificates of <code>mydomain.be</code>, just execute: ~/acme.sh --renew -d mydomain.be The renewed certificates will automatically be copied to the files you provided in the command to generate the certificates (see previous section). '''After renewing the certificate, you have to email us to install your certificate.''' More information in the last section on this page. ==== Installing the certificates ==== Check whether everything is stored correctly by executing the following command: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL, so make sure you follow this procedure carefully. [[Category:Webserver]] 4b490a29014a39b40dcd402ce2676c3296a06b40 0 152 1160 2020-10-24T19:36:52Z Casper 39 Created page with "==Setting up multiple instances on your website== When you finished setting up any CMS (e.g. WordPress, Joomla, Drupal, etc.), perhaps you want a second installation of a CMS..." wikitext text/x-wiki ==Setting up multiple instances on your website== When you finished setting up any CMS (e.g. WordPress, Joomla, Drupal, etc.), perhaps you want a second installation of a CMS on your website. For example: you have your main WordPress website running on the URL wordpress.com, but you also want another new WordPress site on second.wordpress.org . To do this you will need to follow a few steps: First of all, you will need to access one of our shell servers. For more information about how to do this, you can visit: [[Accessing your files]]. Continuing, we need to make a new directory in your homedir, next to the <code>www</code> folder where you placed the first installation of the CMS. It is possible to place the new directory inside your <code>www</code> folder, but we do not recommend this because it will be very confusing for later maintenance/updates. We also recommend to name this directory to something obvious (e.g. a directory named <code>wiki</code> for a wiki installation), this will help others in the future. Next, you will need to send us an email at ulyssis@ulyssis.org to make a VHOST for this new directory. The information you need to send us is: the path of the new directory and the domain you want this website to be on (e.g. wiki.wordpress.org). When you receive a reply back from us that everything is in order, you will need to follow the steps again to install the new CMS in this directory. Here follows a list of things to be careful for when doing this: {{notice| Warning| Make sure you install the new instance in the '''correct folder'''}} {{notice| Warning| Be careful when using the .htaccess file, as it may cause problem with multiple instances}} {{notice| Warning| When installing your new CMS, make sure you configure the setting correctly for this installation as it will not be exactly the same as your previous setup}} {{notice| Warning| Provide the correct information when sending us an email for creating the new VHOST}} 7cba08d8025411f4cf681a573ea58d0bca410226 1161 1160 2020-10-24T19:37:39Z Casper 39 /* Setting up multiple instances on your website */ wikitext text/x-wiki ==Setting up multiple instances on your website== When you finished setting up any CMS (e.g. WordPress, Joomla, Drupal, etc.), perhaps you want a second installation of a CMS on your website. For example: you have your main WordPress website running on the URL wordpress.com, but you also want another new WordPress site on second.wordpress.org . To do this you will need to follow a few steps: First of all, you will need to access one of our shell servers. For more information about how to do this, you can visit: [[Accessing your files]]. Continuing, we need to make a new directory in your homedir, next to the <code>www</code> folder where you placed the first installation of the CMS. It is possible to place the new directory inside your <code>www</code> folder, but we do not recommend this because it will be very confusing for later maintenance/updates. We also recommend to name this directory to something obvious (e.g. a directory named <code>wiki</code> for a wiki installation), this will help others in the future. Next, you will need to send us an email at ulyssis@ulyssis.org to make a VHOST for this new directory. The information you need to send us is: the '''path''' of the new directory and the '''domain''' you want this website to be on (e.g. wiki.wordpress.org). When you receive a reply back from us that everything is in order, you will need to follow the steps again to install the new CMS in this directory. Here follows a list of things to be careful for when doing this: {{notice| Warning| Make sure you install the new instance in the '''correct folder'''}} {{notice| Warning| Be careful when using the .htaccess file, as it may cause problem with multiple instances}} {{notice| Warning| When installing your new CMS, make sure you configure the setting correctly for this installation as it will not be exactly the same as your previous setup}} {{notice| Warning| Provide the correct information when sending us an email for creating the new VHOST}} 770130188af3f47ad7bbe82f9f9aade2f0af6f9e 1162 1161 2020-10-24T19:38:36Z Casper 39 wikitext text/x-wiki ==Setting up multiple instances on your website== When you finished setting up any CMS (e.g. WordPress, Joomla, Drupal, etc.), perhaps you want a second installation of a CMS on your website. For example: you have your main WordPress website running on the URL wordpress.com, but you also want another new WordPress site on second.wordpress.org . To do this you will need to follow a few steps: First of all, you will need to access one of our shell servers. For more information about how to do this, you can visit: [[Accessing your files]]. Continuing, we need to make a new directory in your homedir, next to the <code>www</code> folder where you placed the first installation of the CMS. It is possible to place the new directory inside your <code>www</code> folder, but we do not recommend this because it will be very confusing for later maintenance/updates. We also recommend to name this directory to something obvious (e.g. a directory named <code>wiki</code> for a wiki installation), this will help others in the future. Next, you will need to send us an email at ulyssis@ulyssis.org to make a VHOST for this new directory. The information you need to send us is: the '''path''' of the new directory and the '''domain''' you want this website to be on (e.g. wiki.wordpress.org). When you receive a reply back from us that everything is in order, you will need to follow the steps from https://docs.ulyssis.org/Setting_up_WordPress, https://docs.ulyssis.org/Setting_up_Joomla or https://docs.ulyssis.org/Setting_up_Drupal again, to install the new CMS in this directory. Here follows a list of things to be careful for when doing this: {{notice| Warning| Make sure you install the new instance in the '''correct folder'''}} {{notice| Warning| Be careful when using the .htaccess file, as it may cause problem with multiple instances}} {{notice| Warning| When installing your new CMS, make sure you configure the setting correctly for this installation as it will not be exactly the same as your previous setup}} {{notice| Warning| Provide the correct information when sending us an email for creating the new VHOST}} d88681abfffcfc6c85d7554e049416593ae56caa 1163 1162 2020-10-24T19:40:29Z Casper 39 wikitext text/x-wiki ==Setting up multiple instances on your website== When you finished setting up any CMS (e.g. WordPress, Joomla, Drupal, etc.), perhaps you want a second installation of a CMS on your website. For example: you have your main WordPress website running on the URL wordpress.com, but you also want another new WordPress site on second.wordpress.org . To do this you will need to follow a few steps: First of all, you will need to access one of our shell servers. For more information about how to do this, you can visit: [[Accessing your files]]. Continuing, we need to make a new directory in your homedir, next to the <code>www</code> folder where you placed the first installation of the CMS. It is possible to place the new directory inside your <code>www</code> folder, but we do not recommend this because it will be very confusing for later maintenance/updates. We also recommend to name this directory to something obvious (e.g. a directory named <code>wiki</code> for a wiki installation), this will help others in the future. Next, you will need to send us an email at ulyssis@ulyssis.org to make a VHOST for this new directory. The information you need to send us is: the '''path''' of the new directory and the '''domain''' you want this website to be on (e.g. wiki.wordpress.org). When you receive a reply back from us that everything is in order, you will need to follow the steps from https://docs.ulyssis.org/Setting_up_WordPress, https://docs.ulyssis.org/Setting_up_Joomla or https://docs.ulyssis.org/Setting_up_Drupal (depending on what CMS you want to install) again, and install the new website in the '''right''' directory. Here follows a list of things to be careful for when doing this: {{notice| Warning| Make sure you install the new instance in the '''correct folder'''}} {{notice| Warning| Be careful when using the .htaccess file, as it may cause problem with multiple instances}} {{notice| Warning| When installing your new CMS, make sure you configure the setting correctly for this installation as it will not be exactly the same as your previous setup}} {{notice| Warning| Provide the correct information when sending us an email for creating the new VHOST}} dde8621a1106dd025da9ab13796e1afaf1a4ce71 1164 1163 2020-10-24T19:41:05Z Casper 39 /* Setting up multiple instances on your website */ wikitext text/x-wiki ==Setting up multiple instances on your website== When you finished setting up any CMS (e.g. WordPress, Joomla, Drupal, etc.), perhaps you want a second installation of a CMS on your website. For example: you have your main WordPress website running on the URL wordpress.com, but you also want another new WordPress site on second.wordpress.org . To do this you will need to follow a few steps: First of all, you will need to access one of our shell servers. For more information about how to do this, you can visit: [[Accessing your files]]. Continuing, we need to make a new directory in your homedir, next to the <code>www</code> folder where you placed the first installation of the CMS. It is possible to place the new directory inside your <code>www</code> folder, but we do not recommend this because it will be very confusing for later maintenance/updates. We also recommend to name this directory to something obvious (e.g. a directory named <code>wiki</code> for a wiki installation), this will help others in the future. Next, you will need to send us an email at ulyssis@ulyssis.org to make a VHOST for this new directory. The information you need to send us is: the '''path''' of the new directory and the '''domain''' you want this website to be on (e.g. wiki.wordpress.org). When you receive a reply back from us that everything is in order, you will need to follow the steps from https://docs.ulyssis.org/Setting_up_WordPress, https://docs.ulyssis.org/Setting_up_Joomla or https://docs.ulyssis.org/Setting_up_Drupal (depending on what CMS you want to install) again, and install the new website in the '''right''' directory. Here follows a list of things to be careful for when following all of these steps: {{notice| Warning| Make sure you install the new instance in the '''correct folder'''}} {{notice| Warning| Be careful when using the .htaccess file, as it may cause problem with multiple instances}} {{notice| Warning| When installing your new CMS, make sure you configure the setting correctly for this installation as it will not be exactly the same as your previous setup}} {{notice| Warning| Provide the correct information when sending us an email for creating the new VHOST}} e5c7c817546881ff485c89a35a3e6477615d3b71 1165 1164 2020-10-24T19:41:45Z Casper 39 wikitext text/x-wiki ==Setting up multiple instances on your website== When you finished setting up any CMS (e.g. WordPress, Joomla, Drupal, etc.), perhaps you want a second installation of a CMS on your website. For example: you have your main WordPress website running on the URL wordpress.com, but you also want another new WordPress site on second.wordpress.org . To do this you will need to follow a few steps: First of all, you will need to access one of our shell servers. For more information about how to do this, you can visit: [[Accessing your files]]. Continuing, we need to make a new directory in your homedir, next to the <code>www</code> folder where you placed the first installation of the CMS. It is possible to place the new directory inside your <code>www</code> folder, but we do not recommend this because it will be very confusing for later maintenance/updates. We also recommend to name this directory to something obvious (e.g. a directory named <code>wiki</code> for a wiki installation), this will help others in the future. Next, you will need to send us an email at ulyssis@ulyssis.org to make a VHOST for this new directory. The information you need to send us is: the '''path''' of the new directory and the '''domain''' you want this website to be on (e.g. wiki.wordpress.org). When you receive a reply back from us that everything is in order, you will need to follow the steps from https://docs.ulyssis.org/Setting_up_WordPress, https://docs.ulyssis.org/Setting_up_Joomla or https://docs.ulyssis.org/Setting_up_Drupal (depending on what CMS you want to install) again, and install the new website in the '''right''' directory. Here follows a list of things to be careful for when following all of these steps: {{notice| Warning| Make sure you install the new instance in the '''correct folder'''}} {{notice| Warning| Be careful when using the .htaccess file, as it may cause problem with multiple instances}} {{notice| Warning| When installing your new CMS, make sure you configure the setting properly for this installation as it will not be exactly the same as your previous setup}} {{notice| Warning| Provide the correct information when sending us an email for creating the new VHOST}} d2bcfb6a117ca8013284c3658e2e21d0c077c70b 1166 1165 2020-10-25T09:09:41Z Casper 39 Casper moved page [[Multiple instances]] to [[Running multiple websites]] wikitext text/x-wiki ==Setting up multiple instances on your website== When you finished setting up any CMS (e.g. WordPress, Joomla, Drupal, etc.), perhaps you want a second installation of a CMS on your website. For example: you have your main WordPress website running on the URL wordpress.com, but you also want another new WordPress site on second.wordpress.org . To do this you will need to follow a few steps: First of all, you will need to access one of our shell servers. For more information about how to do this, you can visit: [[Accessing your files]]. Continuing, we need to make a new directory in your homedir, next to the <code>www</code> folder where you placed the first installation of the CMS. It is possible to place the new directory inside your <code>www</code> folder, but we do not recommend this because it will be very confusing for later maintenance/updates. We also recommend to name this directory to something obvious (e.g. a directory named <code>wiki</code> for a wiki installation), this will help others in the future. Next, you will need to send us an email at ulyssis@ulyssis.org to make a VHOST for this new directory. The information you need to send us is: the '''path''' of the new directory and the '''domain''' you want this website to be on (e.g. wiki.wordpress.org). When you receive a reply back from us that everything is in order, you will need to follow the steps from https://docs.ulyssis.org/Setting_up_WordPress, https://docs.ulyssis.org/Setting_up_Joomla or https://docs.ulyssis.org/Setting_up_Drupal (depending on what CMS you want to install) again, and install the new website in the '''right''' directory. Here follows a list of things to be careful for when following all of these steps: {{notice| Warning| Make sure you install the new instance in the '''correct folder'''}} {{notice| Warning| Be careful when using the .htaccess file, as it may cause problem with multiple instances}} {{notice| Warning| When installing your new CMS, make sure you configure the setting properly for this installation as it will not be exactly the same as your previous setup}} {{notice| Warning| Provide the correct information when sending us an email for creating the new VHOST}} d2bcfb6a117ca8013284c3658e2e21d0c077c70b 1168 1166 2020-10-25T09:10:29Z Casper 39 /* Setting up multiple instances on your website */ wikitext text/x-wiki ==Setting up multiple websites== When you finished setting up any CMS (e.g. WordPress, Joomla, Drupal, etc.), perhaps you want a second installation of a CMS on your website. For example: you have your main WordPress website running on the URL wordpress.com, but you also want another new WordPress site on second.wordpress.org . To do this you will need to follow a few steps: First of all, you will need to access one of our shell servers. For more information about how to do this, you can visit: [[Accessing your files]]. Continuing, we need to make a new directory in your homedir, next to the <code>www</code> folder where you placed the first installation of the CMS. It is possible to place the new directory inside your <code>www</code> folder, but we do not recommend this because it will be very confusing for later maintenance/updates. We also recommend to name this directory to something obvious (e.g. a directory named <code>wiki</code> for a wiki installation), this will help others in the future. Next, you will need to send us an email at ulyssis@ulyssis.org to make a VHOST for this new directory. The information you need to send us is: the '''path''' of the new directory and the '''domain''' you want this website to be on (e.g. wiki.wordpress.org). When you receive a reply back from us that everything is in order, you will need to follow the steps from https://docs.ulyssis.org/Setting_up_WordPress, https://docs.ulyssis.org/Setting_up_Joomla or https://docs.ulyssis.org/Setting_up_Drupal (depending on what CMS you want to install) again, and install the new website in the '''right''' directory. Here follows a list of things to be careful for when following all of these steps: {{notice| Warning| Make sure you install the new instance in the '''correct folder'''}} {{notice| Warning| Be careful when using the .htaccess file, as it may cause problem with multiple instances}} {{notice| Warning| When installing your new CMS, make sure you configure the setting properly for this installation as it will not be exactly the same as your previous setup}} {{notice| Warning| Provide the correct information when sending us an email for creating the new VHOST}} 3811a08e2d3eab8566c1878031b87a1652702a1d 1169 1168 2020-10-25T09:17:01Z Casper 39 wikitext text/x-wiki ==Setting up multiple websites== When you finished setting up any CMS (e.g. WordPress, Joomla, Drupal, etc.), perhaps you want a second installation of a CMS on your website. For example: you have your main WordPress website running on the URL wordpress.com, but you also want another new WordPress site on second.wordpress.org . To do this you will need to follow a few steps: First of all, you will need to access one of our shell servers. For more information about how to do this, you can visit: [[Accessing your files]]. Continuing, we need to make a new directory in your homedir, next to the <code>www</code> folder where you placed the first installation of the CMS. It is possible to place the new directory inside your <code>www</code> folder, but we do not recommend this because it will be very confusing for later maintenance/updates. We also recommend to name this directory to something obvious (e.g. a directory named <code>wiki</code> for a wiki installation), this will help others in the future. Next, you will need to send us an email at ulyssis@ulyssis.org to connect the new directory to a subdomain. The information you need to send us is: the '''path''' (often this will look something like this: /home/user/<your_username>/<name_of_the_directory) of the new directory, and the '''subdomain''' you want this website to be on (e.g. wiki.wordpress.org). When you receive a reply back from us that everything is in order, you will need to follow the steps from https://docs.ulyssis.org/Setting_up_WordPress, https://docs.ulyssis.org/Setting_up_Joomla or https://docs.ulyssis.org/Setting_up_Drupal (depending on what CMS you want to install) again, and install the new website in the '''right''' directory. Here follows a list of things to be careful for when following all of these steps: {{notice| Warning| Make sure you install the new instance in the '''correct folder'''}} {{notice| Warning| Be careful when using the .htaccess file, as it may cause problem with multiple instances}} {{notice| Warning| When installing your new CMS, make sure you configure the setting properly for this installation as it will not be exactly the same as your previous setup}} {{notice| Warning| Provide the correct information when sending us an email for connecting the directory to the chosen subdomain}} e48ead8c93b7878ea2d6b192adb8817d99855773 1170 1169 2020-10-25T09:22:23Z Casper 39 wikitext text/x-wiki ==Setting up multiple websites== When you finished setting up any CMS (e.g. WordPress, Joomla, Drupal, etc.), perhaps you want a second installation of a CMS on your website. For example: you have your main WordPress website running on the URL wordpress.com, but you also want another new WordPress site on second.wordpress.org . To do this you will need to follow a few steps: First of all, you will need to access one of our shell servers. For more information about how to do this, you can visit: [[Accessing your files]]. Continuing, we need to make a new directory in your homedir, next to the <code>www</code> folder where you placed the first installation of the CMS. It is possible to place the new directory inside your <code>www</code> folder, but we do not recommend this because it will be very confusing for later maintenance/updates. We also recommend to name this directory to something obvious (e.g. a directory named <code>wiki</code> for a wiki installation), this will help others in the future. Next, you will need to send us an email at ulyssis@ulyssis.org to connect the new directory to a subdomain. The information you need to send us is: the '''path''' (often this will look something like this: /home/user/<your_username>/<name_of_the_directory) of the new directory, and the '''subdomain''' you want this website to be on (e.g. wiki.<your_website>.be). When you receive a reply back from us that everything is in order, you will need to follow the steps from https://docs.ulyssis.org/Setting_up_WordPress, https://docs.ulyssis.org/Setting_up_Joomla or https://docs.ulyssis.org/Setting_up_Drupal (depending on what CMS you want to install) again, and install the new website in the '''right''' directory. Here follows a list of things to be careful for when following all of these steps: {{notice| Warning| Make sure you install the new instance in the '''correct folder'''}} {{notice| Warning| Be careful when using the .htaccess file, as it may cause problem with multiple instances}} {{notice| Warning| When installing your new CMS, make sure you configure the setting properly for this installation as it will not be exactly the same as your previous setup}} {{notice| Warning| Provide the correct information when sending us an email for connecting the directory to the chosen subdomain}} e08b2307fce35f8d672f4d87e7c24a96c910e568 1171 1170 2020-10-25T09:23:54Z Casper 39 wikitext text/x-wiki ==Setting up multiple websites== When you finished setting up any CMS (e.g. WordPress, Joomla, Drupal, etc.), perhaps you want a second installation of a CMS on your website. For example: you have your main WordPress website running on the URL wordpress.com, but you also want another new WordPress site on second.wordpress.org . To do this you will need to follow a few steps: First of all, you will need to access one of our shell servers. For more information about how to do this, you can visit: [[Accessing your files]]. Continuing, we need to make a new directory in your homedir, next to the <code>www</code> folder where you placed the first installation of the CMS. It is possible to place the new directory inside your <code>www</code> folder, but we do not recommend this because it will be very confusing for later maintenance/updates. We also recommend to name this directory to something obvious (e.g. a directory named <code>wiki</code> for a wiki installation), this will help others in the future. Next, you will need to send us an email at ulyssis@ulyssis.org to connect the new directory to a subdomain. The information you need to send us is: the '''path''' (often this will look something like this: /home/user/<your_username>/<name_of_the_directory) of the new directory, and the '''subdomain''' you want this website to be on (e.g. wiki.<your_website>.be). When you receive a reply back from us that everything is in order, you will need to follow the steps from https://docs.ulyssis.org/Setting_up_WordPress, https://docs.ulyssis.org/Setting_up_Joomla or https://docs.ulyssis.org/Setting_up_Drupal (depending on what CMS you want to install) again, and install the new website in the '''right''' directory. Here follows a list of things to be careful for when following all of these steps: {{notice| Warning| Make sure you install the new instance in the '''correct folder'''}} {{notice| Warning| Be careful when using the .htaccess file, as it may cause problem with multiple installations}} {{notice| Warning| When installing your new CMS, make sure you configure the setting properly for this installation as it may not be exactly the same as your previous setup}} {{notice| Warning| Provide the correct information when sending us an email for connecting the directory to the chosen subdomain}} 0ada30b396fb939d7f2c04b79ec3bef9c95189bc 1172 1171 2020-10-25T17:09:52Z Casper 39 wikitext text/x-wiki ==Setting up multiple websites== When you finished setting up any CMS (e.g. WordPress, Joomla, Drupal, etc.), perhaps you want a second installation of a CMS on your website. For example: you have your main WordPress website running on the URL wordpress.com, but you also want another new WordPress site on second.wordpress.org . To do this you will need to follow a few steps: First of all, you will need to access one of our shell servers. For more information about how to do this, you can visit: [[Accessing your files]]. Continuing, we need to make a new directory in your homedir, next to the <code>www</code> folder where you placed the first installation of the CMS. It is possible to place the new directory inside your <code>www</code> folder, but we do not recommend this because it will be very confusing for later maintenance/updates. We also recommend to name this directory to something obvious (e.g. a directory named <code>wiki</code> for a wiki installation), this will help others in the future. Next, you will need to send us an email at ulyssis@ulyssis.org to connect the new directory to a subdomain. The information you need to send us is: the '''path''' (often this will look something like this: /home/user/<your_username>/<name_of_the_directory) of the new directory, and the '''subdomain''' you want this website to be on (e.g. wiki.<your_website>.be). When you receive a reply back from us that everything is in order, you will need to follow the steps from https://docs.ulyssis.org/Setting_up_WordPress, https://docs.ulyssis.org/Setting_up_Joomla or https://docs.ulyssis.org/Setting_up_Drupal (depending on what CMS you want to install) again, and install the new website in the '''right''' directory. Here follows a list of things you should be careful of when following all of these steps: {{notice| Warning| Make sure you install the new instance in the '''correct folder'''}} {{notice| Warning| Be careful when using the .htaccess file, as it may cause problem with multiple installations}} {{notice| Warning| When installing your new CMS, make sure you configure the setting properly for this installation as it may not be exactly the same as your previous setup}} {{notice| Warning| Provide the correct information when sending us an email for connecting the directory to the chosen subdomain}} e7cbd603f7bad09c0c173fb6ba33f23c669fccad 1173 1172 2020-10-25T23:06:43Z Casper 39 wikitext text/x-wiki ==Setting up multiple websites== When you finished setting up any CMS (e.g. WordPress, Joomla, Drupal, etc.), perhaps you want a second installation of a CMS on your website. For example: you have your main WordPress website running on the URL wordpress.com, but you also want another new WordPress site on second.yourorganization.be . To do this you will need to follow a few steps: First of all, you will need to access one of our shell servers. For more information about how to do this, you can visit: [[Accessing your files]]. Continuing, we need to make a new directory in your homedir, next to the <code>www</code> folder where you placed the first installation of the CMS. It is possible to place the new directory inside your <code>www</code> folder, but we do not recommend this because it will be very confusing for later maintenance/updates. We also recommend to name this directory to something obvious (e.g. a directory named <code>wiki</code> for a wiki installation), this will help others in the future. Next, you will need to send us an email at ulyssis@ulyssis.org to connect the new directory to a subdomain. The information you need to send us is: the '''path''' (often this will look something like this: /home/user/<your_username>/<name_of_the_directory) of the new directory, and the '''subdomain''' you want this website to be on (e.g. wiki.yourorganization.be). When you receive a reply back from us that everything is in order, you will need to follow the steps from https://docs.ulyssis.org/Setting_up_WordPress, https://docs.ulyssis.org/Setting_up_Joomla or https://docs.ulyssis.org/Setting_up_Drupal (depending on what CMS you want to install) again, and install the new website in the '''right''' directory. Here follows a list of things you should be careful of when following all of these steps: {{notice| Warning| Make sure you install the new instance in the '''correct folder'''}} {{notice| Warning| Be careful when using the .htaccess file, as it may cause problem with multiple installations}} {{notice| Warning| When installing your new CMS, make sure you configure the setting properly for this installation as it may not be exactly the same as your previous setup}} {{notice| Warning| Provide the correct information when sending us an email for connecting the directory to the chosen subdomain}} c995a93b4150f8ab1db297e23f0418657daee10f 1174 1173 2020-10-25T23:33:51Z Casper 39 wikitext text/x-wiki It's definitely possible to run multiple websites on a single ULYSSIS account. So you do not need to buy a new account to run a secondary website on. Very often this is used for running a wiki installation together with a wordpress installation, but in fact you can combine almost any CMS, software, etc. This is also called 'running multiple instances'. For example: you have your primary WordPress installation, but beside that you would also like a blog that runs on Joomla. By following this guide, you can make your WordPress run on yourorganization.be and a blog on blog.yourorganization.be So to run multiple installations on your website, you will need to follow a few easy steps: First of all, you will need to access one of our shell servers. For more information about how to do this, you can visit: [[Accessing your files]]. Continuing, we need to make a new directory in your homedir, next to the <code>www</code> folder where you placed the first installation of the CMS. It is possible to place the new directory inside your <code>www</code> folder, but we do not recommend this because it will be very confusing for later maintenance/updates. We also recommend to name this directory to something obvious (e.g. a directory named <code>wiki</code> for a wiki installation), this will help others in the future. Next, you will need to send us an email at ulyssis@ulyssis.org to connect the new directory to a subdomain. The information you need to send us is: the '''path''' (often this will look something like this: /home/user/<your_username>/<name_of_the_directory) of the new directory, and the '''subdomain''' you want this website to be on (e.g. wiki.yourorganization.be). When you receive a reply back from us that everything is in order, you will need to follow the steps from https://docs.ulyssis.org/Setting_up_WordPress, https://docs.ulyssis.org/Setting_up_Joomla or https://docs.ulyssis.org/Setting_up_Drupal (depending on what CMS you want to install) again, and install the new website in the '''right''' directory. Here follows a list of things you should be careful of when following all of these steps: {{notice| Warning| Make sure you install the new instance in the '''correct folder'''}} {{notice| Warning| Be careful when using the .htaccess file, as it may cause problem with multiple installations}} {{notice| Warning| When installing your new CMS, make sure you configure the setting properly for this installation as it may not be exactly the same as your previous setup}} {{notice| Warning| Provide the correct information when sending us an email for connecting the directory to the chosen subdomain}} 5bd70a21cd14fc5953ee1c22b823fcafc6a69112 0 87 1175 753 2020-11-01T12:25:48Z Bert 8 wikitext text/x-wiki Cron is a job scheduler, a utility that can be used to execute shell commands at specific points in time. These jobs are also called Cron jobs, and can be edited using the crontab command. ==The Crontab Command== To edit the cron table (crontab) file, you will use the crontab command. The crontab command has a few options: * <code>crontab -e</code>: Edit the crontab for the current user * <code>crontab -l</code>: List the cron jobs for the current user * <code>crontab -r</code>: Remove all cron jobs for the current user (Use the -i option to prompt before deleting) ===Editing The Crontab=== Perform these steps to edit the crontab. * Execute the <code>crontab -e</code> command * If this is the first time editing the crontab, a prompt will appear asking you to specify your text editor. If you don't know what to reply, we suggest you choose <code>nano</code>. * If everything is performed correctly, a file should appear. * You can edit this file. (Remember that everything after # is a comment) To add a new line to the file, you should follow this format: ┌───────────── minute (0 - 59) │ ┌───────────── hour (0 - 23) │ │ ┌───────────── day of month (1 - 31) │ │ │ ┌───────────── month (1 - 12) │ │ │ │ ┌───────────── day of week (0 - 6) (Sunday to Saturday; │ │ │ │ │ 7 is also Sunday) │ │ │ │ │ │ │ │ │ │ * * * * * command to execute You can use an asterisk (*) if a field does not matter. For example: <code>0 * * * * python somescript.py</code> will run <code>python somescript.py</code> every hour. <code>1 0 15 * 0 somecommand</code> will run <code>somecommand</code> every month the 15th day '''or''' if the day is a Sunday, at 1 past midnight (00:01). ==Real-life Example: Scheduling Drush Updates== Drush and Cron can be used to update Drupal automatically. * First, run the <code>crontab -e</code> command. More info can be found in the previous section. * Next, add the following line to the file: <code>0 0 * * * cd /path/to/your/drupal/folder/ && drush pm-update</code> This will execute the <code>cd /path/to/your/drupal/folder/</code> command, changing the current directory to your drupal folder, and the <code>drush pm-update</code> command, updating Drupal, every day, at midnight. The <code>&&</code> indicates a new command follows. * Finally, save and exit the file and you're good to go! [[Category:Shell]] 05210cc3636349a302ea4ea26d6fd11a6c11cd24 0 41 1176 1008 2020-11-06T23:23:52Z Bert 8 wikitext text/x-wiki ULYSSIS takes backups of all files, databases, settings and repositories 1-4 times a week. These backups can be restored in case of severe server failure or in case of an emergency (if for example a user by mistake deletes all of their site). An account holder who made a mistake and would like certain files restored can simply send us an email explaining what has happened, why certain files or folders need to be restored, when things went wrong, and finally list those files or folders. We will then try to find a suitable backup from before the date and time where things went wrong. Keep in mind that restoring backups is a slow process. It is therefore more convenient that users take their own backups when they do experiments on their account and then remove those backups once the experiments are done. == A backup of your files == You can use the methods described in [[Accessing your files]] to download a copy of all of your files or specific folders you will be working on. If something goes wrong, you can easily restore files to a previous state by re-uploading those you have downloaded and saved. == A backup of your databases == To take a backup of your database you simply use the export function of PHPMyAdmin, PHPPgAdmin and/or Adminer as described on [[Using PHPMyAdmin]], [[Using PHPPgAdmin]] and [[Using Adminer]]. If you are backing up and/or restoring a larger database, it's advisable to use command line tools since they are more performant than the web-based tools and don't have any timeouts that could interrupt your backup/restore. === MySQL command line === To take a backup, execute the following command on one of our shellservers (with the right database name filled in): mysqldump -h mysql.ulyssis.org -p username_database > backup.sql This will prompt you for your database password (please refer to [[Using MySQL]] if you don't know your password) and then dump the entire database to backup.sql file as SQL. To restore your backup you can use the mysql command on one of our shellservers (with the right database name filled in), whatever SQL file you specify will be executed: mysql -h mysql.ulyssis.org -p username_database < backup.sql Please keep in mind that by default mysqldump includes statements in the SQL file that will delete all tables that will be restored. If you wish to have more control over different settings when taking or restoring please, you can refer to the respective man pages of mysqldump and mysql using <code>man mysqldump</code> and <code>man mysql</code> === PostgreSQL command line === To take a backup, execute the following command on one of our shellservers (with the right database name filled in): pg_dump -h pgsql.ulyssis.org -W --clean username_database > backup.sql This will prompt you for your database password (please refer to [[Using PostgreSQL]] if you don't know your password) and then dump the entire database to backup.sql file as SQL with COPY statements. If you prefer INSERT instead of COPY statements, you can add <code>--inserts</code> to your command. To restore your backup you can use the pg_restore command on one of our shellservers (with the right database name filled in), whatever SQL file you specify will be executed: psql -h pgsql.ulyssis.org -W username_database < backup.sql Please keep in mind that because we specified <code>--clean</code> earlier, our SQL file includes statements that will delete all tables, sequences, functions and schemas that will be restored. If you wish to have more control over different settings when taking or restoring please, you can refer to the respective man pages of pg_dump and psql using <code>man pg_dump</code> and <code>man psql</code> [[Category:Files]] [[Category:Databases]] 849652ec0ac91620549d3d8404bca3761bb7c2f3 0 19 1177 976 2020-11-07T12:45:00Z Bert 8 /* Advanced */ wikitext text/x-wiki Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mailbox regularly, because all important information will be sent to this address. You can check your e-mail using webmail or an email client of your own. It is also possible to configure your email address in UCC to automatically [[Forwarders|forward]] all correspondence to another address. ==Webmail== You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to login. ==POP and IMAP access== You can access your ulyssis mail with POP or IMAP. The configuration parameters are: * '''server''': <code>mail.ulyssis.org</code> * '''username''': ''your ULYSSIS username'' * '''password''': ''your ULYSSIS password'' * '''security''': SSL ==SMTP== ULYSSIS doesn't offer SMTP. Instead, you can use KULeuven's SMTP server: * '''server''': <code>smtps.kuleuven.be</code> * '''port''': 443 * '''username''': ''your student id'' * '''password''': ''your KULeuven password'' * '''security''': SSL == Advanced == Your emails are stored within your account under ~/Maildir. These files can of course be read with a command line email client such as alpine or mutt. We support sendmail style local delivery using .forward. More information is available in the official documentation of [https://www.sendmail.org/~ca/email/doc8.9/op-sh-2.html#sh-2.8 Sendmail] and [http://www.postfix.org/local.8.html Postfix]. While it's possible to use .forward to simply forward email to other addresses, we recommend only using it when the same feature is not available through our control panel [https://ucc.ulyssis.org UCC]. Specifically, .forward can be used to pass emails to other applications. In the past, a popular application to pass email through was procmail. However, procmail has not seen development for about 2 decades, and its developer suggest not using it anymore. So while some users may find procmail filters useful, we do not support or suggest its use anymore. A detailed manual for procmail is available on the [https://wiki.archlinux.org/index.php/Procmail ArchWiki]. [[Category:Mail]] 1af3468e2edda151edf1e4311f9e855829689f44 1178 1177 2020-11-07T15:10:22Z Bert 8 wikitext text/x-wiki Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mailbox regularly, because all important information will be sent to this address. You can check your e-mail using webmail or an email client of your own. It is also possible to configure your email address in UCC to automatically [[Forwarders|forward]] all correspondence to another address. ==Webmail== You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to login. ==POP and IMAP access== You can access your ulyssis mail with POP or IMAP. The configuration parameters are: * '''server''': <code>mail.ulyssis.org</code> * '''username''': ''your ULYSSIS username'' * '''password''': ''your ULYSSIS password'' * '''security''': SSL ==SMTP== ULYSSIS doesn't offer SMTP. Instead, you can use KULeuven's SMTP server: * '''server''': <code>smtps.kuleuven.be</code> * '''port''': 443 * '''username''': ''your student id'' * '''password''': ''your KULeuven password'' * '''security''': SSL == Advanced == Your emails are stored within your account under ~/Maildir. These files can of course be read with a command line email client such as alpine or mutt. We support sendmail style local delivery using .forward. More information is available in the official documentation of [https://www.sendmail.org/~ca/email/doc8.9/op-sh-2.html#sh-2.8 Sendmail] and [http://www.postfix.org/local.8.html Postfix]. While it's possible to use .forward to simply forward email to other addresses, we recommend only using it when the same feature is not available through our control panel [https://ucc.ulyssis.org UCC]. Specifically, .forward can be used to pass emails to other applications. In the past, a popular application to pass email through was procmail. However, procmail has not seen development for about 2 decades, and its developer suggests not using it anymore. So while some users may find procmail filters useful, we do not support or suggest its use anymore. A detailed manual for procmail is available on the [https://wiki.archlinux.org/index.php/Procmail ArchWiki]. [[Category:Mail]] ce660441406c58defb7ebc41e62d548d663dfaf8 0 47 1179 778 2020-11-09T01:41:48Z Thomasd 40 /* Setup your wiki */ wikitext text/x-wiki This page will go through a basic setup of MediaWiki. It is based on [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wikipage], and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. This tutorial we'll use a ULYSSIS-account with username "me". == Putting setup-files in place == First we'll have to download the setup file which you can find over at [http://www.mediawiki.org/wiki/Download the official MediaWiki website]. It's an archived file, so you need to extract it first and put the files in a subdirectory of your "document root". The default is just a www directory in your home folder. Putting your files in document_root/wiki/ will make your wiki be located at usersname.ulyssis.be/wiki/. If you prefer, you can do this all graphically using the manual [[Accessing_your_files]]. If you prefer the command line; <pre> homeuser@home:~$ ssh me@ssh1.ulyssis.org enter super secret password: me@zap:~$ wget http://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.6.tar.gz me@zap:~$ tar xvxf mediawiki-1.23.6.tar.gz me@zap:~$ mv mediawiki-1.23.6 www/wiki me@zap:~$ rm -r mediawiki-1.23.6.tar.gz </pre> ==Setting up database== Like the [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wiki] tells us, we have three different options to choose from; PostgreSQL, MySQL and SQLite. It's easy to set a PostgreSQL or MySQL database; just go to the UCC. For this tutorial we will continue with a MySQL database (PostgreSQL installation steps are quite similar). Let us visit https://ucc.ulyssis.org/mysql; if this is your first time using MySQL you'll need to create a new account by putting in a super secret password. The wizard will create your MySQL account with the same name as your user-account. We'll also create a new database with an appropriate name by clicking on 'Add database'. In this tutorial we will choose; "wiki", notice that it will be prepended with our username, so we'll end up with a new database named "me_wiki". ==Setup your wiki== If all went well, you can access your website at http://username.ulyssis.be/the_folder_you_used and start the setup wizard. In our example, will surf to http://me.ulyssis.be/wiki. The wizard will guide you through some configuration options. Most of them our pretty straight-forward. When in doubt, you can always click the question mark wich will show you some sensible and recommended default... We'll just discuss the page were the wizard asks you for the database. In our example; <pre> Database host: mysql.ulyssis.org Database name: me_wiki // The name of our database; i.e. the name we chose, prepended by our username. Database table prefix: // We can leave this blank. Database user: me // This is the name of our MySQL-user, which was named after our ULYSSIS-username. Database password: supersecretpassword // Please note that this is not your ULYSSIS-password, but the password you used in UCC when creating the MySQL user! </pre> ==Creating the wiki== After the setup wizard is complete, you can begin the installation procedure. If all went well, you'll be greeted by a page which congratulates you with your new installation. ==Finishing up installation== The setup will offer you a configuration file (containing some settings you specified) that you need to download to your server (more specifically in directory where your MediaWiki-files reside in). You again can do this graphically, or if you prefer a terminal; <pre> homeuser@home:~$ scp path_to_file/LocalSettings.php me@ssh1.ulyssis.org:~/www/wiki enter super secret password: </pre> After this is done, you can finally start using your wiki. Please refer to [http://www.mediawiki.org/wiki/MediaWiki the original MediaWiki documentation] for a more detailed or advanced information. == Extending MediaWiki == By default, every MediaWiki installation looks and works identical. While that is convenient for users, it can be less than ideal if you need specific functionality or wish to adapt your wiki to your style. === Extensions === Extensions add functionality to a wiki, such as more fine-grained authentication, extra layout elements for articles or text filters. An overview of what kinds of extensions are possible can be found on [https://www.mediawiki.org/wiki/Manual:Extensions the official manual]. Some noteworthy extensions can be used to prevent spam or unauthorised access. You can find more information on [[Preventing spam on MediaWiki]] and [[Securing MediaWiki using Centrale KU Leuven Login]]. We've also found that users sometimes have problems with high amounts of disk space usage. To help those users out, we've developed a MediaWiki extension that can automatically reduce file size of new uploads. Specifically it's possible to compress PDFs, convert inefficient image formats such as BMP and TIFF to PNG, loslessly compress PNG, lossy compress JPG, resize images and strip EXIF data. You can find more details on https://github.com/ULYSSIS-KUL/CompressUploads === Skins === Skins are similar to themes, templates or styles within other software. By default MediaWiki uses the well known Vector skin. But other skins are available. Sadly, MediaWiki doesn't maintain a complete list of all available skins and whether they work with recent releases, so it may take a bit of perseverance. General information on Skins is available on the [https://www.mediawiki.org/wiki/Manual:Skins Official Manual]. Besides that there's the [https://www.mediawiki.org/wiki/Manual:Gallery_of_user_styles the user style gallery] and [https://www.mediawiki.org/wiki/Category:All_skins the list of skins]. [[Category:CMSs]] 145d673be58d533c4e8d6f556fe46af1a457f65c 0 10 1184 1183 2020-11-19T11:37:38Z Yoa 30 /* Let's Encrypt */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty consultative bodies (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request, the following steps have to be performed: * Set up the site that needs SSL if that's not already the case * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Make sure our nameservers are being used for the involved domain(s), as explained on [[Adding domain names]] * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir -p ~/letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain (the CA file) ├── mydomain.be.crt (the cert file; "public key") └── mydomain.be.key (the key file; "private key") If you already possess the necessary files, renaming and copying them accordingly is sufficient. '''You still have to email us to install your certificate.''' More information in the last section on this page. Otherwise, you can generate or renew your certificates using acme.sh. This is explained in the next section. ==== Generating certificates ==== {{notice|If you use a <code>.htaccess</code> file in the webroot of the domain name, make sure to add the following lines at the top of the file:|<pre><IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule></pre>}} Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll show how to use the acme.sh program to generate certificates on the ULYSSIS servers. Firstly, execute the following commands to download the acme.sh script in your home directory and make it executable: curl -o ~/acme.sh https://raw.githubusercontent.com/acmesh-official/acme.sh/master/acme.sh chmod +x ~/acme.sh Next, determine for which domains and subdomains you want to generate a certificate. You will need to generate a single certificate for each domain and subdomain which points to the same folder on your account (in most cases this is <code>www</code> in your home directory). The following example command will generate a certificate for <code>mydomain.be</code> and <code>www.mydomain.be</code> which points to the <code>www</code> folder in the home directory. '''Change the parameters''' as explained below before executing this command! ~/acme.sh --issue --cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt --key-file ~/letsencrypt/mydomain.be/mydomain.be.key --ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain -m "email@mydomain.be" -w ~/www -d mydomain.be -d www.mydomain.be The explanation of these many parameters is as follows: * <code>--issue</code> tells acme.sh to generate a new certificate. * <code>--cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt</code> tells acme.sh to store the certificate file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. '''This folder should already exist''', please refer to the previous section if you have not created this folder yet. * <code>--key-file ~/letsencrypt/mydomain.be/mydomain.be.key</code> tells acme.sh to store the key file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>--ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain</code> tells acme.sh to store the CA file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>-m "email@mydomain.be"</code> tells acme.sh the email address associated with the certificate. Let's Encrypt will remind this email address (if provided) when the certificate is close to expiring. * <code>-w ~/www</code> tells acme.sh where the domains in this certificate point to. Make sure to change the <code>www</code> part if the domains point to a different folder in your home directory. * <code>-d mydomain.be</code> and <code>-d www.mydomain.be</code> tell acme.sh that the certificate should protect <code>mydomain.be</code> and <code>www.mydomain.be</code>. You should '''add all domain names''' pointing to the <code>-w</code> folder. '''After generating the certificate, you have to email us to install your new certificate.''' More information in the last section on this page. ==== Renewing certificates ==== To renew the certificates of <code>mydomain.be</code>, just execute: ~/acme.sh --renew -d mydomain.be The renewed certificates will automatically be copied to the files you provided in the command to generate the certificates (see previous section). '''After renewing the certificate, you have to email us to install your certificate.''' More information in the last section on this page. ==== Installing the certificates ==== Check whether everything is stored correctly by executing the following command: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL, so make sure you follow this procedure carefully. [[Category:Webserver]] 3dcc94f7e63c5307640ab2de62059c869698dd7c 1185 1184 2020-11-19T11:40:10Z Yoa 30 /* Generating certificates */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty consultative bodies (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request, the following steps have to be performed: * Set up the site that needs SSL if that's not already the case * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Make sure our nameservers are being used for the involved domain(s), as explained on [[Adding domain names]] * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir -p ~/letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain (the CA file) ├── mydomain.be.crt (the cert file; "public key") └── mydomain.be.key (the key file; "private key") If you already possess the necessary files, renaming and copying them accordingly is sufficient. '''You still have to email us to install your certificate.''' More information in the last section on this page. Otherwise, you can generate or renew your certificates using acme.sh. This is explained in the next section. ==== Generating certificates ==== {{notice|If you use a <code>.htaccess</code> file in the webroot of the domain name, make sure to add the following lines at the top of the file:|<pre><IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule></pre>}} Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll show how to use the acme.sh program to generate certificates on the ULYSSIS servers. '''If you already followed this section to generate certificates, skip to the next section on renewing certificates.''' Firstly, execute the following commands to download the acme.sh script in your home directory and make it executable: curl -o ~/acme.sh https://raw.githubusercontent.com/acmesh-official/acme.sh/master/acme.sh chmod +x ~/acme.sh Next, determine for which domains and subdomains you want to generate a certificate. You will need to generate a single certificate for each domain and subdomain which points to the same folder on your account (in most cases this is <code>www</code> in your home directory). The following example command will generate a certificate for <code>mydomain.be</code> and <code>www.mydomain.be</code> which points to the <code>www</code> folder in the home directory. '''Change the parameters''' as explained below before executing this command! ~/acme.sh --issue --cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt --key-file ~/letsencrypt/mydomain.be/mydomain.be.key --ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain -m "email@mydomain.be" -w ~/www -d mydomain.be -d www.mydomain.be The explanation of these many parameters is as follows: * <code>--issue</code> tells acme.sh to generate a new certificate. * <code>--cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt</code> tells acme.sh to store the certificate file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. '''This folder should already exist''', please refer to the previous section if you have not created this folder yet. * <code>--key-file ~/letsencrypt/mydomain.be/mydomain.be.key</code> tells acme.sh to store the key file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>--ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain</code> tells acme.sh to store the CA file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>-m "email@mydomain.be"</code> tells acme.sh the email address associated with the certificate. Let's Encrypt will remind this email address (if provided) when the certificate is close to expiring. * <code>-w ~/www</code> tells acme.sh where the domains in this certificate point to. Make sure to change the <code>www</code> part if the domains point to a different folder in your home directory. * <code>-d mydomain.be</code> and <code>-d www.mydomain.be</code> tell acme.sh that the certificate should protect <code>mydomain.be</code> and <code>www.mydomain.be</code>. You should '''add all domain names''' pointing to the <code>-w</code> folder. '''After generating the certificate, you have to email us to install your new certificate.''' More information in the last section on this page. ==== Renewing certificates ==== To renew the certificates of <code>mydomain.be</code>, just execute: ~/acme.sh --renew -d mydomain.be The renewed certificates will automatically be copied to the files you provided in the command to generate the certificates (see previous section). '''After renewing the certificate, you have to email us to install your certificate.''' More information in the last section on this page. ==== Installing the certificates ==== Check whether everything is stored correctly by executing the following command: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL, so make sure you follow this procedure carefully. [[Category:Webserver]] 0b21d5333c6f76f44b9a44803c8156dc176c2bd0 1186 1185 2020-11-19T11:42:58Z Yoa 30 /* Generating certificates */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty consultative bodies (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request, the following steps have to be performed: * Set up the site that needs SSL if that's not already the case * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Make sure our nameservers are being used for the involved domain(s), as explained on [[Adding domain names]] * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir -p ~/letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain (the CA file) ├── mydomain.be.crt (the cert file; "public key") └── mydomain.be.key (the key file; "private key") If you already possess the necessary files, renaming and copying them accordingly is sufficient. '''You still have to email us to install your certificate.''' More information in the last section on this page. Otherwise, you can generate or renew your certificates using acme.sh. This is explained in the next section. ==== Generating certificates ==== {{notice|If you use a <code>.htaccess</code> file in the webroot of the domain name, make sure to add the following lines at the top of the file:|<pre><IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule></pre>}} Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll show how to use the acme.sh program to generate certificates on the ULYSSIS servers. '''If you already followed this section to generate certificates, skip to the next section on renewing certificates.''' Firstly, execute the following commands to download the acme.sh script in your home directory and make it executable: curl -o ~/acme.sh https://raw.githubusercontent.com/acmesh-official/acme.sh/master/acme.sh chmod +x ~/acme.sh Next, determine for which domains and subdomains you want to generate a certificate. You will need to generate a single certificate for each domain and subdomain which points to the same folder on your account (in most cases this is <code>www</code> in your home directory). The following example command will generate a certificate for <code>mydomain.be</code> and <code>www.mydomain.be</code> which points to the <code>www</code> folder in the home directory. '''Change the parameters''' as explained below before executing this command! ~/acme.sh --issue --cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt --key-file ~/letsencrypt/mydomain.be/mydomain.be.key --ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain -m "email@mydomain.be" -w ~/www -d mydomain.be -d www.mydomain.be The explanation of these many parameters is as follows: * <code>--issue</code> tells acme.sh to generate a new certificate. * <code>--cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt</code> tells acme.sh to store the certificate file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. '''This folder should already exist''', please refer to the previous section if you have not created this folder yet. * <code>--key-file ~/letsencrypt/mydomain.be/mydomain.be.key</code> tells acme.sh to store the key file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>--ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain</code> tells acme.sh to store the CA file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>-m "email@mydomain.be"</code> tells acme.sh the email address associated with the certificate. Let's Encrypt will remind this email address (if provided) when the certificate is close to expiring. * <code>-w ~/www</code> tells acme.sh where the domains in this certificate point to. Make sure to change the <code>www</code> part if the domains point to a different folder in your home directory. * <code>-d mydomain.be</code> and <code>-d www.mydomain.be</code> tell acme.sh that the certificate should protect <code>mydomain.be</code> and <code>www.mydomain.be</code>. You should '''add all domain names''' pointing to the <code>-w</code> folder. After executing this command with the right parameters, your certificate should be generated successfully. When you have to renew the certificate in the future, you should follow the instructions in the next section. '''Don't forget to email us to install your new certificate.''' More information in the last section on this page. ==== Renewing certificates ==== To renew the certificates of <code>mydomain.be</code>, just execute: ~/acme.sh --renew -d mydomain.be The renewed certificates will automatically be copied to the files you provided in the command to generate the certificates (see previous section). '''After renewing the certificate, you have to email us to install your certificate.''' More information in the last section on this page. ==== Installing the certificates ==== Check whether everything is stored correctly by executing the following command: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL, so make sure you follow this procedure carefully. [[Category:Webserver]] 59ba26b322137daf8991e70327e4c5c22cc0ed2d 1187 1186 2020-11-19T11:43:25Z Yoa 30 /* Renewing certificates */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty consultative bodies (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request, the following steps have to be performed: * Set up the site that needs SSL if that's not already the case * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Make sure our nameservers are being used for the involved domain(s), as explained on [[Adding domain names]] * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir -p ~/letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain (the CA file) ├── mydomain.be.crt (the cert file; "public key") └── mydomain.be.key (the key file; "private key") If you already possess the necessary files, renaming and copying them accordingly is sufficient. '''You still have to email us to install your certificate.''' More information in the last section on this page. Otherwise, you can generate or renew your certificates using acme.sh. This is explained in the next section. ==== Generating certificates ==== {{notice|If you use a <code>.htaccess</code> file in the webroot of the domain name, make sure to add the following lines at the top of the file:|<pre><IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule></pre>}} Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll show how to use the acme.sh program to generate certificates on the ULYSSIS servers. '''If you already followed this section to generate certificates, skip to the next section on renewing certificates.''' Firstly, execute the following commands to download the acme.sh script in your home directory and make it executable: curl -o ~/acme.sh https://raw.githubusercontent.com/acmesh-official/acme.sh/master/acme.sh chmod +x ~/acme.sh Next, determine for which domains and subdomains you want to generate a certificate. You will need to generate a single certificate for each domain and subdomain which points to the same folder on your account (in most cases this is <code>www</code> in your home directory). The following example command will generate a certificate for <code>mydomain.be</code> and <code>www.mydomain.be</code> which points to the <code>www</code> folder in the home directory. '''Change the parameters''' as explained below before executing this command! ~/acme.sh --issue --cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt --key-file ~/letsencrypt/mydomain.be/mydomain.be.key --ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain -m "email@mydomain.be" -w ~/www -d mydomain.be -d www.mydomain.be The explanation of these many parameters is as follows: * <code>--issue</code> tells acme.sh to generate a new certificate. * <code>--cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt</code> tells acme.sh to store the certificate file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. '''This folder should already exist''', please refer to the previous section if you have not created this folder yet. * <code>--key-file ~/letsencrypt/mydomain.be/mydomain.be.key</code> tells acme.sh to store the key file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>--ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain</code> tells acme.sh to store the CA file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>-m "email@mydomain.be"</code> tells acme.sh the email address associated with the certificate. Let's Encrypt will remind this email address (if provided) when the certificate is close to expiring. * <code>-w ~/www</code> tells acme.sh where the domains in this certificate point to. Make sure to change the <code>www</code> part if the domains point to a different folder in your home directory. * <code>-d mydomain.be</code> and <code>-d www.mydomain.be</code> tell acme.sh that the certificate should protect <code>mydomain.be</code> and <code>www.mydomain.be</code>. You should '''add all domain names''' pointing to the <code>-w</code> folder. After executing this command with the right parameters, your certificate should be generated successfully. When you have to renew the certificate in the future, you should follow the instructions in the next section. '''Don't forget to email us to install your new certificate.''' More information in the last section on this page. ==== Renewing certificates ==== To renew the certificates of <code>mydomain.be</code>, just execute: ~/acme.sh --renew -d mydomain.be The renewed certificates will automatically be copied to the files you provided in the command to generate the certificates (see previous section). '''After renewing the certificate, you have to email us to install your certificate.''' More information in the next section. ==== Installing the certificates ==== Check whether everything is stored correctly by executing the following command: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL, so make sure you follow this procedure carefully. [[Category:Webserver]] 29a8b2b6f564b3cb2d2bb5d51a044f962e026af6 1188 1187 2020-11-19T11:58:14Z Yoa 30 /* Renewing certificates */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty consultative bodies (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request, the following steps have to be performed: * Set up the site that needs SSL if that's not already the case * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Make sure our nameservers are being used for the involved domain(s), as explained on [[Adding domain names]] * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir -p ~/letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain (the CA file) ├── mydomain.be.crt (the cert file; "public key") └── mydomain.be.key (the key file; "private key") If you already possess the necessary files, renaming and copying them accordingly is sufficient. '''You still have to email us to install your certificate.''' More information in the last section on this page. Otherwise, you can generate or renew your certificates using acme.sh. This is explained in the next section. ==== Generating certificates ==== {{notice|If you use a <code>.htaccess</code> file in the webroot of the domain name, make sure to add the following lines at the top of the file:|<pre><IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule></pre>}} Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll show how to use the acme.sh program to generate certificates on the ULYSSIS servers. '''If you already followed this section to generate certificates, skip to the next section on renewing certificates.''' Firstly, execute the following commands to download the acme.sh script in your home directory and make it executable: curl -o ~/acme.sh https://raw.githubusercontent.com/acmesh-official/acme.sh/master/acme.sh chmod +x ~/acme.sh Next, determine for which domains and subdomains you want to generate a certificate. You will need to generate a single certificate for each domain and subdomain which points to the same folder on your account (in most cases this is <code>www</code> in your home directory). The following example command will generate a certificate for <code>mydomain.be</code> and <code>www.mydomain.be</code> which points to the <code>www</code> folder in the home directory. '''Change the parameters''' as explained below before executing this command! ~/acme.sh --issue --cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt --key-file ~/letsencrypt/mydomain.be/mydomain.be.key --ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain -m "email@mydomain.be" -w ~/www -d mydomain.be -d www.mydomain.be The explanation of these many parameters is as follows: * <code>--issue</code> tells acme.sh to generate a new certificate. * <code>--cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt</code> tells acme.sh to store the certificate file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. '''This folder should already exist''', please refer to the previous section if you have not created this folder yet. * <code>--key-file ~/letsencrypt/mydomain.be/mydomain.be.key</code> tells acme.sh to store the key file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>--ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain</code> tells acme.sh to store the CA file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>-m "email@mydomain.be"</code> tells acme.sh the email address associated with the certificate. Let's Encrypt will remind this email address (if provided) when the certificate is close to expiring. * <code>-w ~/www</code> tells acme.sh where the domains in this certificate point to. Make sure to change the <code>www</code> part if the domains point to a different folder in your home directory. * <code>-d mydomain.be</code> and <code>-d www.mydomain.be</code> tell acme.sh that the certificate should protect <code>mydomain.be</code> and <code>www.mydomain.be</code>. You should '''add all domain names''' pointing to the <code>-w</code> folder. After executing this command with the right parameters, your certificate should be generated successfully. When you have to renew the certificate in the future, you should follow the instructions in the next section. '''Don't forget to email us to install your new certificate.''' More information in the last section on this page. ==== Renewing certificates ==== To renew the certificates of <code>mydomain.be</code>, just execute: ~/acme.sh --renew -d mydomain.be For the <code>-d</code> parameter, you have to provide the '''first''' domain name you provided when generating the certificate (in the previous section, this was <code>mydomain.be</code>. If you are not sure which domain name to use, you can execute the command: ~/acme.sh --list This will generate a list of available certificates, which looks a bit like this: Main_Domain KeyLength SAN_Domains CA Created Renew mydomain.be "" www.mydomain.be LetsEncrypt.org ... ... In this example, the main domain is <code>mydomain.be</code>. The renewed certificates will automatically be copied to the files you provided in the command to generate the certificates (see previous section). '''After renewing the certificate, you have to email us to install your certificate.''' More information in the next section. ==== Installing the certificates ==== Check whether everything is stored correctly by executing the following command: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL, so make sure you follow this procedure carefully. [[Category:Webserver]] 0f52fb48a4344560390d3329d217ec85832aec0e 1189 1188 2020-11-19T11:58:56Z Yoa 30 /* Renewing certificates */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty consultative bodies (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request, the following steps have to be performed: * Set up the site that needs SSL if that's not already the case * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Make sure our nameservers are being used for the involved domain(s), as explained on [[Adding domain names]] * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir -p ~/letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain (the CA file) ├── mydomain.be.crt (the cert file; "public key") └── mydomain.be.key (the key file; "private key") If you already possess the necessary files, renaming and copying them accordingly is sufficient. '''You still have to email us to install your certificate.''' More information in the last section on this page. Otherwise, you can generate or renew your certificates using acme.sh. This is explained in the next section. ==== Generating certificates ==== {{notice|If you use a <code>.htaccess</code> file in the webroot of the domain name, make sure to add the following lines at the top of the file:|<pre><IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule></pre>}} Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll show how to use the acme.sh program to generate certificates on the ULYSSIS servers. '''If you already followed this section to generate certificates, skip to the next section on renewing certificates.''' Firstly, execute the following commands to download the acme.sh script in your home directory and make it executable: curl -o ~/acme.sh https://raw.githubusercontent.com/acmesh-official/acme.sh/master/acme.sh chmod +x ~/acme.sh Next, determine for which domains and subdomains you want to generate a certificate. You will need to generate a single certificate for each domain and subdomain which points to the same folder on your account (in most cases this is <code>www</code> in your home directory). The following example command will generate a certificate for <code>mydomain.be</code> and <code>www.mydomain.be</code> which points to the <code>www</code> folder in the home directory. '''Change the parameters''' as explained below before executing this command! ~/acme.sh --issue --cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt --key-file ~/letsencrypt/mydomain.be/mydomain.be.key --ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain -m "email@mydomain.be" -w ~/www -d mydomain.be -d www.mydomain.be The explanation of these many parameters is as follows: * <code>--issue</code> tells acme.sh to generate a new certificate. * <code>--cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt</code> tells acme.sh to store the certificate file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. '''This folder should already exist''', please refer to the previous section if you have not created this folder yet. * <code>--key-file ~/letsencrypt/mydomain.be/mydomain.be.key</code> tells acme.sh to store the key file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>--ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain</code> tells acme.sh to store the CA file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>-m "email@mydomain.be"</code> tells acme.sh the email address associated with the certificate. Let's Encrypt will remind this email address (if provided) when the certificate is close to expiring. * <code>-w ~/www</code> tells acme.sh where the domains in this certificate point to. Make sure to change the <code>www</code> part if the domains point to a different folder in your home directory. * <code>-d mydomain.be</code> and <code>-d www.mydomain.be</code> tell acme.sh that the certificate should protect <code>mydomain.be</code> and <code>www.mydomain.be</code>. You should '''add all domain names''' pointing to the <code>-w</code> folder. After executing this command with the right parameters, your certificate should be generated successfully. When you have to renew the certificate in the future, you should follow the instructions in the next section. '''Don't forget to email us to install your new certificate.''' More information in the last section on this page. ==== Renewing certificates ==== To renew the certificates of <code>mydomain.be</code>, just execute: ~/acme.sh --renew -d mydomain.be For the <code>-d</code> parameter, you have to provide the '''first''' domain name you provided when generating the certificate (in the previous section, this was <code>mydomain.be</code>. If you are not sure which domain name to use, you can execute the command: ~/acme.sh --list This will generate a list of available certificates, which looks a bit like this: Main_Domain KeyLength SAN_Domains CA Created Renew mydomain.be "" www.mydomain.be LetsEncrypt.org ... ... ... ... ... ... ... ... In this example, the main domain is <code>mydomain.be</code>. The renewed certificates will automatically be copied to the files you provided in the command to generate the certificates (see previous section). '''After renewing the certificate, you have to email us to install your certificate.''' More information in the next section. ==== Installing the certificates ==== Check whether everything is stored correctly by executing the following command: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL, so make sure you follow this procedure carefully. [[Category:Webserver]] c6f69367fa6a3c4bff41cfc11f6e979ed72633a3 1190 1189 2020-11-19T12:00:07Z Yoa 30 /* Generating certificates */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty consultative bodies (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request, the following steps have to be performed: * Set up the site that needs SSL if that's not already the case * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Make sure our nameservers are being used for the involved domain(s), as explained on [[Adding domain names]] * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir -p ~/letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain (the CA file) ├── mydomain.be.crt (the cert file; "public key") └── mydomain.be.key (the key file; "private key") If you already possess the necessary files, renaming and copying them accordingly is sufficient. '''You still have to email us to install your certificate.''' More information in the last section on this page. Otherwise, you can generate or renew your certificates using acme.sh. This is explained in the next section. ==== Generating certificates ==== {{notice|If you use a <code>.htaccess</code> file in the webroot of the domain name, make sure to add the following lines at the top of the file:|<pre><IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule></pre>}} Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll show how to use the acme.sh program to generate certificates on the ULYSSIS servers. '''If you already followed this section to generate certificates, skip to the next section on renewing certificates.''' Firstly, execute the following commands to download the acme.sh script in your home directory and make it executable: curl -o ~/acme.sh https://raw.githubusercontent.com/acmesh-official/acme.sh/master/acme.sh chmod +x ~/acme.sh Next, determine for which domains and subdomains you want to generate a certificate. You will need to generate a single certificate for each domain and subdomain which points to the same folder on your account (in most cases this is <code>www</code> in your home directory). The following example command will generate a certificate for <code>mydomain.be</code> and <code>www.mydomain.be</code> which points to the <code>www</code> folder in the home directory. '''Change the parameters''' as explained below before executing this command! ~/acme.sh --issue --cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt --key-file ~/letsencrypt/mydomain.be/mydomain.be.key --ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain -m "email@mydomain.be" -w ~/www -d mydomain.be -d www.mydomain.be The explanation of these many parameters is as follows: * <code>--issue</code> tells acme.sh to generate a new certificate. * <code>--cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt</code> tells acme.sh to store the certificate file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. '''This folder should already exist''', please refer to the previous section if you have not created this folder yet. * <code>--key-file ~/letsencrypt/mydomain.be/mydomain.be.key</code> tells acme.sh to store the key file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>--ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain</code> tells acme.sh to store the CA file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>-m "email@mydomain.be"</code> tells acme.sh the email address associated with the certificate. Let's Encrypt will remind this email address (if provided) when the certificate is close to expiring. * <code>-w ~/www</code> tells acme.sh where the domains in this certificate point to. Make sure to change the <code>www</code> part if the domains point to a different folder in your home directory. * <code>-d mydomain.be</code> and <code>-d www.mydomain.be</code> tell acme.sh that the certificate should protect <code>mydomain.be</code> and <code>www.mydomain.be</code>. The first domain name will be the "main domain", which is important for renewing. You should '''add all domain names''' pointing to the <code>-w</code> folder. After executing this command with the right parameters, your certificate should be generated successfully. When you have to renew the certificate in the future, you should follow the instructions in the next section. '''Don't forget to email us to install your new certificate.''' More information in the last section on this page. ==== Renewing certificates ==== To renew the certificates of <code>mydomain.be</code>, just execute: ~/acme.sh --renew -d mydomain.be For the <code>-d</code> parameter, you have to provide the '''first''' domain name you provided when generating the certificate (in the previous section, this was <code>mydomain.be</code>. If you are not sure which domain name to use, you can execute the command: ~/acme.sh --list This will generate a list of available certificates, which looks a bit like this: Main_Domain KeyLength SAN_Domains CA Created Renew mydomain.be "" www.mydomain.be LetsEncrypt.org ... ... ... ... ... ... ... ... In this example, the main domain is <code>mydomain.be</code>. The renewed certificates will automatically be copied to the files you provided in the command to generate the certificates (see previous section). '''After renewing the certificate, you have to email us to install your certificate.''' More information in the next section. ==== Installing the certificates ==== Check whether everything is stored correctly by executing the following command: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can send us an email clearly stating for which domains we need to add certificates and where the files are stored. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL, so make sure you follow this procedure carefully. [[Category:Webserver]] ae2422cf9122e608d0c09c63525aa5d358ada607 1191 1190 2020-11-19T16:16:59Z Yoa 30 /* Installing the certificates */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty consultative bodies (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request, the following steps have to be performed: * Set up the site that needs SSL if that's not already the case * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Make sure our nameservers are being used for the involved domain(s), as explained on [[Adding domain names]] * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir -p ~/letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain (the CA file) ├── mydomain.be.crt (the cert file; "public key") └── mydomain.be.key (the key file; "private key") If you already possess the necessary files, renaming and copying them accordingly is sufficient. '''You still have to email us to install your certificate.''' More information in the last section on this page. Otherwise, you can generate or renew your certificates using acme.sh. This is explained in the next section. ==== Generating certificates ==== {{notice|If you use a <code>.htaccess</code> file in the webroot of the domain name, make sure to add the following lines at the top of the file:|<pre><IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule></pre>}} Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll show how to use the acme.sh program to generate certificates on the ULYSSIS servers. '''If you already followed this section to generate certificates, skip to the next section on renewing certificates.''' Firstly, execute the following commands to download the acme.sh script in your home directory and make it executable: curl -o ~/acme.sh https://raw.githubusercontent.com/acmesh-official/acme.sh/master/acme.sh chmod +x ~/acme.sh Next, determine for which domains and subdomains you want to generate a certificate. You will need to generate a single certificate for each domain and subdomain which points to the same folder on your account (in most cases this is <code>www</code> in your home directory). The following example command will generate a certificate for <code>mydomain.be</code> and <code>www.mydomain.be</code> which points to the <code>www</code> folder in the home directory. '''Change the parameters''' as explained below before executing this command! ~/acme.sh --issue --cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt --key-file ~/letsencrypt/mydomain.be/mydomain.be.key --ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain -m "email@mydomain.be" -w ~/www -d mydomain.be -d www.mydomain.be The explanation of these many parameters is as follows: * <code>--issue</code> tells acme.sh to generate a new certificate. * <code>--cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt</code> tells acme.sh to store the certificate file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. '''This folder should already exist''', please refer to the previous section if you have not created this folder yet. * <code>--key-file ~/letsencrypt/mydomain.be/mydomain.be.key</code> tells acme.sh to store the key file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>--ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain</code> tells acme.sh to store the CA file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>-m "email@mydomain.be"</code> tells acme.sh the email address associated with the certificate. Let's Encrypt will remind this email address (if provided) when the certificate is close to expiring. * <code>-w ~/www</code> tells acme.sh where the domains in this certificate point to. Make sure to change the <code>www</code> part if the domains point to a different folder in your home directory. * <code>-d mydomain.be</code> and <code>-d www.mydomain.be</code> tell acme.sh that the certificate should protect <code>mydomain.be</code> and <code>www.mydomain.be</code>. The first domain name will be the "main domain", which is important for renewing. You should '''add all domain names''' pointing to the <code>-w</code> folder. After executing this command with the right parameters, your certificate should be generated successfully. When you have to renew the certificate in the future, you should follow the instructions in the next section. '''Don't forget to email us to install your new certificate.''' More information in the last section on this page. ==== Renewing certificates ==== To renew the certificates of <code>mydomain.be</code>, just execute: ~/acme.sh --renew -d mydomain.be For the <code>-d</code> parameter, you have to provide the '''first''' domain name you provided when generating the certificate (in the previous section, this was <code>mydomain.be</code>. If you are not sure which domain name to use, you can execute the command: ~/acme.sh --list This will generate a list of available certificates, which looks a bit like this: Main_Domain KeyLength SAN_Domains CA Created Renew mydomain.be "" www.mydomain.be LetsEncrypt.org ... ... ... ... ... ... ... ... In this example, the main domain is <code>mydomain.be</code>. The renewed certificates will automatically be copied to the files you provided in the command to generate the certificates (see previous section). '''After renewing the certificate, you have to email us to install your certificate.''' More information in the next section. ==== Installing the certificates ==== Check whether everything is stored correctly by executing the following command: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can '''send us an email clearly stating for which domains we need to add certificates and where the files are stored'''. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL, so make sure you follow this procedure carefully. [[Category:Webserver]] de118a9a0f6c1725afdfe648b5c83521b8ec9332 1192 1191 2020-11-19T19:54:28Z Yoa 30 /* Installing the certificates */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty consultative bodies (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request, the following steps have to be performed: * Set up the site that needs SSL if that's not already the case * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Make sure our nameservers are being used for the involved domain(s), as explained on [[Adding domain names]] * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir -p ~/letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain (the CA file) ├── mydomain.be.crt (the cert file; "public key") └── mydomain.be.key (the key file; "private key") If you already possess the necessary files, renaming and copying them accordingly is sufficient. '''You still have to email us to install your certificate.''' More information in the last section on this page. Otherwise, you can generate or renew your certificates using acme.sh. This is explained in the next section. ==== Generating certificates ==== {{notice|If you use a <code>.htaccess</code> file in the webroot of the domain name, make sure to add the following lines at the top of the file:|<pre><IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule></pre>}} Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll show how to use the acme.sh program to generate certificates on the ULYSSIS servers. '''If you already followed this section to generate certificates, skip to the next section on renewing certificates.''' Firstly, execute the following commands to download the acme.sh script in your home directory and make it executable: curl -o ~/acme.sh https://raw.githubusercontent.com/acmesh-official/acme.sh/master/acme.sh chmod +x ~/acme.sh Next, determine for which domains and subdomains you want to generate a certificate. You will need to generate a single certificate for each domain and subdomain which points to the same folder on your account (in most cases this is <code>www</code> in your home directory). The following example command will generate a certificate for <code>mydomain.be</code> and <code>www.mydomain.be</code> which points to the <code>www</code> folder in the home directory. '''Change the parameters''' as explained below before executing this command! ~/acme.sh --issue --cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt --key-file ~/letsencrypt/mydomain.be/mydomain.be.key --ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain -m "email@mydomain.be" -w ~/www -d mydomain.be -d www.mydomain.be The explanation of these many parameters is as follows: * <code>--issue</code> tells acme.sh to generate a new certificate. * <code>--cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt</code> tells acme.sh to store the certificate file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. '''This folder should already exist''', please refer to the previous section if you have not created this folder yet. * <code>--key-file ~/letsencrypt/mydomain.be/mydomain.be.key</code> tells acme.sh to store the key file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>--ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain</code> tells acme.sh to store the CA file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>-m "email@mydomain.be"</code> tells acme.sh the email address associated with the certificate. Let's Encrypt will remind this email address (if provided) when the certificate is close to expiring. * <code>-w ~/www</code> tells acme.sh where the domains in this certificate point to. Make sure to change the <code>www</code> part if the domains point to a different folder in your home directory. * <code>-d mydomain.be</code> and <code>-d www.mydomain.be</code> tell acme.sh that the certificate should protect <code>mydomain.be</code> and <code>www.mydomain.be</code>. The first domain name will be the "main domain", which is important for renewing. You should '''add all domain names''' pointing to the <code>-w</code> folder. After executing this command with the right parameters, your certificate should be generated successfully. When you have to renew the certificate in the future, you should follow the instructions in the next section. '''Don't forget to email us to install your new certificate.''' More information in the last section on this page. ==== Renewing certificates ==== To renew the certificates of <code>mydomain.be</code>, just execute: ~/acme.sh --renew -d mydomain.be For the <code>-d</code> parameter, you have to provide the '''first''' domain name you provided when generating the certificate (in the previous section, this was <code>mydomain.be</code>. If you are not sure which domain name to use, you can execute the command: ~/acme.sh --list This will generate a list of available certificates, which looks a bit like this: Main_Domain KeyLength SAN_Domains CA Created Renew mydomain.be "" www.mydomain.be LetsEncrypt.org ... ... ... ... ... ... ... ... In this example, the main domain is <code>mydomain.be</code>. The renewed certificates will automatically be copied to the files you provided in the command to generate the certificates (see previous section). '''After renewing the certificate, you have to email us to install your certificate.''' More information in the next section. ==== Getting your certificates installed ==== Check whether everything is stored correctly by executing the following command: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once you have placed your files in the correct folder, you can '''send us an email clearly stating for which domains we need to add certificates and where the files are stored'''. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL, so make sure you follow this procedure carefully. [[Category:Webserver]] 2ad78029ca960dd281608d622d9436a838f7dbf7 1195 1192 2020-12-12T00:31:56Z Principis 32 /* Getting your certificates installed */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty consultative bodies (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request, the following steps have to be performed: * Set up the site that needs SSL if that's not already the case * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Make sure our nameservers are being used for the involved domain(s), as explained on [[Adding domain names]] * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir -p ~/letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain (the CA file) ├── mydomain.be.crt (the cert file; "public key") └── mydomain.be.key (the key file; "private key") If you already possess the necessary files, renaming and copying them accordingly is sufficient. '''You still have to email us to install your certificate.''' More information in the last section on this page. Otherwise, you can generate or renew your certificates using acme.sh. This is explained in the next section. ==== Generating certificates ==== {{notice|If you use a <code>.htaccess</code> file in the webroot of the domain name, make sure to add the following lines at the top of the file:|<pre><IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule></pre>}} Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll show how to use the acme.sh program to generate certificates on the ULYSSIS servers. '''If you already followed this section to generate certificates, skip to the next section on renewing certificates.''' Firstly, execute the following commands to download the acme.sh script in your home directory and make it executable: curl -o ~/acme.sh https://raw.githubusercontent.com/acmesh-official/acme.sh/master/acme.sh chmod +x ~/acme.sh Next, determine for which domains and subdomains you want to generate a certificate. You will need to generate a single certificate for each domain and subdomain which points to the same folder on your account (in most cases this is <code>www</code> in your home directory). The following example command will generate a certificate for <code>mydomain.be</code> and <code>www.mydomain.be</code> which points to the <code>www</code> folder in the home directory. '''Change the parameters''' as explained below before executing this command! ~/acme.sh --issue --cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt --key-file ~/letsencrypt/mydomain.be/mydomain.be.key --ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain -m "email@mydomain.be" -w ~/www -d mydomain.be -d www.mydomain.be The explanation of these many parameters is as follows: * <code>--issue</code> tells acme.sh to generate a new certificate. * <code>--cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt</code> tells acme.sh to store the certificate file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. '''This folder should already exist''', please refer to the previous section if you have not created this folder yet. * <code>--key-file ~/letsencrypt/mydomain.be/mydomain.be.key</code> tells acme.sh to store the key file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>--ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain</code> tells acme.sh to store the CA file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>-m "email@mydomain.be"</code> tells acme.sh the email address associated with the certificate. Let's Encrypt will remind this email address (if provided) when the certificate is close to expiring. * <code>-w ~/www</code> tells acme.sh where the domains in this certificate point to. Make sure to change the <code>www</code> part if the domains point to a different folder in your home directory. * <code>-d mydomain.be</code> and <code>-d www.mydomain.be</code> tell acme.sh that the certificate should protect <code>mydomain.be</code> and <code>www.mydomain.be</code>. The first domain name will be the "main domain", which is important for renewing. You should '''add all domain names''' pointing to the <code>-w</code> folder. After executing this command with the right parameters, your certificate should be generated successfully. When you have to renew the certificate in the future, you should follow the instructions in the next section. '''Don't forget to email us to install your new certificate.''' More information in the last section on this page. ==== Renewing certificates ==== To renew the certificates of <code>mydomain.be</code>, just execute: ~/acme.sh --renew -d mydomain.be For the <code>-d</code> parameter, you have to provide the '''first''' domain name you provided when generating the certificate (in the previous section, this was <code>mydomain.be</code>. If you are not sure which domain name to use, you can execute the command: ~/acme.sh --list This will generate a list of available certificates, which looks a bit like this: Main_Domain KeyLength SAN_Domains CA Created Renew mydomain.be "" www.mydomain.be LetsEncrypt.org ... ... ... ... ... ... ... ... In this example, the main domain is <code>mydomain.be</code>. The renewed certificates will automatically be copied to the files you provided in the command to generate the certificates (see previous section). '''After renewing the certificate, you have to email us to install your certificate.''' More information in the next section. ==== Getting your certificates installed ==== Check whether everything is stored correctly by executing the following command: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once all steps are done, the account holder can '''send us an email clearly stating the account name, for which domains we need to add certificates and where the files are stored'''. If you are renewing existing certificates, also clearly state that in the email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL, so make sure you follow this procedure carefully. [[Category:Webserver]] 08f93258a34e4ec3b1af68b359926d96bc91fc66 1196 1195 2020-12-12T00:35:48Z Principis 32 /* Getting your certificates installed */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty consultative bodies (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request, the following steps have to be performed: * Set up the site that needs SSL if that's not already the case * Create a forwarder from hostmaster@yourdomain.tld to ulyssis@ulyssis.org * Make sure our nameservers are being used for the involved domain(s), as explained on [[Adding domain names]] * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir -p ~/letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain (the CA file) ├── mydomain.be.crt (the cert file; "public key") └── mydomain.be.key (the key file; "private key") If you already possess the necessary files, renaming and copying them accordingly is sufficient. '''You still have to email us to install your certificate.''' More information in the last section on this page. Otherwise, you can generate or renew your certificates using acme.sh. This is explained in the next section. ==== Generating certificates ==== {{notice|If you use a <code>.htaccess</code> file in the webroot of the domain name, make sure to add the following lines at the top of the file:|<pre><IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule></pre>}} Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll show how to use the acme.sh program to generate certificates on the ULYSSIS servers. '''If you already followed this section to generate certificates, skip to the next section on renewing certificates.''' Firstly, execute the following commands to download the acme.sh script in your home directory and make it executable: curl -o ~/acme.sh https://raw.githubusercontent.com/acmesh-official/acme.sh/master/acme.sh chmod +x ~/acme.sh Next, determine for which domains and subdomains you want to generate a certificate. You will need to generate a single certificate for each domain and subdomain which points to the same folder on your account (in most cases this is <code>www</code> in your home directory). The following example command will generate a certificate for <code>mydomain.be</code> and <code>www.mydomain.be</code> which points to the <code>www</code> folder in the home directory. '''Change the parameters''' as explained below before executing this command! ~/acme.sh --issue --cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt --key-file ~/letsencrypt/mydomain.be/mydomain.be.key --ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain -m "email@mydomain.be" -w ~/www -d mydomain.be -d www.mydomain.be The explanation of these many parameters is as follows: * <code>--issue</code> tells acme.sh to generate a new certificate. * <code>--cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt</code> tells acme.sh to store the certificate file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. '''This folder should already exist''', please refer to the previous section if you have not created this folder yet. * <code>--key-file ~/letsencrypt/mydomain.be/mydomain.be.key</code> tells acme.sh to store the key file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>--ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain</code> tells acme.sh to store the CA file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>-m "email@mydomain.be"</code> tells acme.sh the email address associated with the certificate. Let's Encrypt will remind this email address (if provided) when the certificate is close to expiring. * <code>-w ~/www</code> tells acme.sh where the domains in this certificate point to. Make sure to change the <code>www</code> part if the domains point to a different folder in your home directory. * <code>-d mydomain.be</code> and <code>-d www.mydomain.be</code> tell acme.sh that the certificate should protect <code>mydomain.be</code> and <code>www.mydomain.be</code>. The first domain name will be the "main domain", which is important for renewing. You should '''add all domain names''' pointing to the <code>-w</code> folder. After executing this command with the right parameters, your certificate should be generated successfully. When you have to renew the certificate in the future, you should follow the instructions in the next section. '''Don't forget to email us to install your new certificate.''' More information in the last section on this page. ==== Renewing certificates ==== To renew the certificates of <code>mydomain.be</code>, just execute: ~/acme.sh --renew -d mydomain.be For the <code>-d</code> parameter, you have to provide the '''first''' domain name you provided when generating the certificate (in the previous section, this was <code>mydomain.be</code>. If you are not sure which domain name to use, you can execute the command: ~/acme.sh --list This will generate a list of available certificates, which looks a bit like this: Main_Domain KeyLength SAN_Domains CA Created Renew mydomain.be "" www.mydomain.be LetsEncrypt.org ... ... ... ... ... ... ... ... In this example, the main domain is <code>mydomain.be</code>. The renewed certificates will automatically be copied to the files you provided in the command to generate the certificates (see previous section). '''After renewing the certificate, you have to email us to install your certificate.''' More information in the next section. ==== Getting your certificates installed ==== Check whether everything is stored correctly by executing the following command: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once all steps are done and if you are the '''account holder''', '''you can send us an email clearly stating the account name, for which domains we need to add certificates and where the files are stored'''. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL, so make sure you follow this procedure carefully. [[Category:Webserver]] b43f87b2e4e6feabcc27732f3ac6c736b5b06ae2 1211 1196 2021-02-15T16:38:38Z Vincenttc 21 /* Requesting SSL from the KU Leuven */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty consultative bodies (facultaire overlegorganen) recognized by Stura body as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. Before sending us a request, the following steps have to be performed: * Set up the site that needs SSL if that's not already the case * Make sure our nameservers are being used for the involved domain(s), as explained on [[Adding domain names]] * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir -p ~/letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain (the CA file) ├── mydomain.be.crt (the cert file; "public key") └── mydomain.be.key (the key file; "private key") If you already possess the necessary files, renaming and copying them accordingly is sufficient. '''You still have to email us to install your certificate.''' More information in the last section on this page. Otherwise, you can generate or renew your certificates using acme.sh. This is explained in the next section. ==== Generating certificates ==== {{notice|If you use a <code>.htaccess</code> file in the webroot of the domain name, make sure to add the following lines at the top of the file:|<pre><IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule></pre>}} Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll show how to use the acme.sh program to generate certificates on the ULYSSIS servers. '''If you already followed this section to generate certificates, skip to the next section on renewing certificates.''' Firstly, execute the following commands to download the acme.sh script in your home directory and make it executable: curl -o ~/acme.sh https://raw.githubusercontent.com/acmesh-official/acme.sh/master/acme.sh chmod +x ~/acme.sh Next, determine for which domains and subdomains you want to generate a certificate. You will need to generate a single certificate for each domain and subdomain which points to the same folder on your account (in most cases this is <code>www</code> in your home directory). The following example command will generate a certificate for <code>mydomain.be</code> and <code>www.mydomain.be</code> which points to the <code>www</code> folder in the home directory. '''Change the parameters''' as explained below before executing this command! ~/acme.sh --issue --cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt --key-file ~/letsencrypt/mydomain.be/mydomain.be.key --ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain -m "email@mydomain.be" -w ~/www -d mydomain.be -d www.mydomain.be The explanation of these many parameters is as follows: * <code>--issue</code> tells acme.sh to generate a new certificate. * <code>--cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt</code> tells acme.sh to store the certificate file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. '''This folder should already exist''', please refer to the previous section if you have not created this folder yet. * <code>--key-file ~/letsencrypt/mydomain.be/mydomain.be.key</code> tells acme.sh to store the key file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>--ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain</code> tells acme.sh to store the CA file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>-m "email@mydomain.be"</code> tells acme.sh the email address associated with the certificate. Let's Encrypt will remind this email address (if provided) when the certificate is close to expiring. * <code>-w ~/www</code> tells acme.sh where the domains in this certificate point to. Make sure to change the <code>www</code> part if the domains point to a different folder in your home directory. * <code>-d mydomain.be</code> and <code>-d www.mydomain.be</code> tell acme.sh that the certificate should protect <code>mydomain.be</code> and <code>www.mydomain.be</code>. The first domain name will be the "main domain", which is important for renewing. You should '''add all domain names''' pointing to the <code>-w</code> folder. After executing this command with the right parameters, your certificate should be generated successfully. When you have to renew the certificate in the future, you should follow the instructions in the next section. '''Don't forget to email us to install your new certificate.''' More information in the last section on this page. ==== Renewing certificates ==== To renew the certificates of <code>mydomain.be</code>, just execute: ~/acme.sh --renew -d mydomain.be For the <code>-d</code> parameter, you have to provide the '''first''' domain name you provided when generating the certificate (in the previous section, this was <code>mydomain.be</code>. If you are not sure which domain name to use, you can execute the command: ~/acme.sh --list This will generate a list of available certificates, which looks a bit like this: Main_Domain KeyLength SAN_Domains CA Created Renew mydomain.be "" www.mydomain.be LetsEncrypt.org ... ... ... ... ... ... ... ... In this example, the main domain is <code>mydomain.be</code>. The renewed certificates will automatically be copied to the files you provided in the command to generate the certificates (see previous section). '''After renewing the certificate, you have to email us to install your certificate.''' More information in the next section. ==== Getting your certificates installed ==== Check whether everything is stored correctly by executing the following command: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once all steps are done and if you are the '''account holder''', '''you can send us an email clearly stating the account name, for which domains we need to add certificates and where the files are stored'''. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL, so make sure you follow this procedure carefully. [[Category:Webserver]] 44416d795426d00be211f99670b4bd64214129cf 1212 1211 2021-02-16T08:45:48Z Bert 8 wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty consultative bodies (facultaire overlegorganen) recognized by Studentenraad KU Leuven as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. We are not eligible to request SSL/TLS certificates for individuals with a personal account, nor research groups or staff associations. We suggest those latter groups request certificates from KU Leuven ICTS directly. Before sending us a request, the following steps have to be performed: * Set up the site that needs SSL if that's not already the case * Make sure our nameservers are being used for the involved domain(s), as explained on [[Adding domain names]] * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir -p ~/letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain (the CA file) ├── mydomain.be.crt (the cert file; "public key") └── mydomain.be.key (the key file; "private key") If you already possess the necessary files, renaming and copying them accordingly is sufficient. '''You still have to email us to install your certificate.''' More information in the last section on this page. Otherwise, you can generate or renew your certificates using acme.sh. This is explained in the next section. ==== Generating certificates ==== {{notice|If you use a <code>.htaccess</code> file in the webroot of the domain name, make sure to add the following lines at the top of the file:|<pre><IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule></pre>}} Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll show how to use the acme.sh program to generate certificates on the ULYSSIS servers. '''If you already followed this section to generate certificates, skip to the next section on renewing certificates.''' Firstly, execute the following commands to download the acme.sh script in your home directory and make it executable: curl -o ~/acme.sh https://raw.githubusercontent.com/acmesh-official/acme.sh/master/acme.sh chmod +x ~/acme.sh Next, determine for which domains and subdomains you want to generate a certificate. You will need to generate a single certificate for each domain and subdomain which points to the same folder on your account (in most cases this is <code>www</code> in your home directory). The following example command will generate a certificate for <code>mydomain.be</code> and <code>www.mydomain.be</code> which points to the <code>www</code> folder in the home directory. '''Change the parameters''' as explained below before executing this command! ~/acme.sh --issue --cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt --key-file ~/letsencrypt/mydomain.be/mydomain.be.key --ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain -m "email@mydomain.be" -w ~/www -d mydomain.be -d www.mydomain.be The explanation of these many parameters is as follows: * <code>--issue</code> tells acme.sh to generate a new certificate. * <code>--cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt</code> tells acme.sh to store the certificate file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. '''This folder should already exist''', please refer to the previous section if you have not created this folder yet. * <code>--key-file ~/letsencrypt/mydomain.be/mydomain.be.key</code> tells acme.sh to store the key file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>--ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain</code> tells acme.sh to store the CA file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>-m "email@mydomain.be"</code> tells acme.sh the email address associated with the certificate. Let's Encrypt will remind this email address (if provided) when the certificate is close to expiring. * <code>-w ~/www</code> tells acme.sh where the domains in this certificate point to. Make sure to change the <code>www</code> part if the domains point to a different folder in your home directory. * <code>-d mydomain.be</code> and <code>-d www.mydomain.be</code> tell acme.sh that the certificate should protect <code>mydomain.be</code> and <code>www.mydomain.be</code>. The first domain name will be the "main domain", which is important for renewing. You should '''add all domain names''' pointing to the <code>-w</code> folder. After executing this command with the right parameters, your certificate should be generated successfully. When you have to renew the certificate in the future, you should follow the instructions in the next section. '''Don't forget to email us to install your new certificate.''' More information in the last section on this page. ==== Renewing certificates ==== To renew the certificates of <code>mydomain.be</code>, just execute: ~/acme.sh --renew -d mydomain.be For the <code>-d</code> parameter, you have to provide the '''first''' domain name you provided when generating the certificate (in the previous section, this was <code>mydomain.be</code>. If you are not sure which domain name to use, you can execute the command: ~/acme.sh --list This will generate a list of available certificates, which looks a bit like this: Main_Domain KeyLength SAN_Domains CA Created Renew mydomain.be "" www.mydomain.be LetsEncrypt.org ... ... ... ... ... ... ... ... In this example, the main domain is <code>mydomain.be</code>. The renewed certificates will automatically be copied to the files you provided in the command to generate the certificates (see previous section). '''After renewing the certificate, you have to email us to install your certificate.''' More information in the next section. ==== Getting your certificates installed ==== Check whether everything is stored correctly by executing the following command: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once all steps are done and if you are the '''account holder''', '''you can send us an email clearly stating the account name, for which domains we need to add certificates and where the files are stored'''. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL, so make sure you follow this procedure carefully. [[Category:Webserver]] 1282dd2ddf16524572cca74bced80844d5c84a08 1213 1212 2021-02-16T08:48:57Z Bert 8 wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty consultative bodies (facultaire overlegorganen) recognized by Studentenraad KU Leuven as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. We are not eligible to request SSL/TLS certificates for individuals with a personal account, nor research groups or staff associations. We suggest those latter groups request certificates from KU Leuven ICTS directly or consider Let's Encrypt or another third party service. Before sending us a request, the following steps have to be performed: * Set up the site that needs SSL if that's not already the case * Make sure our nameservers are being used for the involved domain(s), as explained on [[Adding domain names]] * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir -p ~/letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain (the CA file) ├── mydomain.be.crt (the cert file; "public key") └── mydomain.be.key (the key file; "private key") If you already possess the necessary files, renaming and copying them accordingly is sufficient. '''You still have to email us to install your certificate.''' More information in the last section on this page. Otherwise, you can generate or renew your certificates using acme.sh. This is explained in the next section. ==== Generating certificates ==== {{notice|If you use a <code>.htaccess</code> file in the webroot of the domain name, make sure to add the following lines at the top of the file:|<pre><IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule></pre>}} Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll show how to use the acme.sh program to generate certificates on the ULYSSIS servers. '''If you already followed this section to generate certificates, skip to the next section on renewing certificates.''' Firstly, execute the following commands to download the acme.sh script in your home directory and make it executable: curl -o ~/acme.sh https://raw.githubusercontent.com/acmesh-official/acme.sh/master/acme.sh chmod +x ~/acme.sh Next, determine for which domains and subdomains you want to generate a certificate. You will need to generate a single certificate for each domain and subdomain which points to the same folder on your account (in most cases this is <code>www</code> in your home directory). The following example command will generate a certificate for <code>mydomain.be</code> and <code>www.mydomain.be</code> which points to the <code>www</code> folder in the home directory. '''Change the parameters''' as explained below before executing this command! ~/acme.sh --issue --cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt --key-file ~/letsencrypt/mydomain.be/mydomain.be.key --ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain -m "email@mydomain.be" -w ~/www -d mydomain.be -d www.mydomain.be The explanation of these many parameters is as follows: * <code>--issue</code> tells acme.sh to generate a new certificate. * <code>--cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt</code> tells acme.sh to store the certificate file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. '''This folder should already exist''', please refer to the previous section if you have not created this folder yet. * <code>--key-file ~/letsencrypt/mydomain.be/mydomain.be.key</code> tells acme.sh to store the key file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>--ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain</code> tells acme.sh to store the CA file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>-m "email@mydomain.be"</code> tells acme.sh the email address associated with the certificate. Let's Encrypt will remind this email address (if provided) when the certificate is close to expiring. * <code>-w ~/www</code> tells acme.sh where the domains in this certificate point to. Make sure to change the <code>www</code> part if the domains point to a different folder in your home directory. * <code>-d mydomain.be</code> and <code>-d www.mydomain.be</code> tell acme.sh that the certificate should protect <code>mydomain.be</code> and <code>www.mydomain.be</code>. The first domain name will be the "main domain", which is important for renewing. You should '''add all domain names''' pointing to the <code>-w</code> folder. After executing this command with the right parameters, your certificate should be generated successfully. When you have to renew the certificate in the future, you should follow the instructions in the next section. '''Don't forget to email us to install your new certificate.''' More information in the last section on this page. ==== Renewing certificates ==== To renew the certificates of <code>mydomain.be</code>, just execute: ~/acme.sh --renew -d mydomain.be For the <code>-d</code> parameter, you have to provide the '''first''' domain name you provided when generating the certificate (in the previous section, this was <code>mydomain.be</code>. If you are not sure which domain name to use, you can execute the command: ~/acme.sh --list This will generate a list of available certificates, which looks a bit like this: Main_Domain KeyLength SAN_Domains CA Created Renew mydomain.be "" www.mydomain.be LetsEncrypt.org ... ... ... ... ... ... ... ... In this example, the main domain is <code>mydomain.be</code>. The renewed certificates will automatically be copied to the files you provided in the command to generate the certificates (see previous section). '''After renewing the certificate, you have to email us to install your certificate.''' More information in the next section. ==== Getting your certificates installed ==== Check whether everything is stored correctly by executing the following command: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once all steps are done and if you are the '''account holder''', '''you can send us an email clearly stating the account name, for which domains we need to add certificates and where the files are stored'''. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL, so make sure you follow this procedure carefully. [[Category:Webserver]] ac0cb4b727810f8740d892f8ff6bdb8a588b7ea8 0 104 1193 1054 2020-11-30T23:51:01Z Vincenttc 21 /* Homedirectory permissions */ wikitext text/x-wiki PHP code is run with PHP-FPM as your ULYSSIS user. This means you can tighten up you website's security by denying other users the permission to read your PHP files. However, due to the way the Apache webserver works, it must be able to determine the existence of your PHP files. Non-PHP files in your www directory must remain readable by other users, because Apache reads these as it's own user. === Recommended permissions === * Homedirectory: See [[#Homedirectory permissions | homedirectory]] * www directory (and other directories from where websites are served), including subdirectories: <code>0705/drwx---r-x</code> * Static website files (css, images, html, ...): <code>0604/-rw----r--</code> * Configuration files containing secrets/passwords: <code>0600/-rw-------</code> * Other directories and files that are not part of a website: <code>0600/-rw-------</code> or <code>0700/-rwx------</code> === Securing database login info === Suppose you have a file called <code>config.php</code>, containing login information for your database. To secure this information, you can make it readable and writeable by only you, and nobody else using <code>chmod 600 config.php</code>. In FileZilla, you can do this by right-clicking on the config file, clicking on "File permissions...", and changing the permissions according to the following screenshots: [[File:config-php_dropdown.png]] [[File:config-php_attrs.png]] === Securing uploads directory === Also, if there are directories that you made writeable by others, e.g. an uploads folder, this is no longer necessary. If this directory is called <code>uploads</code>, you can remove write rights for others with <code>chmod go-w uploads</code>. In FileZilla, you can do this by right-clicking on the config file, clicking on "File permissions...", and changing the permissions according to the following screenshots: [[File:uploads_dropdown.png]] [[File:uploads_attrs.png]] [[Category:Files]] [[Category:Security & anti-spam]] e4d128e1d4b4bca340a03d80af6e65b4897c28a4 1194 1193 2020-11-30T23:51:34Z Vincenttc 21 /* Recommended permissions */ wikitext text/x-wiki PHP code is run with PHP-FPM as your ULYSSIS user. This means you can tighten up you website's security by denying other users the permission to read your PHP files. However, due to the way the Apache webserver works, it must be able to determine the existence of your PHP files. Non-PHP files in your www directory must remain readable by other users, because Apache reads these as it's own user. === Recommended permissions === * www directory (and other directories from where websites are served), including subdirectories: <code>0705/drwxr-xr-x</code> * Static website files (css, images, html, ...): <code>0604/-rw-r--r--</code> * Configuration files containing secrets/passwords: <code>0600/-rw-------</code> * Other directories and files that are not part of a website: <code>0600/-rw-------</code> or <code>0700/-rwx------</code> === Securing database login info === Suppose you have a file called <code>config.php</code>, containing login information for your database. To secure this information, you can make it readable and writeable by only you, and nobody else using <code>chmod 600 config.php</code>. In FileZilla, you can do this by right-clicking on the config file, clicking on "File permissions...", and changing the permissions according to the following screenshots: [[File:config-php_dropdown.png]] [[File:config-php_attrs.png]] === Securing uploads directory === Also, if there are directories that you made writeable by others, e.g. an uploads folder, this is no longer necessary. If this directory is called <code>uploads</code>, you can remove write rights for others with <code>chmod go-w uploads</code>. In FileZilla, you can do this by right-clicking on the config file, clicking on "File permissions...", and changing the permissions according to the following screenshots: [[File:uploads_dropdown.png]] [[File:uploads_attrs.png]] [[Category:Files]] [[Category:Security & anti-spam]] 2e0645b940a80518b0746a0c8f5497ed30ae7791 0 6 1197 747 2020-12-15T23:31:02Z Bert 8 /* Creating a MySQL database */ wikitext text/x-wiki ==Creating a MySQL user== To use MySQL on your ULYSSIS account you first need to create a MySQL user on [https://ucc.ulyssis.org UCC]. In the MySQL section of the panel you will be suggested to click a link to create a user. Then fill in a password for the database user. It is highly recommended that this password differs from the password you use for your account. Then you just click ''Create user'' and you are ready to go. ==Creating a MySQL database== After creating a MySQL user, you can simple press ''Add database'' in [https://ucc.ulyssis.org UCC] and enter the name for your new database. It will automatically be prefixed by your username. ==Deleting a MySQL database== If you no longer need a database, you can easily remove it by clicking on ''MySQL'' in [https://ucc.ulyssis.org UCC] and then pressing on ''Remove database'' next to the database you would like to delete. After confirming, the database and all its tables and other contents will be gone. For security reasons, you can't remove databases using an SQL query like DROP DATABASE, but have to go through UCC. ==Using MySQL for your website or application== Host: mysql.ulyssis.org Username: your account's username Password: the password you chose when you made the MySQL user Database: the database name you chose, prefixed by your username For example, if my username is foobar, I made a database called website and I were to create a PHP website I would use something like: <syntaxhighlight lang="php">$db = new mysqli('mysql.ulyssis.org', 'foobar', 'correct horse battery staple', 'foobar_website');</syntaxhighlight> or <syntaxhighlight lang="php">$db = new PDO('mysql:host=mysql.ulyssis.org;dbname=foobar_website', 'foobar', 'correct horse battery staple');</syntaxhighlight> ==Managing MySQL with PHPMyAdmin== Using your username and password you can easily manage your MySQL databases, tables and records on https://phpmyadmin.ulyssis.org ==Accessing MySQL from outside of our network== To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH-tunnel. In many MySQL management tools this is already supported. === MySQL Workbench === While [https://www.mysql.com/products/workbench/ MySQL Workbench] might not fully support our MySQL database, all commonly used operations work perfectly. You can connect to our database using MySQL Workbench by creating a connection as follows ([username] should be replaced by your username, of course): [[File:MySQL_Workbench_SSH.png]] === Linux, Mac OSX === On Linux, Mac OSX and other Unix-like Operating Systems it is also easily possible to use the following command to create a tunnel to a local port (in this case 3300) ssh username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N While this command is running, you can connect to the MySQL server with host 'localhost' and port '3300'. To terminate the port forwarding, press ctrl-C in the terminal. You can use "ssh -f username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N": the f-argument will put the command in the background. [[Category:Databases]] 8ce2bad21d8745d2d00b08741cda84f195b0ed3e 1198 1197 2020-12-16T00:04:46Z Bert 8 wikitext text/x-wiki MySQL is one of the most popular databases for websites. It's used by most CMSes and other common web software, and many programming languages have support for it. ULYSSIS specifically uses MariaDB, which is a fork of MySQL with similar features and (almost) identical SQL syntax, but offers better performance and has less corporate interference in the development process. == Managing MySQL == ===Creating a MySQL user=== To use MySQL on your ULYSSIS account you first need to create a MySQL user on [https://ucc.ulyssis.org UCC]. In the MySQL section of the panel you will be suggested to click a link to create a user. Then fill in a password for the database user. It is highly recommended that this password differs from the password you use for your account. Then you just click ''Create user'' and you are ready to go. ===Creating a MySQL database=== After creating a MySQL user, you can simple press ''Add database'' in [https://ucc.ulyssis.org UCC] and enter the name for your new database. It will automatically be prefixed by your username. ===Deleting a MySQL database=== If you no longer need a database, you can easily remove it by clicking on ''MySQL'' in [https://ucc.ulyssis.org UCC] and then pressing on ''Remove database'' next to the database you would like to delete. After confirming, the database and all its tables and other contents will be gone. For security reasons, you can't remove databases using an SQL query like DROP DATABASE, but have to go through UCC. == Accessing MySQL == ===Using MySQL for your website or application=== Host: mysql.ulyssis.org Username: your account's username Password: the password you chose when you made the MySQL user Database: the database name you chose, prefixed by your username For example, if my username is foobar, I made a database called website and I were to create a PHP website I would use something like: <syntaxhighlight lang="php">$db = new mysqli('mysql.ulyssis.org', 'foobar', 'correct horse battery staple', 'foobar_website');</syntaxhighlight> or <syntaxhighlight lang="php">$db = new PDO('mysql:host=mysql.ulyssis.org;dbname=foobar_website', 'foobar', 'correct horse battery staple');</syntaxhighlight> ===Accessing MySQL with PHPMyAdmin or Adminer=== Using your username and password you can easily manage your MySQL databases, tables and records on https://phpmyadmin.ulyssis.org and https://adminer.ulyssis.org. Documentation is also available to aid in [[using PHPMyAdmin]] and [[using Adminer]] ===Accessing MySQL from outside of our network=== To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH-tunnel. In many MySQL management tools this is already supported. ==== MySQL Workbench ==== While [https://www.mysql.com/products/workbench/ MySQL Workbench] might not fully support our MySQL database, all commonly used operations work perfectly. You can connect to our database using MySQL Workbench by creating a connection as follows ([username] should be replaced by your username, of course): [[File:MySQL_Workbench_SSH.png]] ==== Linux, Mac OSX ==== On Linux, Mac OSX and other Unix-like Operating Systems it is also easily possible to use the following command to create a tunnel to a local port (in this case 3300) ssh username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N While this command is running, you can connect to the MySQL server with host 'localhost' and port '3300'. To terminate the port forwarding, press ctrl-C in the terminal. You can use "ssh -f username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N": the f-argument will put the command in the background. [[Category:Databases]] 856aa96a26168168ce29ebaf66d3b2f004a2d822 1199 1198 2020-12-16T00:06:52Z Bert 8 /* Managing MySQL */ wikitext text/x-wiki MySQL is one of the most popular databases for websites. It's used by most CMSes and other common web software, and many programming languages have support for it. ULYSSIS specifically uses MariaDB, which is a fork of MySQL with similar features and (almost) identical SQL syntax, but offers better performance and has less corporate interference in the development process. == Managing MySQL == All common management tasks can be performed through our control panel [https://ucc.ulyssis.org UCC] under the MySQL section. ===Creating a MySQL user=== To use MySQL on your ULYSSIS account you first need to create a MySQL user on [https://ucc.ulyssis.org UCC]. In the MySQL section of the panel you will be suggested to click a link to create a user. Then fill in a password for the database user. It is highly recommended that this password differs from the password you use for your account. Then you just click ''Create user'' and you are ready to go. ===Creating a MySQL database=== After creating a MySQL user, you can simple press ''Add database'' in [https://ucc.ulyssis.org UCC] and enter the name for your new database. It will automatically be prefixed by your username. ===Deleting a MySQL database=== If you no longer need a database, you can easily remove it by clicking on ''MySQL'' in [https://ucc.ulyssis.org UCC] and then pressing on ''Remove database'' next to the database you would like to delete. After confirming, the database and all its tables and other contents will be gone. For security reasons, you can't remove databases using an SQL query like DROP DATABASE, but have to go through UCC. == Accessing MySQL == ===Using MySQL for your website or application=== Host: mysql.ulyssis.org Username: your account's username Password: the password you chose when you made the MySQL user Database: the database name you chose, prefixed by your username For example, if my username is foobar, I made a database called website and I were to create a PHP website I would use something like: <syntaxhighlight lang="php">$db = new mysqli('mysql.ulyssis.org', 'foobar', 'correct horse battery staple', 'foobar_website');</syntaxhighlight> or <syntaxhighlight lang="php">$db = new PDO('mysql:host=mysql.ulyssis.org;dbname=foobar_website', 'foobar', 'correct horse battery staple');</syntaxhighlight> ===Accessing MySQL with PHPMyAdmin or Adminer=== Using your username and password you can easily manage your MySQL databases, tables and records on https://phpmyadmin.ulyssis.org and https://adminer.ulyssis.org. Documentation is also available to aid in [[using PHPMyAdmin]] and [[using Adminer]] ===Accessing MySQL from outside of our network=== To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH-tunnel. In many MySQL management tools this is already supported. ==== MySQL Workbench ==== While [https://www.mysql.com/products/workbench/ MySQL Workbench] might not fully support our MySQL database, all commonly used operations work perfectly. You can connect to our database using MySQL Workbench by creating a connection as follows ([username] should be replaced by your username, of course): [[File:MySQL_Workbench_SSH.png]] ==== Linux, Mac OSX ==== On Linux, Mac OSX and other Unix-like Operating Systems it is also easily possible to use the following command to create a tunnel to a local port (in this case 3300) ssh username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N While this command is running, you can connect to the MySQL server with host 'localhost' and port '3300'. To terminate the port forwarding, press ctrl-C in the terminal. You can use "ssh -f username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N": the f-argument will put the command in the background. [[Category:Databases]] ce45657826d1e8f68796e677ae4d2fdc28929575 1200 1199 2020-12-16T00:08:43Z Bert 8 /* Accessing MySQL */ wikitext text/x-wiki MySQL is one of the most popular databases for websites. It's used by most CMSes and other common web software, and many programming languages have support for it. ULYSSIS specifically uses MariaDB, which is a fork of MySQL with similar features and (almost) identical SQL syntax, but offers better performance and has less corporate interference in the development process. == Managing MySQL == All common management tasks can be performed through our control panel [https://ucc.ulyssis.org UCC] under the MySQL section. ===Creating a MySQL user=== To use MySQL on your ULYSSIS account you first need to create a MySQL user on [https://ucc.ulyssis.org UCC]. In the MySQL section of the panel you will be suggested to click a link to create a user. Then fill in a password for the database user. It is highly recommended that this password differs from the password you use for your account. Then you just click ''Create user'' and you are ready to go. ===Creating a MySQL database=== After creating a MySQL user, you can simple press ''Add database'' in [https://ucc.ulyssis.org UCC] and enter the name for your new database. It will automatically be prefixed by your username. ===Deleting a MySQL database=== If you no longer need a database, you can easily remove it by clicking on ''MySQL'' in [https://ucc.ulyssis.org UCC] and then pressing on ''Remove database'' next to the database you would like to delete. After confirming, the database and all its tables and other contents will be gone. For security reasons, you can't remove databases using an SQL query like DROP DATABASE, but have to go through UCC. == Accessing MySQL == Our MySQL and PostgreSQL databases run on a separate database server, this means you may need to enter a specific host, together with the correct credentials, to access your database within a website or application. You may also wish to use a common tool such as PHPMyAdmin or access a database remotely. Details on how to do that are available in the sections below. ===Using MySQL for your website or application=== Host: mysql.ulyssis.org Username: your account's username Password: the password you chose when you made the MySQL user Database: the database name you chose, prefixed by your username For example, if my username is foobar, I made a database called website and I were to create a PHP website I would use something like: <syntaxhighlight lang="php">$db = new mysqli('mysql.ulyssis.org', 'foobar', 'correct horse battery staple', 'foobar_website');</syntaxhighlight> or <syntaxhighlight lang="php">$db = new PDO('mysql:host=mysql.ulyssis.org;dbname=foobar_website', 'foobar', 'correct horse battery staple');</syntaxhighlight> ===Accessing MySQL with PHPMyAdmin or Adminer=== Using your username and password you can easily manage your MySQL databases, tables and records on https://phpmyadmin.ulyssis.org and https://adminer.ulyssis.org. Documentation is also available to aid in [[using PHPMyAdmin]] and [[using Adminer]] ===Accessing MySQL from outside of our network=== To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH-tunnel. In many MySQL management tools this is already supported. ==== MySQL Workbench ==== While [https://www.mysql.com/products/workbench/ MySQL Workbench] might not fully support our MySQL database, all commonly used operations work perfectly. You can connect to our database using MySQL Workbench by creating a connection as follows ([username] should be replaced by your username, of course): [[File:MySQL_Workbench_SSH.png]] ==== Linux, Mac OSX ==== On Linux, Mac OSX and other Unix-like Operating Systems it is also easily possible to use the following command to create a tunnel to a local port (in this case 3300) ssh username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N While this command is running, you can connect to the MySQL server with host 'localhost' and port '3300'. To terminate the port forwarding, press ctrl-C in the terminal. You can use "ssh -f username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N": the f-argument will put the command in the background. [[Category:Databases]] 944375405051545da27e234717e737b4b15f2584 1201 1200 2020-12-16T18:04:32Z Pcy 37 fix wording and punctuation a little bit wikitext text/x-wiki MySQL is one of the most popular databases for websites. It's used by most CMSes and other common web software, and many programming languages have support for it. ULYSSIS specifically uses MariaDB, which is a fork of MySQL with similar features and (almost) identical SQL syntax, but offers better performance and has less corporate interference in the development process. == Managing MySQL == All common management tasks can be performed through our control panel [https://ucc.ulyssis.org UCC], under the MySQL section. ===Creating a MySQL user=== To use MySQL on your ULYSSIS account, you first need to create a MySQL user on [https://ucc.ulyssis.org UCC]. In the MySQL section of the panel, you will be suggested to click a link to create a user. Then fill in a password for the database user. It is highly recommended that this password differs from the password you use for your account. Finally, click ''Create user'' and you are ready to go. ===Creating a MySQL database=== After having created a MySQL user, you can click ''Add database'' in [https://ucc.ulyssis.org UCC] and enter the name for your new database. It will automatically be prefixed by your username. ===Deleting a MySQL database=== If you no longer need a database, you can easily remove it by clicking on ''MySQL'' in [https://ucc.ulyssis.org UCC] and then pressing on ''Remove database'' next to the database you would like to delete. After confirming, the database and all its tables and other contents will be gone. For security reasons, you can't remove databases using an SQL query like DROP DATABASE, but have to go through UCC. == Accessing MySQL == Our MySQL and PostgreSQL databases run on a separate database server, this means you may need to enter a specific host, together with the correct credentials, to access your database within a website or application. You may also wish to use a common tool such as PHPMyAdmin or access a database remotely. Details on how to do that are available in the sections below. ===Using MySQL for your website or application=== Host: mysql.ulyssis.org Username: your account's username Password: the password you chose when you made the MySQL user Database: the database name you chose, prefixed by your username For example, if my username is foobar, I made a database called website and I were to create a PHP website I would use something like: <syntaxhighlight lang="php">$db = new mysqli('mysql.ulyssis.org', 'foobar', 'correct horse battery staple', 'foobar_website');</syntaxhighlight> or <syntaxhighlight lang="php">$db = new PDO('mysql:host=mysql.ulyssis.org;dbname=foobar_website', 'foobar', 'correct horse battery staple');</syntaxhighlight> ===Accessing MySQL with PHPMyAdmin or Adminer=== Using your username and password you can easily manage your MySQL databases, tables and records on https://phpmyadmin.ulyssis.org and https://adminer.ulyssis.org. Documentation is also available to aid in [[using PHPMyAdmin]] and [[using Adminer]]. ===Accessing MySQL from outside of our network=== To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH tunnel. In many MySQL management tools this is already supported. ==== MySQL Workbench ==== While [https://www.mysql.com/products/workbench/ MySQL Workbench] might not fully support our MySQL database, all commonly used operations work perfectly. You can connect to our database using MySQL Workbench by creating a connection as follows ([username] should be replaced by your username, of course): [[File:MySQL_Workbench_SSH.png]] ==== Linux, Mac OSX ==== On Linux, Mac OSX and other Unix-like Operating Systems it is also easily possible to use the following command to create a tunnel to a local port (in this case 3300) ssh username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N While this command is running, you can connect to the MySQL server with host 'localhost' and port '3300'. To terminate the port forwarding, press ctrl-C in the terminal. You can use "ssh -f username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N": the f-argument will put the command in the background. [[Category:Databases]] d5d03e6c6d0b3c8e4a227cb05353648320380206 0 5 1202 1122 2020-12-20T22:58:51Z Bert 8 wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Connecting== {{notice|Keep in mind|Our automatic security systems may temporarily prevent you from connecting over SSH/SFTP if you try to connect several times with the wrong username and/or password. This will result in the connection being refused. You can switch between sftp://ssh1.ulyssis.org and sftp://ssh2.ulyssis.org when this happens or wait 10 minutes. More information on our security measures is available on [[ULYSSIS security measures]]}} ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. If your distribution does not contain an option to connect to a server, you can use [https://filezilla-project.org/ FileZilla], which is completely free. See the instructions under [[Accessing_your_files#Windows|Windows]]. [[File:UbuntuConnectToServer.png]] ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/ FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png]] ===Mac=== ''[https://filezilla-project.org/ FileZilla], which was mentioned above, is also available for Mac. To use it, follow [[#Windows|the instructions for Windows]]. You can also opt for [http://cyberduck.io/ Cyberduck], though. In that case, follow the instructions below.'' Download the free and open source program [http://cyberduck.io/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> [[File:maccyberduck3.png]] Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. If you want to connect again later on, you can just click the Bookmarks icon on the top left. Next you click on History. And then you can double click to re-open the connection. ==Using FileZilla== When you connect to a server using FileZilla, the following layout will appear: [[File:Base_layout.png|700px]] As you can see, the local files are located on the left-hand side, while the remote (server) files are located on the right-hand side. File navigation and paths are also present. [[File:Layout.png|700px]] To transfer a file or folder, you can drag and drop it, either from the local side to the remote side, or from the remote side to the local side. These operations represent uploading and downloading respectively. [[File:Transfer.png|700px]] You can also press enter while selecting a file, or double-click a file, to transfer it. [[File:Transfer2.png|700px]] To open a folder, you can double-click it, or press enter while selecting it. [[File:Open.png|700px]] You can delete files or folders by pressing the delete button while selecting them, or by right-clicking and clicking 'delete'. [[File:Delete.png|700px]] To create files or folders remotely, you can right-click the remote window and click 'create directory' or 'create new file'. [[File:Create_directory.png|700px]] [[File:Create_file.png|700px]] As you can see, the menu has some more interesting options, for example 'rename' or 'view/edit'. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): scp file.txt username@ssh1.ulyssis.org:/home/user/username For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. [[Category:Files]] [[Category:Shell]] cff421300975a8a834bae85ffbce1625619b9322 0 143 1203 1071 2020-12-21T10:28:31Z Bert 8 wikitext text/x-wiki At ULYSSIS we try to prevent as much spam as possible from ending up in our users mailboxes or being passed through forwarders. However, as we offer email to many organisations that post information in several languages, we also attract a lot of non-English spam. Because of this, regular spam filters may miss out on some of the spam. To further prevent spam from being delivered, we've not only enabled extra features to look for bulk emails, dubious cryptocurrency hashes and unexpected languages, but we've also written many custom spam tests based on common patterns within spam our users receive. We depend on gathering samples of spam and comparing them to regular email to decide what kind of custom test may be useful and what score we should give it. We therefore encourage users who receive spam in their ULYSSIS mailbox or through a forwarder hosted on our services to forward us their spam on [mailto:spam-analysis@ulyssis.org spam-analysis@ulyssis.org]. Keep in mind that we can achieve much better results if you supply us with all the headers when you forward your spam. You can refer to [https://www.auckland.ac.nz/en/students/safe-computing/recognising-online-threats/forward-email-headers.html this guide] by the University of Auckland if you don't know how to do this. Spammers are also free to send us as much email as they like on [mailto:spam-analysis@ulyssis.org spam-analysis@ulyssis.org]! [[Category:Mail]] c781fe5324ad4807f2c00b4485c0a92b7231263d 0 145 1204 1112 2020-12-21T10:32:03Z Bert 8 wikitext text/x-wiki This page lists the changes to the webservers of ULYSSIS in the summer of 2020, and how you can prepare for it. If any of these instructions are not clear to you, or if you have some more questions about the changes, '''don't hesitate to e-mail us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]'''. == When are the changes planned? == The changes will be in effect after the downtime in September when we upgrade all of our servers. The exact date has not yet been decided. We will contact our users once it has. After that, we will use the new webserver configuration. == What will change? == We will upgrade the Ubuntu release on our servers from 18.04 LTS to 20.04 LTS. This will include newer version of many services. An overview of the most important version changes can be found below. For other services/packages, you can always use the [https://packages.ubuntu.com/ Ubuntu Package Search]. The distribution name for Ubuntu 20.04 LTS is "focal". * PHP will be updated from 7.2 to 7.4 * PostgreSQL will be updated from 10 to 12 * MariaDB (MySQL) will be updated from 10.1.44 to 10.3.22 * Python will be updated from 3.6 to 3.8 Note that any existing Python virtual environments in use will need to be recreated in order to function properly. Additionally, we will make use of the maintenance window to change certain aspects of our services. Notably, we will no longer support the user of <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> files. Instead, users are advised to use <code>.user.ini</code> files. More details regarding the changes can be found on the remainder of this page. === Support for <code>php_flag</code> and <code>php_value</code> === {{info|To help users trying to find out if their accounts still contain problematic cases of php_flag and php_value, we've introduced a [https://docs.ulyssis.org/summer2020tool/ simple tool] that tries to automatically check all .htaccess files that are in use.}} Support for <code>php_flag</code> and <code>php_value</code> in <code>.htaccess</code> as described in older versions of [[Special:PermanentLink/714|Managing PHP errors]] and [[Special:PermanentLink/715|Setting PHP options]] will no longer be supported. If you have added these options, you will have to remove them and migrate them to a <code>.user.ini</code> file. The current versions of these pages ([[Managing PHP errors]] and [[Setting PHP options]]) explain how you can do this. Note that if the options are inside a block that checks for the existence of a specific version of <code>mod_php</code>, then this will not cause an error. This is the case for many CMSs. === Basic Auth in PHP and FCGI scripts === When using Basic authentication on a PHP or FCGI script, it was necessary to apply a [[Basic authentication|workaround]]. This will no longer be needed in the future as the Authorization header will be passed by default to the script. This behavior can be disabled using the CGIPassAuth directive. For more details see https://httpd.apache.org/docs/current/en/mod/core.html#cgipassauth . === Client IP address === Currently, the [[Getting Apache logs|Apache logs]] only show the proper client IP when unencrypted traffic is used (no HTTPS). When using HTTPS, the client IP is logged as 193.190.253.234, the IP address of our loadbalancer. During the maintenance, we will make the required changes to ensure that the logged IP address will be the client's IP address, even if HTTPS is used. Additionally, this will improve the effectiveness of the brute-force detection in place on our webservers for WordPress installations. For more information, see [[ULYSSIS security measures#CMSs and other popular software|ULYSSIS security measures]]. [[Category:Webserver]] 4649705c179e1cb1ac5ca47ff44461251ec53ba2 0 144 1205 1069 2020-12-21T10:33:38Z Bert 8 wikitext text/x-wiki ULYSSIS considers security an important part of its services. While we of course make sure our software is up-to-date, there is also the security of the applications our users use, the emails they receive, and the account they have on our servers. Even though it's obvious our users are responsible for their own software, passwords and emails, we attempt to safeguard them from harm and adhere to good general standards as well as those agreed upon with KU Leuven ICTS when we started. == Web == As the main service of our hosting accounts, most of our security revolves around securing the many applications our users use. The main responsibility for these applications lies of course with the users who should frequently apply updates and make sure the code they write is secure. === General measures === Under normal circumstances, most web applications will not have interaction with non-http(s) third party applications and APIs (if they have any external interaction in the first place), therefore we only allow general outgoing connections from our webworkers to ports 80 and 443. Based on requests from users and ICTS, we do allow specific outgoing connections to the KU Leuven LDAP and KU Leuven Dingnet MQTT server. If you require access to an unusual port on a specific service, preferably of some kind of academic value or offered by KU Leuven, feel free to contact us with a description of what you would like to do and what services, IP addresses and ports are relevant (and why). As part of our arrangement with KU Leuven ICTS, we pass all our mail through their central email and anti-virus system (CAV). Because of this restriction, it's not possible to connect to external services for email from within our network. You can however easily use local email on our servers, which will be processed as you would expect. To prevent spam and other problems, we do monitor volume and assess spaminess before forwarding emails. More details are available on [[Sending email from websites]] and in the section about email on this page. Most users are aware of Google and Bing, as well as their bots that scan the internet for interesting and useful websites. There are however many other search bots out there, some of which have far from the best reputation. These cause problems with high amounts of traffic due to lack of rate limiting within these bots (which can create problems for resource usage) and almost always collect data for commercial use within products such as SEO services. As these search bots bring no real benefits to our users, bots such as AhrefsBot, Majestic12 and LinkdexBot have been blocked from visiting our webservers in general. Beyond these measures, we also make sure to follow-up any problematic situation and move to suspend the user or website to prevent further harm. Some of these situations include sudden spikes in resource usage, unexpected large email queues, large email delivery failures, high amounts of attempts to connect to blocked ports, or the use of very insecure/outdated software. === CMSs and other popular software === On CMSs and certain pieces of popular software, security is even more important as they are often attacked. Installing updates frequently is therefore paramount. To make sure updates are taken seriously, we have implemented a [[Software Version Checker]] for organisation and kring accounts. Beyond updates, common or short passwords can also be a big problem with CMSs. With the growing popularity of WordPress, we've noticed more frequent dictionary and brute force attacks on WordPress login forms and XML RPC management interfaces. To protect our users, as well as to prevent problematic increases in traffic and resource usage, we automatically block IPs that attempt to access wp-login.php or xmlrpc.php too often and we've installed extra monitoring systems. This of course doesn't mean we don't expect our users to use strong passwords and perhaps even consider disabling XML RPC. == Email and spam == All emails that are processed by ULYSSIS pass through our spam setup as well as the central anti-virus (CAV) of the KU Leuven. While the KU Leuven focuses specifically on malware, we apply a more broad approach. Every email is given a spam score based on its headers and content. The score and tests are included in every email. If the score surpasses 5.0, the email is marked as spam but still delivered, if it surpasses 7.5 it is no longer delivered. Emails that include executables (even hidden within an archive or a screensaver) are never delivered and our team is notified. As we receive a lot of exotic spam that is often not in English, regular spam rules often don't suffice to prevent spam from being delivered. At ULYSSIS we therefore use a large set of custom spam rules we've written based on samples. Please refer to the [[spam]] article on this documentation website for details on how to submit spam samples. If you are having issues with emails that are processed by our servers being marked as spam, keep in mind that as our email has to pass through the CAV, we depend on the KU Leuven to maintain a good reputation with other email providers. == Other == Beyond specific measures on our web and email services, we also take certain security measures on other services or on our entire network. === Shellservers === On our shellservers we implement a simple technique to prevent brute forcing or dictionary attacks through SSH by temporarily blocking IP addresses after several failed login attempts. While this usually goes completely unnoticed by users, in circumstances where a user uses the wrong password many times, they may get hit by this security measure and would have to either wait for a few minutes or try to connect to our other shellserver. Similar to all of our webservers, connecting to external email servers is not allowed. You can refer to that part of this article or to [[Sending email from websites]] for more information. === Blocklists === We maintain automatic as well as manual blocklists to prevent spam and attacks from IP addresses or ranges that are known to commit these kinds of actions. We only block those IP addresses that have been implicated in illegal activities, and try to always prevent undue implications for addresses within the same range that have not necessarily been part of any activity. In case of addresses that may change operator, we may also consider a block to be temporary. [[Category:Security & anti-spam‏‎]] [[Category:Webserver]] [[Category:Mail]] [[Category:Shell]] 8c4e08da96a411cd6052d7ec1491bcc3eb9c9b92 1210 1205 2021-01-20T14:22:40Z Bert 8 wikitext text/x-wiki ULYSSIS considers security an important part of its services. While we of course make sure our software is up-to-date, there is also the security of the applications our users use, the emails they receive, and the account they have on our servers. Even though it's obvious our users are responsible for their own software, passwords and emails, we attempt to safeguard them from harm and adhere to good general standards as well as those agreed upon with KU Leuven ICTS when we started. == Web == As the main service of our hosting accounts, most of our security revolves around securing the many applications our users run. The main responsibility for these applications lies of course with the users who should frequently apply updates and make sure the code they write is secure. === General measures === Under normal circumstances, most web applications will not have interaction with non-http(s) third party applications and APIs (if they have any external interaction in the first place), therefore we only allow general outgoing connections from our webworkers to ports 80 and 443. Based on requests from users and ICTS, we do allow specific outgoing connections to the KU Leuven LDAP and KU Leuven Dingnet MQTT server. If you require access to an unusual port on a specific service, preferably of some kind of academic value or offered by KU Leuven, feel free to contact us with a description of what you would like to do and what services, IP addresses and ports are relevant (and why). As part of our arrangement with KU Leuven ICTS, we pass all our mail through their central email and anti-virus system (CAV). Because of this restriction, it's not possible to connect to external services for email from within our network. You can however easily use local email on our servers, which will be processed as you would expect. To prevent spam and other problems, we do monitor volume and assess spaminess before forwarding emails. More details are available on [[Sending email from websites]] and in the section about email on this page. Most users are aware of Google and Bing, as well as their bots that scan the internet for interesting and useful websites. There are however many other search bots out there, some of which have far from the best reputation. These cause problems with high amounts of traffic due to lack of rate limiting within these bots (which can create problems for resource usage) and almost always collect data for commercial use within products such as SEO services. As these search bots bring no real benefits to our users, bots such as AhrefsBot, Majestic12 and LinkdexBot have been blocked from visiting our webservers in general. Beyond these measures, we also make sure to follow-up any problematic situation and move to suspend the user or website to prevent further harm. Some of these situations include sudden spikes in resource usage, unexpected large email queues, large email delivery failures, high amounts of attempts to connect to blocked ports, or the use of very insecure/outdated software. === CMSs and other popular software === On CMSs and certain pieces of popular software, security is even more important as they are often attacked. Installing updates frequently is therefore paramount. To make sure updates are taken seriously, we have implemented a [[Software Version Checker]] for organisation and kring accounts. Beyond updates, common or short passwords can also be a big problem with CMSs. With the growing popularity of WordPress, we've noticed more frequent dictionary and brute force attacks on WordPress login forms and XML RPC management interfaces. To protect our users, as well as to prevent problematic increases in traffic and resource usage, we automatically block IPs that attempt to access wp-login.php or xmlrpc.php too often and we've installed extra monitoring systems. This of course doesn't mean we don't expect our users to use strong passwords and perhaps even consider disabling XML RPC. == Email and spam == All emails that are processed by ULYSSIS pass through our spam setup as well as the central anti-virus (CAV) of the KU Leuven. While the KU Leuven focuses specifically on malware, we apply a more broad approach. Every email is given a spam score based on its headers and content. The score and tests are included in every email. If the score surpasses 5.0, the email is marked as spam but still delivered, if it surpasses 7.5 it is no longer delivered. Emails that include executables (even hidden within an archive or a screensaver) are never delivered and our team is notified. As we receive a lot of exotic spam that is often not in English, regular spam rules often don't suffice to prevent spam from being delivered. At ULYSSIS we therefore use a large set of custom spam rules we've written based on samples. Please refer to the [[spam]] article on this documentation website for details on how to submit spam samples. If you are having issues with emails that are processed by our servers being marked as spam, keep in mind that as our email has to pass through the CAV, we depend on the KU Leuven to maintain a good reputation with other email providers. == Other == Beyond specific measures on our web and email services, we also take certain security measures on other services or on our entire network. === Shellservers === On our shellservers we implement a simple technique to prevent brute forcing or dictionary attacks through SSH by temporarily blocking IP addresses after several failed login attempts. While this usually goes completely unnoticed by users, in circumstances where a user uses the wrong password many times, they may get hit by this security measure and would have to either wait for a few minutes or try to connect to our other shellserver. Similar to all of our webservers, connecting to external email servers is not allowed. You can refer to that part of this article or to [[Sending email from websites]] for more information. === Blocklists === We maintain automatic as well as manual blocklists to prevent spam and attacks from IP addresses or ranges that are known to commit these kinds of actions. We only block those IP addresses that have been implicated in illegal activities, and try to always prevent undue implications for addresses within the same range that have not necessarily been part of any activity. In case of addresses that may change operator, we may also consider a block to be temporary. [[Category:Security & anti-spam‏‎]] [[Category:Webserver]] [[Category:Mail]] [[Category:Shell]] 34adc043dfb5808301b73588097023511817858d 0 152 1206 1174 2020-12-21T23:00:47Z Casper 39 wikitext text/x-wiki It's definitely possible to run multiple websites on a single ULYSSIS account. So you do not need to buy a new account to run a secondary website on. Very often this is used for running a wiki installation together with a WordPress installation, but in fact you can combine almost any CMS (like WordPress, Drupal or Joomla) or software. This is also called 'running multiple instances'. As an example: You have a primary WordPress installation on youroganization.be, but beside that you would also like a blog that runs on Joomla. By following this guide, you can have a main WordPress installation while also having a separate blog on blog.yourorganization.be . The "blog." of this URL is also called a subdomain. If you would like more information regarding you can visit [https://www.domain.com/blog/2019/01/15/subdomain/ this] website. So to run multiple installations on your website, you will need to follow a few steps: First of all, you will need access to one of our shell servers. If you need more information on how to do this, you can visit the following page: [[Accessing your files]]. Continuing, we need to make a new directory in your home folder, preferably next to the <code>www</code> folder where you installed the software that is running on your main website. It is also possible to install the new software to a new directory inside your <code>www</code>, but we do not recommend this for most users because it will be very confusing for later maintenance and updates. We also recommend to name the new directory to something obvious (e.g. a directory named <code>wiki</code> for a wiki installation), this will help future maintainers of your account. Next, you will need to send us an email at ulyssis@ulyssis.org to connect the the newly made directory to your subdomain. The information you need to send us is: the '''path''' to the new directory (often this will look something like this: /home/user/<your_username>/<name_of_the_directory>), and the '''subdomain''' you want this website to run on (e.g. blog.yourorganization.be). When you receive a reply back from us that everything is in order, you will need to follow the steps from https://docs.ulyssis.org/Setting_up_WordPress, https://docs.ulyssis.org/Setting_up_Joomla, https://docs.ulyssis.org/Setting_up_Drupal or something else. This depends on what software you are planning to install on the new subdomain. While running the setup for your software, make sure to you install it to the '''right directory''', and adjust the configurations where needed. If you have made edits to the .htaccess file for your website in the past, be cautious as it may interfere with your new installation on the subdomain. When everything is complete, you should now have another website running at e.g. <chosen_subdomain>.yourorganization.be . If you have further questions or problems regarding the guide above, do not hesitate to contact us. 897d4eeac54d1501af905a2d3bb7bac1d071faf7 1207 1206 2020-12-21T23:02:56Z Casper 39 wikitext text/x-wiki It's definitely possible to run multiple websites on a single ULYSSIS account. So you do not need to buy a new account to run a secondary website on. Very often this is used for running a wiki installation together with a WordPress installation, but in fact you can combine almost any CMS (like WordPress, Drupal or Joomla) or software. This is also called 'running multiple instances'. As an example: You have a primary WordPress installation on youroganization.be, but beside that you would also like a blog that runs on Joomla. By following this guide, you can have a main WordPress installation while also having a separate blog on blog.yourorganization.be . The "blog." of this URL is also called a subdomain. If you would like more information regarding subdomains and what they can be used for, you can visit [https://www.domain.com/blog/2019/01/15/subdomain/ this] website. So to run multiple installations on your website, you will need to follow a few steps: First of all, you will need access to one of our shell servers. If you need more information on how to do this, you can visit the following page: [[Accessing your files]]. Continuing, we need to make a new directory in your home folder, preferably next to the <code>www</code> folder where you installed the software that is running on your main website. It is also possible to install the new software to a new directory inside your <code>www</code>, but we do not recommend this for most users because it will be very confusing for later maintenance and updates. We also recommend to name the new directory to something obvious (e.g. a directory named <code>wiki</code> for a wiki installation), this will help future maintainers of your account. Next, you will need to send us an email at ulyssis@ulyssis.org to connect the the newly made directory to your subdomain. The information you need to send us is: the '''path''' to the new directory (often this will look something like this: /home/user/<your_username>/<name_of_the_directory>), and the '''subdomain''' you want this website to run on (e.g. blog.yourorganization.be). When you receive a reply back from us that everything is in order, you will need to follow the steps from https://docs.ulyssis.org/Setting_up_WordPress, https://docs.ulyssis.org/Setting_up_Joomla, https://docs.ulyssis.org/Setting_up_Drupal or something else. This depends on what software you are planning to install on the new subdomain. While running the setup for your software, make sure to you install it to the '''right directory''', and adjust the configurations where needed. If you have made edits to the .htaccess file for your website in the past, be cautious as it may interfere with your new installation on the subdomain. When everything is complete, you should now have another website running at e.g. <chosen_subdomain>.yourorganization.be . If you have further questions or problems regarding the guide above, do not hesitate to contact us. 11e3cc24bdd16b39df1c1b612908b05a063c5646 0 98 1208 1120 2021-01-12T23:55:42Z Yoa 30 /* Installation */ wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for login through the Central KU Leuven Login (Shibboleth). The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Central KU Leuven Login) enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest/download/MediaWikiShibboleth.zip github]. Unzip the zip file in the <code>extensions/</code> directory in your MediaWiki installation folder. Make sure there is now a <code>MediaWikiShibboleth</code> folder in <code>extensions/</code>. Finally, locate the <code>LocalSettings.php</code> file in your MediaWiki installation folder and add the following lines to it: wfLoadExtension('MediaWikiShibboleth'); $wgGroupPermissions['*']['createaccount'] = false; $wgRevokePermissions['Shibboleth']['editmyprivateinfo'] = true; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 4 lines of the previous paragraph. This really defeats the purpose of the extension though. ==Configuration== MediaWikiShibboleth has some configuration options which allow for restricting who can log in to your wiki. These restrictions are cumulative. For example, it is possible to allow only students enrolled in a specific degree or programme to log in. These options work especially well with restricting the access of the wiki to logged-in users only. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code>LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code>LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code>LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow students enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code>LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. === Translations === It's possible to translate and modify all public MediaWikiShibboleth messages. The translations can be found in the <code>extensions/MediaWikiShibboleth/i18n/</code>. Dutch (<code>nl.json</code>) and English (<code>en.json</code>) translations are already provided. Even the provided translations can be customized, and we strongly advise you to do so, in order to match them with your Wiki situation. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Login without Central KU Leuven login" to expand a login menu. The new log in page looks like this with "Login without Central KU Leuven login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] [[Category:Security & anti-spam]] 716eee872485daf2d9f3435823c7ea01400c2d2f 1209 1208 2021-01-13T13:55:36Z Yoa 30 /* Installation */ wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for login through the Central KU Leuven Login (Shibboleth). The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Central KU Leuven Login) enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest/download/MediaWikiShibboleth.zip github]. Unzip the zip file in the <code>extensions/</code> directory in your MediaWiki installation folder. Make sure there is now a <code>MediaWikiShibboleth</code> folder in <code>extensions/</code>. Finally, locate the <code>LocalSettings.php</code> file in your MediaWiki installation folder and add the following lines to it: wfLoadExtension('MediaWikiShibboleth'); $wgGroupPermissions['*']['createaccount'] = false; $wgRevokePermissions['Shibboleth']['editmyprivateinfo'] = true; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 2 lines of the previous paragraph. This really defeats the purpose of the extension though. ==Configuration== MediaWikiShibboleth has some configuration options which allow for restricting who can log in to your wiki. These restrictions are cumulative. For example, it is possible to allow only students enrolled in a specific degree or programme to log in. These options work especially well with restricting the access of the wiki to logged-in users only. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code>LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code>LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code>LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow students enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code>LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. === Translations === It's possible to translate and modify all public MediaWikiShibboleth messages. The translations can be found in the <code>extensions/MediaWikiShibboleth/i18n/</code>. Dutch (<code>nl.json</code>) and English (<code>en.json</code>) translations are already provided. Even the provided translations can be customized, and we strongly advise you to do so, in order to match them with your Wiki situation. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Login without Central KU Leuven login" to expand a login menu. The new log in page looks like this with "Login without Central KU Leuven login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] [[Category:Security & anti-spam]] a3dc955fb856a274307b0d07bde5618b5fd51ed4 0 15 1214 1038 2021-02-27T11:49:54Z Pcy 37 fix grammar & wording wikitext text/x-wiki You can transfer the account of your (faculty) organization to a new webmaster. The new webmaster must have a valid Central KU Leuven Login. Otherwise, the new webmaster will not be able to accept the account transfer. The instructions below must be executed by the current account owner. * Log in to [https://ucc.ulyssis.org/ UCC]. * Click 'Transfer account' in the menu on the right. * Enter the details of the new account owner. Ensure the KULeuven email address is entered correctly. The new webmaster will receive an email to confirm the transfer. [[Category:Account]] 3e1e2336cd5ca29c98b3d8e3a423e55bd71de52b 0 154 1215 2021-03-06T23:22:42Z Vincenttc 21 Created page with "This page discusses what happens when you use more disk space than has been allotted to your account (your quota) and how to reduce your disk usage. This page is also useful i..." wikitext text/x-wiki This page discusses what happens when you use more disk space than has been allotted to your account (your quota) and how to reduce your disk usage. This page is also useful if you want to reduce your disk usage even if you're not using more than your quota. You can check your current disk usage as well as your quota on https://ucc.ulyssis.org/quota . == What happens when I go over my quota? == If you are user more disk space than your quota for more than seven consecutive days, you will no longer be able to write any additional files or extend existing files. You will probably no longer be able to edit websites on your account or it might even stop working outright. If you haven't configured a forwarder for your <code>''username''@ulyssis.org</code> email address, you will lose emails send to this address. The grace period of seven days is intended for you to have time to reduce your disk space. You will receive an email every day reminding you that you are using to much disk space. In order to prevent impact on other users during this seven day period, an additional quota slightly higher than your normal quota is imposed, independent of whether the grace period has passed or not. == Identifying which files & folders use the most disk space == It is not always easy to immediately identify what is using up your disk space on your account. Sadly, * SSH to one of the shell servers: https://docs.ulyssis.org/Accessing_shell_servers_over_SSH * Type in <code>ncdu</code> and press enter. You will then see that <code>ncdu</code> is scanning your account. * Once it has finished scanning it will show which files or folders directly in your home directory are using the most disk space. When the filename stars with <code>/</code> it is a folder. * You select different files/folders using the '''up and down arrow keys''', navigate the directory structure using the '''enter and escape''' keys, quit ncdu by pressing '''q''' and delete a file or folder with '''d'''. Be careful to not delete files you still need as you will need to contact us in order to restore them from a backup. * You can check your progress on https://ucc.ulyssis.org/quota b54a645ce0e3008ba50762dbd3f51dff5cda177f 1216 1215 2021-03-06T23:28:04Z Vincenttc 21 /* Identifying which files & folders use the most disk space */ wikitext text/x-wiki This page discusses what happens when you use more disk space than has been allotted to your account (your quota) and how to reduce your disk usage. This page is also useful if you want to reduce your disk usage even if you're not using more than your quota. You can check your current disk usage as well as your quota on https://ucc.ulyssis.org/quota . == What happens when I go over my quota? == If you are user more disk space than your quota for more than seven consecutive days, you will no longer be able to write any additional files or extend existing files. You will probably no longer be able to edit websites on your account or it might even stop working outright. If you haven't configured a forwarder for your <code>''username''@ulyssis.org</code> email address, you will lose emails send to this address. The grace period of seven days is intended for you to have time to reduce your disk space. You will receive an email every day reminding you that you are using to much disk space. In order to prevent impact on other users during this seven day period, an additional quota slightly higher than your normal quota is imposed, independent of whether the grace period has passed or not. == Identifying which files & folders use the most disk space == It is not always easy to immediately identify what is using up your disk space on your account. Sadly, there do not exist good cross-platform tools to help with this. Instead, we will be using the tool '''ncdu''' which runs directly on one of our shell servers. You do not need to be proficient with command line interfaces in order to use this tool. However, should you get stuck, do not hesitate to contact us at <code>ulyssis@ulyssis.org</code>. * SSH to one of the shell servers: https://docs.ulyssis.org/Accessing_shell_servers_over_SSH * Type in <code>ncdu</code> and press enter. You will then see that <code>ncdu</code> is scanning your account. * Once it has finished scanning it will show which files or folders directly in your home directory are using the most disk space. When the filename stars with <code>/</code> it is a folder. * You select different files/folders using the '''up and down arrow keys''', navigate the directory structure using the '''enter and escape''' keys, quit ncdu by pressing '''q''' and delete a file or folder with '''d'''. Be careful to not delete files you still need as you will need to contact us in order to restore them from a backup. * You can check your progress on https://ucc.ulyssis.org/quota 8a4949a0bb2191ff2afb88a03c2e55e0523552af 1217 1216 2021-03-06T23:47:17Z Vincenttc 21 /* Identifying which files & folders use the most disk space */ wikitext text/x-wiki This page discusses what happens when you use more disk space than has been allotted to your account (your quota) and how to reduce your disk usage. This page is also useful if you want to reduce your disk usage even if you're not using more than your quota. You can check your current disk usage as well as your quota on https://ucc.ulyssis.org/quota . == What happens when I go over my quota? == If you are user more disk space than your quota for more than seven consecutive days, you will no longer be able to write any additional files or extend existing files. You will probably no longer be able to edit websites on your account or it might even stop working outright. If you haven't configured a forwarder for your <code>''username''@ulyssis.org</code> email address, you will lose emails send to this address. The grace period of seven days is intended for you to have time to reduce your disk space. You will receive an email every day reminding you that you are using to much disk space. In order to prevent impact on other users during this seven day period, an additional quota slightly higher than your normal quota is imposed, independent of whether the grace period has passed or not. == Identifying which files & folders use the most disk space == It is not always easy to immediately identify what is using up your disk space on your account. Sadly, there do not exist good cross-platform tools to help with this. Instead, we will be using the tool '''ncdu''' which runs directly on one of our shell servers. You do not need to be proficient with command line interfaces in order to use this tool, a step-by-step guide can be found below. However, should you get stuck, do not hesitate to contact us at <code>ulyssis@ulyssis.org</code>. * SSH to one of the shell servers: https://docs.ulyssis.org/Accessing_shell_servers_over_SSH * Type in <code>ncdu</code> and press enter. You will then see that <code>ncdu</code> is scanning your account. * Once it has finished scanning it will show which files or folders directly in your home directory are using the most disk space. When the filename stars with <code>/</code> it is a folder. * You select different files/folders using the '''up and down arrow keys''', navigate the directory structure using the '''enter and escape''' keys, quit ncdu by pressing '''q''' and delete a file or folder with '''d'''. Be careful to not delete files you still need as you will need to contact us in order to restore them from a backup. * You can check your progress on https://ucc.ulyssis.org/quota === Common sources of unnecessary disk usage === * Deleted emails: if you have deleted a substantial amount of emails (or some emails with large attachments) and they still exist in the ''Trash'' folder of your ''@ulyssis.org'' email account, they might take op a large amount of disk space. In order to actually delete them you will gave to empty this ''Trash'' folder. You can do this on https://webmail.ulyssis.org or by deleting the folder ''Maildir/.Trash'' using ncdu (see previous section). * Old websites: if you have older websites on your account that you are no longer using, it might be worth removing them in their entirety. If the deleted website uses a database (this will always be the case if your using WordPress, MediaWiki or another popular CMS), then you can delete that as well through our control panel: https://ucc.ulyssis.org. If this website had an associated (sub)domain, please send us an email to have it removed. 9d397553055ee8602d4fd050976beaeaf361c28e 1218 1217 2021-03-07T14:53:05Z Vincenttc 21 /* What happens when I go over my quota? */ wikitext text/x-wiki This page discusses what happens when you use more disk space than has been allotted to your account (your quota) and how to reduce your disk usage. This page is also useful if you want to reduce your disk usage even if you're not using more than your quota. You can check your current disk usage as well as your quota on https://ucc.ulyssis.org/quota . == What happens when I go over my quota? == If you are user more disk space than your quota for more than seven consecutive days, you will no longer be able to write any additional files or extend existing files. You will probably no longer be able to edit websites on your account or it might even stop working outright. If you haven't configured a forwarder for your <code>''username''@ulyssis.org</code> email address, you will lose emails send to this address. The grace period of seven days is intended for you to have time to reduce your disk space. You will receive an email every day reminding you that you are using to much disk space. In order to prevent impact on other users during this seven day period, an additional quota slightly higher than your normal quota is imposed, independent of whether the grace period has passed or not. == Identifying which files & folders use the most disk space == It is not always easy to immediately identify what is using up your disk space on your account. Sadly, there do not exist good cross-platform tools to help with this. Instead, we will be using the tool ''ncdu'' which runs directly on one of our shell servers. You do not need to be proficient with command line interfaces in order to use this tool, a step-by-step guide can be found below. However, should you get stuck, do not hesitate to contact us at <code>ulyssis@ulyssis.org</code>. * SSH to one of the shell servers: https://docs.ulyssis.org/Accessing_shell_servers_over_SSH * Type in <code>ncdu</code> and press enter. You will then see that <code>ncdu</code> is scanning your account. * Once it has finished scanning it will show which files or folders directly in your home directory are using the most disk space. When the filename stars with <code>/</code> it is a folder. * You select different files/folders using the '''up and down arrow keys''', navigate the directory structure using the '''enter and escape''' keys, quit ncdu by pressing '''q''' and delete a file or folder with '''d'''. Be careful to not delete files you still need as you will need to contact us in order to restore them from a backup. * You can check your progress on https://ucc.ulyssis.org/quota === Common sources of unnecessary disk usage === * Deleted emails: if you have deleted a substantial amount of emails (or some emails with large attachments) and they still exist in the ''Trash'' folder of your ''@ulyssis.org'' email account, they might take op a large amount of disk space. In order to actually delete them you will gave to empty this ''Trash'' folder. You can do this on https://webmail.ulyssis.org or by deleting the folder ''Maildir/.Trash'' using ncdu (see previous section). * Old websites: if you have older websites on your account that you are no longer using, it might be worth removing them in their entirety. If the deleted website uses a database (this will always be the case if your using WordPress, MediaWiki or another popular CMS), then you can delete that as well through our control panel: https://ucc.ulyssis.org. If this website had an associated (sub)domain, please send us an email to have it removed. f9fa9ed16cc02883f7e0da860376c3488a4abed4 1219 1218 2021-03-07T15:48:04Z Vincenttc 21 /* Identifying which files & folders use the most disk space */ wikitext text/x-wiki This page discusses what happens when you use more disk space than has been allotted to your account (your quota) and how to reduce your disk usage. This page is also useful if you want to reduce your disk usage even if you're not using more than your quota. You can check your current disk usage as well as your quota on https://ucc.ulyssis.org/quota . == What happens when I go over my quota? == If you are user more disk space than your quota for more than seven consecutive days, you will no longer be able to write any additional files or extend existing files. You will probably no longer be able to edit websites on your account or it might even stop working outright. If you haven't configured a forwarder for your <code>''username''@ulyssis.org</code> email address, you will lose emails send to this address. The grace period of seven days is intended for you to have time to reduce your disk space. You will receive an email every day reminding you that you are using to much disk space. In order to prevent impact on other users during this seven day period, an additional quota slightly higher than your normal quota is imposed, independent of whether the grace period has passed or not. == Identifying which files & folders use the most disk space == It is not always easy to immediately identify what is using up your disk space on your account. Sadly, there do not exist good cross-platform tools to help with this. Instead, we will be using the tool ''ncdu'' which runs directly on one of our shell servers. You do not need to be proficient with command line interfaces in order to use this tool, a step-by-step guide can be found below. However, should you get stuck, do not hesitate to contact us at <code>ulyssis@ulyssis.org</code>. * SSH to one of the shell servers: https://docs.ulyssis.org/Accessing_shell_servers_over_SSH * Type in <code>ncdu</code> and press enter. You will then see that <code>ncdu</code> is scanning your account. * Once it has finished scanning it will show which files or folders directly in your home directory are using the most disk space. When the filename stars with <code>/</code> it is a folder. * You select different files/folders using the '''up and down arrow keys''', navigate the directory structure using the '''enter and escape''' keys, quit ncdu by pressing '''q''' and delete a file or folder with '''d'''. Be careful to not delete files you still need as you will need to contact us in order to restore them from a backup. * You can check your progress on https://ucc.ulyssis.org/quota === Common sources of unnecessary disk usage === * Deleted emails (or emails in general): if you have deleted a substantial amount of emails (or some emails with large attachments) and they still exist in the ''Trash'' folder of your ''@ulyssis.org'' email account, they might take op a large amount of disk space. In order to actually delete them you will gave to empty this ''Trash'' folder. You can do this on https://webmail.ulyssis.org or by deleting the folder ''Maildir/.Trash'' using ncdu (see previous section). * Old websites: if you have older websites on your account that you are no longer using, it might be worth removing them in their entirety. If the deleted website uses a database (this will always be the case if your using WordPress, MediaWiki or another popular CMS), then you can delete that as well through our control panel: https://ucc.ulyssis.org. If this website had an associated (sub)domain, please send us an email to have it removed. * Unused images: in the case of many CMS's (WordPress, Drupal, ...), removing an image from a post will not delete it. For example, in the case of WordPress it will still be available through the [https://wordpress.com/support/media/deleting-files/ Media Library]. In order to reclaim the disk space used by the image, you will have to delete it there as well. * Large images: images are often several MBs in size and often have a large resolution. While this is great for editing, printing, ..., such large sizes are not all that useful for inclusion in a webpage. They can make your side load slower and use more disk space without a significant increase in quality. You should therefore consider resizing images before uploading them or installing a plugin that reduces their size on upload. However, do watch out for plugins that keep the original image around as this will not reduce but increase your disk usage. For a tutorial on how to resize images, you can take a look at https://wordpress.com/support/media/image-optimization/. This tutorial is geared towards WordPress, but is also applicable in general. If you are using MediaWiki, we have written a plugin that reduces the size of various type of files. You can find more details on [[Setting up MediaWiki#Extensions|Setting up MediaWiki - Extensions]]. * Backups: ULYSSIS makes daily backups of all account data, including databases, and keeps them for at least a month. It is therefore not necessary to make automated backups of your own, for example with plugins like [https://nl.wordpress.org/plugins/updraftplus/ Updraft] in the case of WordPress. Although it is a good practice to make backups whenever you make changes to your site (for example, before performing updates), it is not necessary to keep them after you have verified that your site still works. de22c7f8c9ac4d98a6a3e1a04c77230a2b0b15e1 1220 1219 2021-03-07T16:40:51Z Bert 8 wikitext text/x-wiki This page discusses what happens when you use more disk space than has been allotted to your account (your quota) and how to reduce your disk usage. This page is also useful if you want to reduce your disk usage even if you're not using more than your quota. You can check your current disk usage as well as your quota on https://ucc.ulyssis.org/quota . == What happens when I go over my quota? == If you are using more disk space than the allowed quota for your account type for more than seven consecutive days (the so called grace period), you will no longer be able to write any additional files or extend existing files. You will probably no longer be able to edit websites on your account or it might even stop working outright. If you haven't configured a forwarder for your <code>''username''@ulyssis.org</code> email address, you will lose emails sent to this address. The grace period of seven days is intended for you to have time to reduce your disk space. You will receive an email every day reminding you that you are using too much disk space. In order to prevent impact on other users in cases where disk usage within an account suddenly and substantially surges, an additional quota slightly higher than your normal quota is imposed, independent of any grace period. == Identifying which files & folders use the most disk space == It is not always easy to immediately identify what is taking up space on your account. Sadly, there's no dependable cross-platform tools to help with this. Instead, we will be using the command line tool ''ncdu'', which runs directly on one of our shell servers. You do not need to be proficient with command line interfaces in order to use this tool, the step-by-step manual below will guide you through the process. However, should you get stuck, do not hesitate to contact us at <code>ulyssis@ulyssis.org</code>. * Connect through SSH to one of the shell servers: https://docs.ulyssis.org/Accessing_shell_servers_over_SSH * Type in <code>ncdu</code> and press enter. You will then see that <code>ncdu</code> is scanning your account. * Once <code>ncdu</code> has finished scanning, it will display which files or folders located directly in your home directory are using the most disk space. When the filename stars with <code>/</code> it is a folder. The results are ordered by size, so it makes most sense to start with the top items. * You can select different files/folders using the '''up and down arrow keys''', navigate the directory structure using either the '''enter and backspace''' keys or the '''left and right''' arrows to move in and out of folders, quit ncdu by pressing '''q''' and delete a file or folder with '''d'''. Be careful to not delete files you still need as you will need to contact us in order to restore them from a backup. * You can check your progress on https://ucc.ulyssis.org/quota. The percentage and values displayed are always current and accurate, there is no delay. === Common sources of unnecessary disk usage === * Deleted emails (or emails in general): if you have deleted a substantial amount of emails (or some emails with large attachments) and they still exist in the ''Trash'' folder of your ''@ulyssis.org'' email account, they might take op a large amount of disk space. In order to actually delete them you will gave to empty this ''Trash'' folder. You can do this on https://webmail.ulyssis.org or by deleting the folder ''Maildir/.Trash'' using ncdu (see previous section). * Old websites: if you have older websites on your account that you are no longer using, it might be worth removing them in their entirety. If the deleted website uses a database (this will always be the case if your using WordPress, MediaWiki or another popular CMS), then you can delete that as well through our control panel: https://ucc.ulyssis.org. If this website had an associated (sub)domain, please send us an email to have it removed. * Unused images: in the case of many CMS's (WordPress, Drupal, ...), removing an image from a post will not delete it. For example, in the case of WordPress it will still be available through the [https://wordpress.com/support/media/deleting-files/ Media Library]. In order to reclaim the disk space used by the image, you will have to delete it there as well. * Large images: images are often several MBs in size and often have a large resolution. While this is great for editing, printing, ..., such large sizes are not all that useful for inclusion in a webpage. They can make your side load slower and use more disk space without a significant increase in quality. You should therefore consider resizing images before uploading them or installing a plugin that reduces their size on upload. However, do watch out for plugins that keep the original image around as this will not reduce but increase your disk usage. For a tutorial on how to resize images, you can take a look at https://wordpress.com/support/media/image-optimization/. This tutorial is geared towards WordPress, but is also applicable in general. If you are using MediaWiki, we have written a plugin that reduces the size of various type of files. You can find more details on [[Setting up MediaWiki#Extensions|Setting up MediaWiki - Extensions]]. * Backups: ULYSSIS makes daily backups of all account data, including databases, and keeps them for at least a month. It is therefore not necessary to make automated backups of your own, for example with plugins like [https://nl.wordpress.org/plugins/updraftplus/ Updraft] in the case of WordPress. Although it is a good practice to make backups whenever you make changes to your site (for example, before performing updates), it is not necessary to keep them after you have verified that your site still works. 0ad7a53ab33c4248faf99fbbd6f9d894f06c8ef7 1221 1220 2021-03-07T16:53:47Z Vincenttc 21 /* Identifying which files & folders use the most disk space */ wikitext text/x-wiki This page discusses what happens when you use more disk space than has been allotted to your account (your quota) and how to reduce your disk usage. This page is also useful if you want to reduce your disk usage even if you're not using more than your quota. You can check your current disk usage as well as your quota on https://ucc.ulyssis.org/quota . == What happens when I go over my quota? == If you are using more disk space than the allowed quota for your account type for more than seven consecutive days (the so called grace period), you will no longer be able to write any additional files or extend existing files. You will probably no longer be able to edit websites on your account or it might even stop working outright. If you haven't configured a forwarder for your <code>''username''@ulyssis.org</code> email address, you will lose emails sent to this address. The grace period of seven days is intended for you to have time to reduce your disk space. You will receive an email every day reminding you that you are using too much disk space. In order to prevent impact on other users in cases where disk usage within an account suddenly and substantially surges, an additional quota slightly higher than your normal quota is imposed, independent of any grace period. == Identifying which files & folders use the most disk space == It is not always easy to immediately identify what is taking up space on your account. Sadly, there are no dependable cross-platform tools to help with this. Instead, we will be using the command line tool ''ncdu'', which runs directly on one of our shell servers. You do not need to be proficient with command line interfaces in order to use this tool, the step-by-step manual below will guide you through the process. However, should you get stuck, do not hesitate to contact us at <code>ulyssis@ulyssis.org</code>. * Connect through SSH to one of the shell servers: https://docs.ulyssis.org/Accessing_shell_servers_over_SSH * Type in <code>ncdu</code> and press enter. You will then see that <code>ncdu</code> is scanning your account. * Once <code>ncdu</code> has finished scanning, it will display which files or folders located directly in your home directory are using the most disk space. When the filename stars with <code>/</code> it is a folder. The results are ordered by size, so it makes most sense to start with the top items. * You can select different files/folders using the '''up and down arrow keys''', navigate the directory structure using either the '''enter and backspace''' keys or the '''left and right''' arrows to move in and out of folders, quit ncdu by pressing '''q''' and delete a file or folder with '''d'''. Be careful to not delete files you still need as you will need to contact us in order to restore them from a backup. * You can check your progress on https://ucc.ulyssis.org/quota. The percentage and values displayed are always current and accurate, there is no delay. === Common sources of unnecessary disk usage === * Deleted emails (or emails in general): if you have deleted a substantial amount of emails (or some emails with large attachments) and they still exist in the ''Trash'' folder of your ''@ulyssis.org'' email account, they might take op a large amount of disk space. In order to actually delete them you will gave to empty this ''Trash'' folder. You can do this on https://webmail.ulyssis.org or by deleting the folder ''Maildir/.Trash'' using ncdu (see previous section). * Old websites: if you have older websites on your account that you are no longer using, it might be worth removing them in their entirety. If the deleted website uses a database (this will always be the case if your using WordPress, MediaWiki or another popular CMS), then you can delete that as well through our control panel: https://ucc.ulyssis.org. If this website had an associated (sub)domain, please send us an email to have it removed. * Unused images: in the case of many CMS's (WordPress, Drupal, ...), removing an image from a post will not delete it. For example, in the case of WordPress it will still be available through the [https://wordpress.com/support/media/deleting-files/ Media Library]. In order to reclaim the disk space used by the image, you will have to delete it there as well. * Large images: images are often several MBs in size and often have a large resolution. While this is great for editing, printing, ..., such large sizes are not all that useful for inclusion in a webpage. They can make your side load slower and use more disk space without a significant increase in quality. You should therefore consider resizing images before uploading them or installing a plugin that reduces their size on upload. However, do watch out for plugins that keep the original image around as this will not reduce but increase your disk usage. For a tutorial on how to resize images, you can take a look at https://wordpress.com/support/media/image-optimization/. This tutorial is geared towards WordPress, but is also applicable in general. If you are using MediaWiki, we have written a plugin that reduces the size of various type of files. You can find more details on [[Setting up MediaWiki#Extensions|Setting up MediaWiki - Extensions]]. * Backups: ULYSSIS makes daily backups of all account data, including databases, and keeps them for at least a month. It is therefore not necessary to make automated backups of your own, for example with plugins like [https://nl.wordpress.org/plugins/updraftplus/ Updraft] in the case of WordPress. Although it is a good practice to make backups whenever you make changes to your site (for example, before performing updates), it is not necessary to keep them after you have verified that your site still works. e18cd2287f1550c5897061ab40e8626e89f16a53 1223 1221 2021-03-07T23:44:22Z Vincenttc 21 /* Identifying which files & folders use the most disk space */ wikitext text/x-wiki This page discusses what happens when you use more disk space than has been allotted to your account (your quota) and how to reduce your disk usage. This page is also useful if you want to reduce your disk usage even if you're not using more than your quota. You can check your current disk usage as well as your quota on https://ucc.ulyssis.org/quota . == What happens when I go over my quota? == If you are using more disk space than the allowed quota for your account type for more than seven consecutive days (the so called grace period), you will no longer be able to write any additional files or extend existing files. You will probably no longer be able to edit websites on your account or it might even stop working outright. If you haven't configured a forwarder for your <code>''username''@ulyssis.org</code> email address, you will lose emails sent to this address. The grace period of seven days is intended for you to have time to reduce your disk space. You will receive an email every day reminding you that you are using too much disk space. In order to prevent impact on other users in cases where disk usage within an account suddenly and substantially surges, an additional quota slightly higher than your normal quota is imposed, independent of any grace period. == Identifying which files & folders use the most disk space == [[File:Disk usage ncdu.png|thumb]] It is not always easy to immediately identify what is taking up space on your account. Sadly, there are no dependable cross-platform tools to help with this. Instead, we will be using the command line tool ''ncdu'', which runs directly on one of our shell servers. You do not need to be proficient with command line interfaces in order to use this tool, the step-by-step manual below will guide you through the process. However, should you get stuck, do not hesitate to contact us at <code>ulyssis@ulyssis.org</code>. * Connect through SSH to one of the shell servers: https://docs.ulyssis.org/Accessing_shell_servers_over_SSH * Type in <code>ncdu</code> and press enter. You will then see that <code>ncdu</code> is scanning your account. * Once <code>ncdu</code> has finished scanning, it will display which files or folders located directly in your home directory are using the most disk space. When the filename stars with <code>/</code> it is a folder. The results are ordered by size, so it makes most sense to start with the top items. * You can select different files/folders using the '''up and down arrow keys''', navigate the directory structure using either the '''enter and backspace''' keys or the '''left and right''' arrows to move in and out of folders, quit ncdu by pressing '''q''' and delete a file or folder with '''d'''. Be careful to not delete files you still need as you will need to contact us in order to restore them from a backup. * You can check your progress on https://ucc.ulyssis.org/quota. The percentage and values displayed are always current and accurate, there is no delay. === Common sources of unnecessary disk usage === * Deleted emails (or emails in general): if you have deleted a substantial amount of emails (or some emails with large attachments) and they still exist in the ''Trash'' folder of your ''@ulyssis.org'' email account, they might take op a large amount of disk space. In order to actually delete them you will gave to empty this ''Trash'' folder. You can do this on https://webmail.ulyssis.org or by deleting the folder ''Maildir/.Trash'' using ncdu (see previous section). * Old websites: if you have older websites on your account that you are no longer using, it might be worth removing them in their entirety. If the deleted website uses a database (this will always be the case if your using WordPress, MediaWiki or another popular CMS), then you can delete that as well through our control panel: https://ucc.ulyssis.org. If this website had an associated (sub)domain, please send us an email to have it removed. * Unused images: in the case of many CMS's (WordPress, Drupal, ...), removing an image from a post will not delete it. For example, in the case of WordPress it will still be available through the [https://wordpress.com/support/media/deleting-files/ Media Library]. In order to reclaim the disk space used by the image, you will have to delete it there as well. * Large images: images are often several MBs in size and often have a large resolution. While this is great for editing, printing, ..., such large sizes are not all that useful for inclusion in a webpage. They can make your side load slower and use more disk space without a significant increase in quality. You should therefore consider resizing images before uploading them or installing a plugin that reduces their size on upload. However, do watch out for plugins that keep the original image around as this will not reduce but increase your disk usage. For a tutorial on how to resize images, you can take a look at https://wordpress.com/support/media/image-optimization/. This tutorial is geared towards WordPress, but is also applicable in general. If you are using MediaWiki, we have written a plugin that reduces the size of various type of files. You can find more details on [[Setting up MediaWiki#Extensions|Setting up MediaWiki - Extensions]]. * Backups: ULYSSIS makes daily backups of all account data, including databases, and keeps them for at least a month. It is therefore not necessary to make automated backups of your own, for example with plugins like [https://nl.wordpress.org/plugins/updraftplus/ Updraft] in the case of WordPress. Although it is a good practice to make backups whenever you make changes to your site (for example, before performing updates), it is not necessary to keep them after you have verified that your site still works. 1c7685656736bca1942019ce447e46a83100e174 1224 1223 2021-03-07T23:44:39Z Vincenttc 21 /* Identifying which files & folders use the most disk space */ wikitext text/x-wiki This page discusses what happens when you use more disk space than has been allotted to your account (your quota) and how to reduce your disk usage. This page is also useful if you want to reduce your disk usage even if you're not using more than your quota. You can check your current disk usage as well as your quota on https://ucc.ulyssis.org/quota . == What happens when I go over my quota? == If you are using more disk space than the allowed quota for your account type for more than seven consecutive days (the so called grace period), you will no longer be able to write any additional files or extend existing files. You will probably no longer be able to edit websites on your account or it might even stop working outright. If you haven't configured a forwarder for your <code>''username''@ulyssis.org</code> email address, you will lose emails sent to this address. The grace period of seven days is intended for you to have time to reduce your disk space. You will receive an email every day reminding you that you are using too much disk space. In order to prevent impact on other users in cases where disk usage within an account suddenly and substantially surges, an additional quota slightly higher than your normal quota is imposed, independent of any grace period. == Identifying which files & folders use the most disk space == It is not always easy to immediately identify what is taking up space on your account. Sadly, there are no dependable cross-platform tools to help with this. Instead, we will be using the command line tool ''ncdu'', which runs directly on one of our shell servers. You do not need to be proficient with command line interfaces in order to use this tool, the step-by-step manual below will guide you through the process. However, should you get stuck, do not hesitate to contact us at <code>ulyssis@ulyssis.org</code>. * Connect through SSH to one of the shell servers: https://docs.ulyssis.org/Accessing_shell_servers_over_SSH * Type in <code>ncdu</code> and press enter. You will then see that <code>ncdu</code> is scanning your account. * Once <code>ncdu</code> has finished scanning, it will display which files or folders located directly in your home directory are using the most disk space. When the filename stars with <code>/</code> it is a folder. The results are ordered by size, so it makes most sense to start with the top items.[[File:Disk usage ncdu.png|thumb]] * You can select different files/folders using the '''up and down arrow keys''', navigate the directory structure using either the '''enter and backspace''' keys or the '''left and right''' arrows to move in and out of folders, quit ncdu by pressing '''q''' and delete a file or folder with '''d'''. Be careful to not delete files you still need as you will need to contact us in order to restore them from a backup. * You can check your progress on https://ucc.ulyssis.org/quota. The percentage and values displayed are always current and accurate, there is no delay. === Common sources of unnecessary disk usage === * Deleted emails (or emails in general): if you have deleted a substantial amount of emails (or some emails with large attachments) and they still exist in the ''Trash'' folder of your ''@ulyssis.org'' email account, they might take op a large amount of disk space. In order to actually delete them you will gave to empty this ''Trash'' folder. You can do this on https://webmail.ulyssis.org or by deleting the folder ''Maildir/.Trash'' using ncdu (see previous section). * Old websites: if you have older websites on your account that you are no longer using, it might be worth removing them in their entirety. If the deleted website uses a database (this will always be the case if your using WordPress, MediaWiki or another popular CMS), then you can delete that as well through our control panel: https://ucc.ulyssis.org. If this website had an associated (sub)domain, please send us an email to have it removed. * Unused images: in the case of many CMS's (WordPress, Drupal, ...), removing an image from a post will not delete it. For example, in the case of WordPress it will still be available through the [https://wordpress.com/support/media/deleting-files/ Media Library]. In order to reclaim the disk space used by the image, you will have to delete it there as well. * Large images: images are often several MBs in size and often have a large resolution. While this is great for editing, printing, ..., such large sizes are not all that useful for inclusion in a webpage. They can make your side load slower and use more disk space without a significant increase in quality. You should therefore consider resizing images before uploading them or installing a plugin that reduces their size on upload. However, do watch out for plugins that keep the original image around as this will not reduce but increase your disk usage. For a tutorial on how to resize images, you can take a look at https://wordpress.com/support/media/image-optimization/. This tutorial is geared towards WordPress, but is also applicable in general. If you are using MediaWiki, we have written a plugin that reduces the size of various type of files. You can find more details on [[Setting up MediaWiki#Extensions|Setting up MediaWiki - Extensions]]. * Backups: ULYSSIS makes daily backups of all account data, including databases, and keeps them for at least a month. It is therefore not necessary to make automated backups of your own, for example with plugins like [https://nl.wordpress.org/plugins/updraftplus/ Updraft] in the case of WordPress. Although it is a good practice to make backups whenever you make changes to your site (for example, before performing updates), it is not necessary to keep them after you have verified that your site still works. 085d44f9f788d94af8e0d9784ae4b9a289f50f1b 1226 1224 2021-03-07T23:47:01Z Vincenttc 21 /* Identifying which files & folders use the most disk space */ wikitext text/x-wiki This page discusses what happens when you use more disk space than has been allotted to your account (your quota) and how to reduce your disk usage. This page is also useful if you want to reduce your disk usage even if you're not using more than your quota. You can check your current disk usage as well as your quota on https://ucc.ulyssis.org/quota . == What happens when I go over my quota? == If you are using more disk space than the allowed quota for your account type for more than seven consecutive days (the so called grace period), you will no longer be able to write any additional files or extend existing files. You will probably no longer be able to edit websites on your account or it might even stop working outright. If you haven't configured a forwarder for your <code>''username''@ulyssis.org</code> email address, you will lose emails sent to this address. The grace period of seven days is intended for you to have time to reduce your disk space. You will receive an email every day reminding you that you are using too much disk space. In order to prevent impact on other users in cases where disk usage within an account suddenly and substantially surges, an additional quota slightly higher than your normal quota is imposed, independent of any grace period. == Identifying which files & folders use the most disk space == It is not always easy to immediately identify what is taking up space on your account. Sadly, there are no dependable cross-platform tools to help with this. Instead, we will be using the command line tool ''ncdu'', which runs directly on one of our shell servers. You do not need to be proficient with command line interfaces in order to use this tool, the step-by-step manual below will guide you through the process. However, should you get stuck, do not hesitate to contact us at <code>ulyssis@ulyssis.org</code>. * Connect through SSH to one of the shell servers: https://docs.ulyssis.org/Accessing_shell_servers_over_SSH * Type in <code>ncdu</code> and press enter. You will then see that <code>ncdu</code> is scanning your account. * Once <code>ncdu</code> has finished scanning, it will display which files or folders located directly in your home directory are using the most disk space. When the filename stars with <code>/</code> it is a folder. The results are ordered by size, so it makes most sense to start with the top items. * [[File:Disk usage ncdu.png|thumb]]You can select different files/folders using the '''up and down arrow keys''', navigate the directory structure using either the '''enter and backspace''' keys or the '''left and right''' arrows to move in and out of folders, quit ncdu by pressing '''q''' and delete a file or folder with '''d'''. Be careful to not delete files you still need as you will need to contact us in order to restore them from a backup. * You can check your progress on https://ucc.ulyssis.org/quota. The percentage and values displayed are always current and accurate, there is no delay. === Common sources of unnecessary disk usage === * Deleted emails (or emails in general): if you have deleted a substantial amount of emails (or some emails with large attachments) and they still exist in the ''Trash'' folder of your ''@ulyssis.org'' email account, they might take op a large amount of disk space. In order to actually delete them you will gave to empty this ''Trash'' folder. You can do this on https://webmail.ulyssis.org or by deleting the folder ''Maildir/.Trash'' using ncdu (see previous section). * Old websites: if you have older websites on your account that you are no longer using, it might be worth removing them in their entirety. If the deleted website uses a database (this will always be the case if your using WordPress, MediaWiki or another popular CMS), then you can delete that as well through our control panel: https://ucc.ulyssis.org. If this website had an associated (sub)domain, please send us an email to have it removed. * Unused images: in the case of many CMS's (WordPress, Drupal, ...), removing an image from a post will not delete it. For example, in the case of WordPress it will still be available through the [https://wordpress.com/support/media/deleting-files/ Media Library]. In order to reclaim the disk space used by the image, you will have to delete it there as well. * Large images: images are often several MBs in size and often have a large resolution. While this is great for editing, printing, ..., such large sizes are not all that useful for inclusion in a webpage. They can make your side load slower and use more disk space without a significant increase in quality. You should therefore consider resizing images before uploading them or installing a plugin that reduces their size on upload. However, do watch out for plugins that keep the original image around as this will not reduce but increase your disk usage. For a tutorial on how to resize images, you can take a look at https://wordpress.com/support/media/image-optimization/. This tutorial is geared towards WordPress, but is also applicable in general. If you are using MediaWiki, we have written a plugin that reduces the size of various type of files. You can find more details on [[Setting up MediaWiki#Extensions|Setting up MediaWiki - Extensions]]. * Backups: ULYSSIS makes daily backups of all account data, including databases, and keeps them for at least a month. It is therefore not necessary to make automated backups of your own, for example with plugins like [https://nl.wordpress.org/plugins/updraftplus/ Updraft] in the case of WordPress. Although it is a good practice to make backups whenever you make changes to your site (for example, before performing updates), it is not necessary to keep them after you have verified that your site still works. 8f076ed95688acef227009da2b8e4fa31a947902 1227 1226 2021-03-08T00:02:21Z Vincenttc 21 /* Identifying which files & folders use the most disk space */ wikitext text/x-wiki This page discusses what happens when you use more disk space than has been allotted to your account (your quota) and how to reduce your disk usage. This page is also useful if you want to reduce your disk usage even if you're not using more than your quota. You can check your current disk usage as well as your quota on https://ucc.ulyssis.org/quota . == What happens when I go over my quota? == If you are using more disk space than the allowed quota for your account type for more than seven consecutive days (the so called grace period), you will no longer be able to write any additional files or extend existing files. You will probably no longer be able to edit websites on your account or it might even stop working outright. If you haven't configured a forwarder for your <code>''username''@ulyssis.org</code> email address, you will lose emails sent to this address. The grace period of seven days is intended for you to have time to reduce your disk space. You will receive an email every day reminding you that you are using too much disk space. In order to prevent impact on other users in cases where disk usage within an account suddenly and substantially surges, an additional quota slightly higher than your normal quota is imposed, independent of any grace period. == Identifying which files & folders use the most disk space == It is not always easy to immediately identify what is taking up space on your account. Sadly, there are no dependable cross-platform tools to help with this. Instead, we will be using the command line tool ''ncdu'', which runs directly on one of our shell servers. You do not need to be proficient with command line interfaces in order to use this tool, the step-by-step manual below will guide you through the process. However, should you get stuck, do not hesitate to contact us at <code>ulyssis@ulyssis.org</code>. * Connect through SSH to one of the shell servers: https://docs.ulyssis.org/Accessing_shell_servers_over_SSH * Type in <code>ncdu</code> and press enter. You will then see that <code>ncdu</code> is scanning your account. * Once <code>ncdu</code> has finished scanning, it will display which files or folders located directly in your home directory are using the most disk space. When the filename stars with <code>/</code> it is a folder. The results are ordered by size, so it makes most sense to start with the top items. * You can select different files/folders using the '''up and down arrow keys''', navigate the directory structure using either the '''enter and backspace''' keys or the '''left and right''' arrows to move in and out of folders, quit ncdu by pressing '''q''' and delete a file or folder with '''d'''. Be careful to not delete files you still need as you will need to contact us in order to restore them from a backup. * You can check your progress on https://ucc.ulyssis.org/quota. The percentage and values displayed are always current and accurate, there is no delay.[[File:Disk usage ncdu.png|thumb|760x760px]] === Common sources of unnecessary disk usage === * Deleted emails (or emails in general): if you have deleted a substantial amount of emails (or some emails with large attachments) and they still exist in the ''Trash'' folder of your ''@ulyssis.org'' email account, they might take op a large amount of disk space. In order to actually delete them you will gave to empty this ''Trash'' folder. You can do this on https://webmail.ulyssis.org or by deleting the folder ''Maildir/.Trash'' using ncdu (see previous section). * Old websites: if you have older websites on your account that you are no longer using, it might be worth removing them in their entirety. If the deleted website uses a database (this will always be the case if your using WordPress, MediaWiki or another popular CMS), then you can delete that as well through our control panel: https://ucc.ulyssis.org. If this website had an associated (sub)domain, please send us an email to have it removed. * Unused images: in the case of many CMS's (WordPress, Drupal, ...), removing an image from a post will not delete it. For example, in the case of WordPress it will still be available through the [https://wordpress.com/support/media/deleting-files/ Media Library]. In order to reclaim the disk space used by the image, you will have to delete it there as well. * Large images: images are often several MBs in size and often have a large resolution. While this is great for editing, printing, ..., such large sizes are not all that useful for inclusion in a webpage. They can make your side load slower and use more disk space without a significant increase in quality. You should therefore consider resizing images before uploading them or installing a plugin that reduces their size on upload. However, do watch out for plugins that keep the original image around as this will not reduce but increase your disk usage. For a tutorial on how to resize images, you can take a look at https://wordpress.com/support/media/image-optimization/. This tutorial is geared towards WordPress, but is also applicable in general. If you are using MediaWiki, we have written a plugin that reduces the size of various type of files. You can find more details on [[Setting up MediaWiki#Extensions|Setting up MediaWiki - Extensions]]. * Backups: ULYSSIS makes daily backups of all account data, including databases, and keeps them for at least a month. It is therefore not necessary to make automated backups of your own, for example with plugins like [https://nl.wordpress.org/plugins/updraftplus/ Updraft] in the case of WordPress. Although it is a good practice to make backups whenever you make changes to your site (for example, before performing updates), it is not necessary to keep them after you have verified that your site still works. 59557761b0efc6a6f8d2a214619e97b4dc6ba88e 1229 1227 2021-03-08T00:10:59Z Vincenttc 21 wikitext text/x-wiki This page discusses what happens when you use more disk space than has been allotted to your account (your quota) and how to reduce your disk usage. This page is also useful if you want to reduce your disk usage even if you're not using more than your quota. You can check your current disk usage as well as your quota on https://ucc.ulyssis.org/quota . == What happens when I go over my quota? == If you are using more disk space than the allowed quota for your account type for more than seven consecutive days (the so called grace period), you will no longer be able to write any additional files or extend existing files. You will probably no longer be able to edit websites on your account or it might even stop working outright. If you haven't configured a forwarder for your <code>''username''@ulyssis.org</code> email address, you will lose emails sent to this address. The grace period of seven days is intended for you to have time to reduce your disk space. You will receive an email every day reminding you that you are using too much disk space. In order to prevent impact on other users in cases where disk usage within an account suddenly and substantially surges, an additional quota slightly higher than your normal quota is imposed, independent of any grace period. == Identifying which files & folders use the most disk space == It is not always easy to immediately identify what is taking up space on your account. Sadly, there are no dependable cross-platform tools to help with this. Instead, we will be using the command line tool ''ncdu'', which runs directly on one of our shell servers. You do not need to be proficient with command line interfaces in order to use this tool, the step-by-step manual below will guide you through the process. However, should you get stuck, do not hesitate to contact us at <code>ulyssis@ulyssis.org</code>. * Connect through SSH to one of the shell servers: https://docs.ulyssis.org/Accessing_shell_servers_over_SSH * Type in <code>ncdu</code> and press enter. You will then see that <code>ncdu</code> is scanning your account. * Once <code>ncdu</code> has finished scanning, it will display which files or folders located directly in your home directory are using the most disk space. When the filename stars with <code>/</code> it is a folder. The results are ordered by size, so it makes most sense to start with the top items. * You can select different files/folders using the '''up and down arrow keys''', navigate the directory structure using either the '''enter and backspace''' keys or the '''left and right''' arrows to move in and out of folders, quit ncdu by pressing '''q''' and delete a file or folder with '''d'''. Be careful to not delete files you still need as you will need to contact us in order to restore them from a backup. * You can check your progress on https://ucc.ulyssis.org/quota. The percentage and values displayed are always current and accurate, there is no delay.[[File:Disk usage ncdu.png|thumb|760x760px]] === Common sources of unnecessary disk usage === * Deleted emails (or emails in general): if you have deleted a substantial amount of emails (or some emails with large attachments) and they still exist in the ''Trash'' folder of your ''@ulyssis.org'' email account, they might take op a large amount of disk space. In order to actually delete them you will gave to empty this ''Trash'' folder. You can do this on https://webmail.ulyssis.org or by deleting the folder ''Maildir/.Trash'' using ncdu (see previous section). * Old websites: if you have older websites on your account that you are no longer using, it might be worth removing them in their entirety. If the deleted website uses a database (this will always be the case if your using WordPress, MediaWiki or another popular CMS), then you can delete that as well through our control panel: https://ucc.ulyssis.org. If this website had an associated (sub)domain, please send us an email to have it removed. * Unused images: in the case of many CMS's (WordPress, Drupal, ...), removing an image from a post will not delete it. For example, in the case of WordPress it will still be available through the [https://wordpress.com/support/media/deleting-files/ Media Library]. In order to reclaim the disk space used by the image, you will have to delete it there as well. * Large images: images are often several MBs in size and often have a large resolution. While this is great for editing, printing, ..., such large sizes are not all that useful for inclusion in a webpage. They can make your side load slower and use more disk space without a significant increase in quality. You should therefore consider resizing images before uploading them or installing a plugin that reduces their size on upload. However, do watch out for plugins that keep the original image around as this will not reduce but increase your disk usage. For a tutorial on how to resize images, you can take a look at https://wordpress.com/support/media/image-optimization/. This tutorial is geared towards WordPress, but is also applicable in general. If you are using MediaWiki, we have written a plugin that reduces the size of various type of files. You can find more details on [[Setting up MediaWiki#Extensions|Setting up MediaWiki - Extensions]]. * Backups: ULYSSIS makes daily backups of all account data, including databases, and keeps them for at least a month. It is therefore not necessary to make automated backups of your own, for example with plugins like [https://nl.wordpress.org/plugins/updraftplus/ Updraft] in the case of WordPress. Although it is a good practice to make backups whenever you make changes to your site (for example, before performing updates), it is not necessary to keep them after you have verified that your site still works. [[Category:Files]] d08da85d6a5e22fc2c5aa15918d7f06909cf8f9c 1230 1229 2021-03-08T00:13:47Z Vincenttc 21 wikitext text/x-wiki This page discusses what happens when you use more disk space than has been allotted to your account (your quota) and how to reduce your disk usage. This page is also useful if you want to reduce your disk usage even if you're not using more than your quota. You can check your current disk usage as well as your quota on https://ucc.ulyssis.org/quota . == What happens when I go over my quota? == If you are using more disk space than the allowed quota for your account type for more than seven consecutive days (the so called grace period), you will no longer be able to write any additional files or extend existing files. You will probably no longer be able to edit websites on your account or it might even stop working outright. If you haven't configured a forwarder for your <code>''username''@ulyssis.org</code> email address, you will lose emails sent to this address. The grace period of seven days is intended for you to have time to reduce your disk space. You will receive an email every day reminding you that you are using too much disk space. In order to prevent impact on other users in cases where disk usage within an account suddenly and substantially surges, an additional quota slightly higher than your normal quota is imposed, independent of any grace period. == Identifying which files & folders use the most disk space == It is not always easy to immediately identify what is taking up space on your account. Sadly, there are no dependable cross-platform tools to help with this. Instead, we will be using the command line tool ''ncdu'', which runs directly on one of our shell servers. You do not need to be proficient with command line interfaces in order to use this tool, the step-by-step manual below will guide you through the process. However, should you get stuck, do not hesitate to contact us at <code>ulyssis@ulyssis.org</code>. * Connect through SSH to one of the shell servers: https://docs.ulyssis.org/Accessing_shell_servers_over_SSH * Type in <code>ncdu</code> and press enter. You will then see that <code>ncdu</code> is scanning your account. * Once <code>ncdu</code> has finished scanning, it will display which files or folders located directly in your home directory are using the most disk space. When the filename stars with <code>/</code> it is a folder. The results are ordered by size, so it makes most sense to start with the top items. * You can select different files/folders using the '''up and down arrow keys''', navigate the directory structure using either the '''enter and backspace''' keys or the '''left and right''' arrows to move in and out of folders, quit ncdu by pressing '''q''' and delete a file or folder with '''d'''. Be careful to not delete files you still need as you will need to contact us in order to restore them from a backup. * You can check your progress on https://ucc.ulyssis.org/quota. The percentage and values displayed are always current and accurate, there is no delay.[[File:Disk usage ncdu.png|thumb|760x760px]] === Common sources of unnecessary disk usage === * Deleted emails (or emails in general): if you have deleted a substantial amount of emails (or some emails with large attachments) and they still exist in the ''Trash'' folder of your ''@ulyssis.org'' email account, they might take op a large amount of disk space. In order to actually delete them you will gave to empty this ''Trash'' folder. You can do this on https://webmail.ulyssis.org or by deleting the folder ''Maildir/.Trash'' using ncdu (see previous section). * Old websites: if you have older websites on your account that you are no longer using, it might be worth removing them in their entirety. If the deleted website uses a database (this will always be the case if your using WordPress, MediaWiki or another popular CMS), then you can delete that as well through our control panel: https://ucc.ulyssis.org. If this website had an associated (sub)domain, please send us an email to have it removed. * Unused images: in the case of many CMS's (WordPress, Drupal, ...), removing an image from a post will not delete it. For example, in the case of WordPress it will still be available through the [https://wordpress.com/support/media/deleting-files/ Media Library]. In order to reclaim the disk space used by the image, you will have to delete it there as well. * Large images: images are often several MBs in size and often have a large resolution. While this is great for editing, printing, ..., such large sizes are not all that useful for inclusion in a webpage. They can make your side load slower and use more disk space without a significant increase in quality. You should therefore consider resizing images before uploading them or installing a plugin that reduces their size on upload. However, do watch out for plugins that keep the original image around as this will not reduce but increase your disk usage. For a tutorial on how to resize images, you can take a look at https://wordpress.com/support/media/image-optimization/. This tutorial is geared towards WordPress, but is also applicable in general. If you are using MediaWiki, we have written a plugin that reduces the size of various type of files. You can find more details on [[Setting up MediaWiki#Extensions|Setting up MediaWiki - Extensions]]. * Backups: ULYSSIS makes daily backups of all account data, including databases, and keeps them for at least a month. It is therefore not necessary to make automated backups of your own, for example with plugins like [https://nl.wordpress.org/plugins/updraftplus/ Updraft] in the case of WordPress. Although it is a good practice to make backups whenever you make changes to your site (for example, before performing updates), it is not necessary to keep them after you have verified that your site still works. [[Category:Files]] [[Category:Account|Help, my account uses to much disk space]] f919fb1e104099be4da58ce475798830128877f5 1231 1230 2021-03-08T00:14:56Z Vincenttc 21 wikitext text/x-wiki This page discusses what happens when you use more disk space than has been allotted to your account (your quota) and how to reduce your disk usage. This page is also useful if you want to reduce your disk usage even if you're not using more than your quota. You can check your current disk usage as well as your quota on https://ucc.ulyssis.org/quota . == What happens when I go over my quota? == If you are using more disk space than the allowed quota for your account type for more than seven consecutive days (the so called grace period), you will no longer be able to write any additional files or extend existing files. You will probably no longer be able to edit websites on your account or it might even stop working outright. If you haven't configured a forwarder for your <code>''username''@ulyssis.org</code> email address, you will lose emails sent to this address. The grace period of seven days is intended for you to have time to reduce your disk space. You will receive an email every day reminding you that you are using too much disk space. In order to prevent impact on other users in cases where disk usage within an account suddenly and substantially surges, an additional quota slightly higher than your normal quota is imposed, independent of any grace period. == Identifying which files & folders use the most disk space == It is not always easy to immediately identify what is taking up space on your account. Sadly, there are no dependable cross-platform tools to help with this. Instead, we will be using the command line tool ''ncdu'', which runs directly on one of our shell servers. You do not need to be proficient with command line interfaces in order to use this tool, the step-by-step manual below will guide you through the process. However, should you get stuck, do not hesitate to contact us at <code>ulyssis@ulyssis.org</code>. * Connect through SSH to one of the shell servers: https://docs.ulyssis.org/Accessing_shell_servers_over_SSH * Type in <code>ncdu</code> and press enter. You will then see that <code>ncdu</code> is scanning your account. * Once <code>ncdu</code> has finished scanning, it will display which files or folders located directly in your home directory are using the most disk space. When the filename stars with <code>/</code> it is a folder. The results are ordered by size, so it makes most sense to start with the top items. * You can select different files/folders using the '''up and down arrow keys''', navigate the directory structure using either the '''enter and backspace''' keys or the '''left and right''' arrows to move in and out of folders, quit ncdu by pressing '''q''' and delete a file or folder with '''d'''. Be careful to not delete files you still need as you will need to contact us in order to restore them from a backup. * You can check your progress on https://ucc.ulyssis.org/quota. The percentage and values displayed are always current and accurate, there is no delay.[[File:Disk usage ncdu.png|thumb|760x760px]] === Common sources of unnecessary disk usage === * Deleted emails (or emails in general): if you have deleted a substantial amount of emails (or some emails with large attachments) and they still exist in the ''Trash'' folder of your ''@ulyssis.org'' email account, they might take op a large amount of disk space. In order to actually delete them you will gave to empty this ''Trash'' folder. You can do this on https://webmail.ulyssis.org or by deleting the folder ''Maildir/.Trash'' using ncdu (see previous section). * Old websites: if you have older websites on your account that you are no longer using, it might be worth removing them in their entirety. If the deleted website uses a database (this will always be the case if your using WordPress, MediaWiki or another popular CMS), then you can delete that as well through our control panel: https://ucc.ulyssis.org. If this website had an associated (sub)domain, please send us an email to have it removed. * Unused images: in the case of many CMS's (WordPress, Drupal, ...), removing an image from a post will not delete it. For example, in the case of WordPress it will still be available through the [https://wordpress.com/support/media/deleting-files/ Media Library]. In order to reclaim the disk space used by the image, you will have to delete it there as well. * Large images: images are often several MBs in size and often have a large resolution. While this is great for editing, printing, ..., such large sizes are not all that useful for inclusion in a webpage. They can make your side load slower and use more disk space without a significant increase in quality. You should therefore consider resizing images before uploading them or installing a plugin that reduces their size on upload. However, do watch out for plugins that keep the original image around as this will not reduce but increase your disk usage. For a tutorial on how to resize images, you can take a look at https://wordpress.com/support/media/image-optimization/. This tutorial is geared towards WordPress, but is also applicable in general. If you are using MediaWiki, we have written a plugin that reduces the size of various type of files. You can find more details on [[Setting up MediaWiki#Extensions|Setting up MediaWiki - Extensions]]. * Backups: ULYSSIS makes daily backups of all account data, including databases, and keeps them for at least a month. It is therefore not necessary to make automated backups of your own, for example with plugins like [https://nl.wordpress.org/plugins/updraftplus/ Updraft] in the case of WordPress. Although it is a good practice to make backups whenever you make changes to your site (for example, before performing updates), it is not necessary to keep them after you have verified that your site still works. [[Category:Files]] __FORCETOC__ c98c177383abdcf7958798b965ca7399f6618bb9 6 155 1222 2021-03-07T23:44:06Z Vincenttc 21 wikitext text/x-wiki Voorbeeld van ncdu met wat uitleg 2fdcb3871ec2546520ed2b36f911850364cbeddf 1225 1222 2021-03-07T23:45:49Z Vincenttc 21 Vincenttc uploaded a new version of [[File:Disk usage ncdu.png]] wikitext text/x-wiki Voorbeeld van ncdu met wat uitleg 2fdcb3871ec2546520ed2b36f911850364cbeddf 0 3 1228 1158 2021-03-08T00:09:06Z Vincenttc 21 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] * [[Secure file permissions]] * [[Reducing disk usage]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2020]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Sending email from websites]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL/TLS|Getting SSL/TLS (HTTPS security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Claiming a port]] * [[ULYSSIS security measures]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] * [[Spam]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up WordPress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] * [[Using PHPPgAdmin]] * [[Using Adminer]] * [[Making Backups]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 7c01a785e5d20c6e61beb701055ab27552965af6 1232 1228 2021-03-08T00:17:37Z Vincenttc 21 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Help, my account uses too much disk space]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] * [[Secure file permissions]] * [[Reducing disk usage]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2020]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Sending email from websites]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL/TLS|Getting SSL/TLS (HTTPS security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Claiming a port]] * [[ULYSSIS security measures]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] * [[Spam]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up WordPress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] * [[Using PHPPgAdmin]] * [[Using Adminer]] * [[Making Backups]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ fc4e7e15121dcb4098665c1f8582239056342894 1234 1232 2021-03-08T00:18:50Z Vincenttc 21 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Reducing disk usage|Help, my account uses too much disk space]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] * [[Secure file permissions]] * [[Reducing disk usage]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2020]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Sending email from websites]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL/TLS|Getting SSL/TLS (HTTPS security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Claiming a port]] * [[ULYSSIS security measures]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] * [[Spam]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up WordPress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] * [[Using PHPPgAdmin]] * [[Using Adminer]] * [[Making Backups]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] * [[ULYSSIS public FTP]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ b1fdcda1109b95bf741ddf963884521a04fc035d 0 154 1235 1231 2021-03-08T00:20:05Z Vincenttc 21 wikitext text/x-wiki This page discusses what happens when you use more disk space than has been allotted to your account (your quota) and how to reduce your disk usage. This page is also useful if you want to reduce your disk usage even if you're not using more than your quota. You can check your current disk usage as well as your quota on https://ucc.ulyssis.org/quota . == What happens when I go over my quota? == If you are using more disk space than the allowed quota for your account type for more than seven consecutive days (the so called grace period), you will no longer be able to write any additional files or extend existing files. You will probably no longer be able to edit websites on your account or it might even stop working outright. If you haven't configured a forwarder for your <code>''username''@ulyssis.org</code> email address, you will lose emails sent to this address. The grace period of seven days is intended for you to have time to reduce your disk space. You will receive an email every day reminding you that you are using too much disk space. In order to prevent impact on other users in cases where disk usage within an account suddenly and substantially surges, an additional quota slightly higher than your normal quota is imposed, independent of any grace period. == Identifying which files & folders use the most disk space == It is not always easy to immediately identify what is taking up space on your account. Sadly, there are no dependable cross-platform tools to help with this. Instead, we will be using the command line tool ''ncdu'', which runs directly on one of our shell servers. You do not need to be proficient with command line interfaces in order to use this tool, the step-by-step manual below will guide you through the process. However, should you get stuck, do not hesitate to contact us at <code>ulyssis@ulyssis.org</code>. * Connect through SSH to one of the shell servers: https://docs.ulyssis.org/Accessing_shell_servers_over_SSH * Type in <code>ncdu</code> and press enter. You will then see that <code>ncdu</code> is scanning your account. * Once <code>ncdu</code> has finished scanning, it will display which files or folders located directly in your home directory are using the most disk space. When the filename stars with <code>/</code> it is a folder. The results are ordered by size, so it makes most sense to start with the top items. * You can select different files/folders using the '''up and down arrow keys''', navigate the directory structure using either the '''enter and backspace''' keys or the '''left and right''' arrows to move in and out of folders, quit ncdu by pressing '''q''' and delete a file or folder with '''d'''. Be careful to not delete files you still need as you will need to contact us in order to restore them from a backup. * You can check your progress on https://ucc.ulyssis.org/quota. The percentage and values displayed are always current and accurate, there is no delay.[[File:Disk usage ncdu.png|thumb|760x760px]] === Common sources of unnecessary disk usage === * Deleted emails (or emails in general): if you have deleted a substantial amount of emails (or some emails with large attachments) and they still exist in the ''Trash'' folder of your ''@ulyssis.org'' email account, they might take op a large amount of disk space. In order to actually delete them you will gave to empty this ''Trash'' folder. You can do this on https://webmail.ulyssis.org or by deleting the folder ''Maildir/.Trash'' using ncdu (see previous section). * Old websites: if you have older websites on your account that you are no longer using, it might be worth removing them in their entirety. If the deleted website uses a database (this will always be the case if your using WordPress, MediaWiki or another popular CMS), then you can delete that as well through our control panel: https://ucc.ulyssis.org. If this website had an associated (sub)domain, please send us an email to have it removed. * Unused images: in the case of many CMS's (WordPress, Drupal, ...), removing an image from a post will not delete it. For example, in the case of WordPress it will still be available through the [https://wordpress.com/support/media/deleting-files/ Media Library]. In order to reclaim the disk space used by the image, you will have to delete it there as well. * Large images: images are often several MBs in size and often have a large resolution. While this is great for editing, printing, ..., such large sizes are not all that useful for inclusion in a webpage. They can make your side load slower and use more disk space without a significant increase in quality. You should therefore consider resizing images before uploading them or installing a plugin that reduces their size on upload. However, do watch out for plugins that keep the original image around as this will not reduce but increase your disk usage. For a tutorial on how to resize images, you can take a look at https://wordpress.com/support/media/image-optimization/. This tutorial is geared towards WordPress, but is also applicable in general. If you are using MediaWiki, we have written a plugin that reduces the size of various type of files. You can find more details on [[Setting up MediaWiki#Extensions|Setting up MediaWiki - Extensions]]. * Backups: ULYSSIS makes daily backups of all account data, including databases, and keeps them for at least a month. It is therefore not necessary to make automated backups of your own, for example with plugins like [https://nl.wordpress.org/plugins/updraftplus/ Updraft] in the case of WordPress. Although it is a good practice to make backups whenever you make changes to your site (for example, before performing updates), it is not necessary to keep them after you have verified that your site still works. [[Category:Files]] __FORCETOC__ [[Category:Account]] a52fdc950a758bd46675e8644922d17c89f7cca9 1236 1235 2021-03-08T01:40:16Z Bert 8 wikitext text/x-wiki This page discusses what happens when you use more disk space than has been allotted to your account (your quota) and how to reduce your disk usage. You may have been pointed here through an automatic email notification you are running over your quote, or through our support. This page is also useful if you want to reduce your disk usage even if you're not using more than your quota. You can check your current disk usage as well as your quota on https://ucc.ulyssis.org/quota . == What happens when I go over my quota? == If you are using more disk space than the allowed quota for your account type for more than seven consecutive days (the so called grace period), you will no longer be able to write any additional files or extend existing files. You will probably no longer be able to edit websites on your account or it might even stop working outright. If you haven't configured a forwarder for your <code>''username''@ulyssis.org</code> email address, you will lose emails sent to this address. The grace period of seven days is intended for you to have time to reduce your disk space. You will receive an email every day reminding you that you are using too much disk space. In order to prevent impact on other users in cases where disk usage within an account suddenly and substantially surges, an additional quota slightly higher than your normal quota is imposed, independent of any grace period. == Identifying which files & folders use the most disk space == It is not always easy to immediately identify what is taking up space on your account. Sadly, there are no dependable cross-platform tools to help with this. Instead, we will be using the command line tool ''ncdu'', which runs directly on one of our shell servers. You do not need to be proficient with command line interfaces in order to use this tool, the step-by-step manual below will guide you through the process. However, should you get stuck, do not hesitate to contact us at <code>ulyssis@ulyssis.org</code>. * Connect through SSH to one of the shell servers: https://docs.ulyssis.org/Accessing_shell_servers_over_SSH * Type in <code>ncdu</code> and press enter. You will then see that <code>ncdu</code> is scanning your account. * Once <code>ncdu</code> has finished scanning, it will display which files or folders located directly in your home directory are using the most disk space. When the filename stars with <code>/</code> it is a folder. The results are ordered by size, so it makes most sense to start with the top items. * You can select different files/folders using the '''up and down arrow keys''', navigate the directory structure using either the '''enter and backspace''' keys or the '''left and right''' arrows to move in and out of folders, quit ncdu by pressing '''q''' and delete a file or folder with '''d'''. Be careful to not delete files you still need as you will need to contact us in order to restore them from a backup. * You can check your progress on https://ucc.ulyssis.org/quota. The percentage and values displayed are always current and accurate, there is no delay.[[File:Disk usage ncdu.png|thumb|760x760px]] === Common sources of unnecessary disk usage === * Deleted emails (or emails in general): if you have deleted a substantial amount of emails (or some emails with large attachments) and they still exist in the ''Trash'' folder of your ''@ulyssis.org'' email account, they might take op a large amount of disk space. In order to actually delete them you will gave to empty this ''Trash'' folder. You can do this on https://webmail.ulyssis.org or by deleting the folder ''Maildir/.Trash'' using ncdu (see previous section). * Old websites: if you have older websites on your account that you are no longer using, it might be worth removing them in their entirety. If the deleted website uses a database (this will always be the case if your using WordPress, MediaWiki or another popular CMS), then you can delete that as well through our control panel: https://ucc.ulyssis.org. If this website had an associated (sub)domain, please send us an email to have it removed. * Unused images: in the case of many CMS's (WordPress, Drupal, ...), removing an image from a post will not delete it. For example, in the case of WordPress it will still be available through the [https://wordpress.com/support/media/deleting-files/ Media Library]. In order to reclaim the disk space used by the image, you will have to delete it there as well. * Large images: images are often several MBs in size and often have a large resolution. While this is great for editing, printing, ..., such large sizes are not all that useful for inclusion in a webpage. They can make your side load slower and use more disk space without a significant increase in quality. You should therefore consider resizing images before uploading them or installing a plugin that reduces their size on upload. However, do watch out for plugins that keep the original image around as this will not reduce but increase your disk usage. For a tutorial on how to resize images, you can take a look at https://wordpress.com/support/media/image-optimization/. This tutorial is geared towards WordPress, but is also applicable in general. If you are using MediaWiki, we have written a plugin that reduces the size of various type of files. You can find more details on [[Setting up MediaWiki#Extensions|Setting up MediaWiki - Extensions]]. * Backups: ULYSSIS makes daily backups of all account data, including databases, and keeps them for at least a month. It is therefore not necessary to make automated backups of your own, for example with plugins like [https://nl.wordpress.org/plugins/updraftplus/ Updraft] in the case of WordPress. Although it is a good practice to make backups whenever you make changes to your site (for example, before performing updates), it is not necessary to keep them after you have verified that your site still works. [[Category:Files]] __FORCETOC__ [[Category:Account]] 3a46d74a643aa1bd7efeddbee811ccf4ee42fc9b 1237 1236 2021-03-08T01:44:33Z Bert 8 wikitext text/x-wiki This page discusses what happens when you use more disk space than has been allotted to your account (your quota) and how to reduce your disk usage. You may have been pointed here through an automatic email notification you are running over your quote, or through our support. This page is also useful if you want to reduce your disk usage even if you're not using more than your quota. You can check your current disk usage as well as your quota on https://ucc.ulyssis.org/quota. This page first discusses what happens when you use more disk space than is available to your account type (so you therefore go over your quota). This is followed by a detailed manual on how to use the command line tool ''ncdu'' to look for the files and folders that may be causing trouble within your account. Finally, there's a list of examples of common causes for large disk space usage. == What happens when I go over my quota? == If you are using more disk space than the allowed quota for your account type for more than seven consecutive days (the so called grace period), you will no longer be able to write any additional files or extend existing files. You will probably no longer be able to edit websites on your account or it might even stop working outright. If you haven't configured a forwarder for your <code>''username''@ulyssis.org</code> email address, you will lose emails sent to this address. The grace period of seven days is intended for you to have time to reduce your disk space. You will receive an email every day reminding you that you are using too much disk space. In order to prevent impact on other users in cases where disk usage within an account suddenly and substantially surges, an additional quota slightly higher than your normal quota is imposed, independent of any grace period. == Identifying which files & folders use the most disk space == It is not always easy to immediately identify what is taking up space on your account. Sadly, there are no dependable cross-platform tools to help with this. Instead, we will be using the command line tool ''ncdu'', which runs directly on one of our shell servers. You do not need to be proficient with command line interfaces in order to use this tool, the step-by-step manual below will guide you through the process. However, should you get stuck, do not hesitate to contact us at <code>ulyssis@ulyssis.org</code>. * Connect through SSH to one of the shell servers: https://docs.ulyssis.org/Accessing_shell_servers_over_SSH * Type in <code>ncdu</code> and press enter. You will then see that <code>ncdu</code> is scanning your account. * Once <code>ncdu</code> has finished scanning, it will display which files or folders located directly in your home directory are using the most disk space. When the filename stars with <code>/</code> it is a folder. The results are ordered by size, so it makes most sense to start with the top items. * You can select different files/folders using the '''up and down arrow keys''', navigate the directory structure using either the '''enter and backspace''' keys or the '''left and right''' arrows to move in and out of folders, quit ncdu by pressing '''q''' and delete a file or folder with '''d'''. Be careful to not delete files you still need as you will need to contact us in order to restore them from a backup. * You can check your progress on https://ucc.ulyssis.org/quota. The percentage and values displayed are always current and accurate, there is no delay.[[File:Disk usage ncdu.png|thumb|760x760px]] === Common sources of unnecessary disk usage === * Deleted emails (or emails in general): if you have deleted a substantial amount of emails (or some emails with large attachments) and they still exist in the ''Trash'' folder of your ''@ulyssis.org'' email account, they might take op a large amount of disk space. In order to actually delete them you will gave to empty this ''Trash'' folder. You can do this on https://webmail.ulyssis.org or by deleting the folder ''Maildir/.Trash'' using ncdu (see previous section). * Old websites: if you have older websites on your account that you are no longer using, it might be worth removing them in their entirety. If the deleted website uses a database (this will always be the case if your using WordPress, MediaWiki or another popular CMS), then you can delete that as well through our control panel: https://ucc.ulyssis.org. If this website had an associated (sub)domain, please send us an email to have it removed. * Unused images: in the case of many CMS's (WordPress, Drupal, ...), removing an image from a post will not delete it. For example, in the case of WordPress it will still be available through the [https://wordpress.com/support/media/deleting-files/ Media Library]. In order to reclaim the disk space used by the image, you will have to delete it there as well. * Large images: images are often several MBs in size and often have a large resolution. While this is great for editing, printing, ..., such large sizes are not all that useful for inclusion in a webpage. They can make your side load slower and use more disk space without a significant increase in quality. You should therefore consider resizing images before uploading them or installing a plugin that reduces their size on upload. However, do watch out for plugins that keep the original image around as this will not reduce but increase your disk usage. For a tutorial on how to resize images, you can take a look at https://wordpress.com/support/media/image-optimization/. This tutorial is geared towards WordPress, but is also applicable in general. If you are using MediaWiki, we have written a plugin that reduces the size of various type of files. You can find more details on [[Setting up MediaWiki#Extensions|Setting up MediaWiki - Extensions]]. * Backups: ULYSSIS makes daily backups of all account data, including databases, and keeps them for at least a month. It is therefore not necessary to make automated backups of your own, for example with plugins like [https://nl.wordpress.org/plugins/updraftplus/ Updraft] in the case of WordPress. Although it is a good practice to make backups whenever you make changes to your site (for example, before performing updates), it is not necessary to keep them after you have verified that your site still works. [[Category:Files]] __FORCETOC__ [[Category:Account]] 5fe67b62dc172564d6fcddd7e44e3826b3aa4b9f 1238 1237 2021-03-08T01:48:47Z Bert 8 wikitext text/x-wiki __TOC__ This page discusses what happens when you use more disk space than has been allotted to your account (your quota) and how to reduce your disk usage. You may have been pointed here through an automatic email notification you are running over your quote, or through our support. This page is also useful if you want to reduce your disk usage even if you're not using more than your quota. You can check your current disk usage as well as your quota on https://ucc.ulyssis.org/quota. This page first discusses what happens when you use more disk space than is available to your account type (so you therefore go over your quota). This is followed by a detailed manual on how to use the command line tool ''ncdu'' to look for the files and folders that may be causing trouble within your account. Finally, there's a list of examples of common causes for large disk space usage. == What happens when I go over my quota? == If you are using more disk space than the allowed quota for your account type for more than seven consecutive days (the so called grace period), you will no longer be able to write any additional files or extend existing files. You will probably no longer be able to edit websites on your account or it might even stop working outright. If you haven't configured a forwarder for your <code>''username''@ulyssis.org</code> email address, you will lose emails sent to this address. The grace period of seven days is intended for you to have time to reduce your disk space. You will receive an email every day reminding you that you are using too much disk space. In order to prevent impact on other users in cases where disk usage within an account suddenly and substantially surges, an additional quota slightly higher than your normal quota is imposed, independent of any grace period. == Identifying which files & folders use the most disk space == It is not always easy to immediately identify what is taking up space on your account. Sadly, there are no dependable cross-platform tools to help with this. Instead, we will be using the command line tool ''ncdu'', which runs directly on one of our shell servers. You do not need to be proficient with command line interfaces in order to use this tool, the step-by-step manual below will guide you through the process. However, should you get stuck, do not hesitate to contact us at <code>ulyssis@ulyssis.org</code>. * Connect through SSH to one of the shell servers: https://docs.ulyssis.org/Accessing_shell_servers_over_SSH * Type in <code>ncdu</code> and press enter. You will then see that <code>ncdu</code> is scanning your account. * Once <code>ncdu</code> has finished scanning, it will display which files or folders located directly in your home directory are using the most disk space. When the filename stars with <code>/</code> it is a folder. The results are ordered by size, so it makes most sense to start with the top items. * You can select different files/folders using the '''up and down arrow keys''', navigate the directory structure using either the '''enter and backspace''' keys or the '''left and right''' arrows to move in and out of folders, quit ncdu by pressing '''q''' and delete a file or folder with '''d'''. Be careful to not delete files you still need as you will need to contact us in order to restore them from a backup. * You can check your progress on https://ucc.ulyssis.org/quota. The percentage and values displayed are always current and accurate, there is no delay.[[File:Disk usage ncdu.png|thumb|760x760px]] === Common sources of unnecessary disk usage === * Deleted emails (or emails in general): if you have deleted a substantial amount of emails (or some emails with large attachments) and they still exist in the ''Trash'' folder of your ''@ulyssis.org'' email account, they might take op a large amount of disk space. In order to actually delete them you will gave to empty this ''Trash'' folder. You can do this on https://webmail.ulyssis.org or by deleting the folder ''Maildir/.Trash'' using ncdu (see previous section). * Old websites: if you have older websites on your account that you are no longer using, it might be worth removing them in their entirety. If the deleted website uses a database (this will always be the case if your using WordPress, MediaWiki or another popular CMS), then you can delete that as well through our control panel: https://ucc.ulyssis.org. If this website had an associated (sub)domain, please send us an email to have it removed. * Unused images: in the case of many CMS's (WordPress, Drupal, ...), removing an image from a post will not delete it. For example, in the case of WordPress it will still be available through the [https://wordpress.com/support/media/deleting-files/ Media Library]. In order to reclaim the disk space used by the image, you will have to delete it there as well. * Large images: images are often several MBs in size and often have a large resolution. While this is great for editing, printing, ..., such large sizes are not all that useful for inclusion in a webpage. They can make your side load slower and use more disk space without a significant increase in quality. You should therefore consider resizing images before uploading them or installing a plugin that reduces their size on upload. However, do watch out for plugins that keep the original image around as this will not reduce but increase your disk usage. For a tutorial on how to resize images, you can take a look at https://wordpress.com/support/media/image-optimization/. This tutorial is geared towards WordPress, but is also applicable in general. If you are using MediaWiki, we have written a plugin that reduces the size of various type of files. You can find more details on [[Setting up MediaWiki#Extensions|Setting up MediaWiki - Extensions]]. * Backups: ULYSSIS makes daily backups of all account data, including databases, and keeps them for at least a month. It is therefore not necessary to make automated backups of your own, for example with plugins like [https://nl.wordpress.org/plugins/updraftplus/ Updraft] in the case of WordPress. Although it is a good practice to make backups whenever you make changes to your site (for example, before performing updates), it is not necessary to keep them after you have verified that your site still works. [[Category:Files]] [[Category:Account]] e66d182fc6fd2b23734a946e2038753d65034b47 1239 1238 2021-03-08T02:24:26Z Bert 8 wikitext text/x-wiki __TOC__ This page discusses what happens when you use more disk space than has been allotted to your account (your quota) and how to reduce your disk usage. You may have been pointed here through an automatic email notification you are running over your quote, or through our support. This page is also useful if you want to reduce your disk usage even if you're not using more than your quota. You can check your current disk usage as well as your quota on https://ucc.ulyssis.org/quota. This page first discusses what happens when you use more disk space than is available to your account type (so you therefore go over your quota). This is followed by a detailed manual on how to use the command line tool ''ncdu'' to look for the files and folders that may be causing trouble within your account. Finally, there's a list of examples of common causes for large disk space usage. == What happens when I go over my quota? == If you are using more disk space than the allowed quota for your account type for more than seven consecutive days (the so called grace period), you will no longer be able to write any additional files or extend existing files. You will probably no longer be able to edit websites on your account or it might even stop working outright. If you haven't configured a forwarder for your <code>''username''@ulyssis.org</code> email address, you will lose emails sent to this address. The grace period of seven days is intended for you to have time to reduce your disk space. You will receive an email every day reminding you that you are using too much disk space. In order to prevent impact on other users in cases where disk usage within an account suddenly and substantially surges, an additional quota slightly higher than your normal quota is imposed, independent of any grace period. == Identifying which files & folders use the most disk space == It is not always easy to immediately identify what is taking up space on your account. Sadly, there are no dependable cross-platform tools to help with this. Instead, we will be using the command line tool ''ncdu'', which runs directly on one of our shell servers. You do not need to be proficient with command line interfaces in order to use this tool, the step-by-step manual below will guide you through the process. However, should you get stuck, do not hesitate to contact us at <code>ulyssis@ulyssis.org</code>. * Connect through SSH to one of the shell servers: https://docs.ulyssis.org/Accessing_shell_servers_over_SSH * Type in <code>ncdu</code> and press enter. You will then see that <code>ncdu</code> is scanning your account. * Once <code>ncdu</code> has finished scanning, it will display which files or folders located directly in your home directory are using the most disk space. When the filename stars with <code>/</code> it is a folder. The results are ordered by size, so it makes most sense to start with the top items. * You can select different files/folders using the '''up and down arrow keys''', navigate the directory structure using either the '''enter and backspace''' keys or the '''left and right''' arrows to move in and out of folders, quit ncdu by pressing '''q''' and delete a file or folder with '''d'''. Be careful to not delete files you still need as you will need to contact us in order to restore them from a backup. * You can check your progress on https://ucc.ulyssis.org/quota. The percentage and values displayed are always current and accurate, there is no delay.[[File:Disk usage ncdu.png|thumb|760x760px]] === Common sources of unnecessary disk usage === * Your ULYSSIS mailbox: Depending on your account settings, your ''@ulyssis.org'' email account may be used as a forwarder or an inbox. When set to ''Inbox'' on https://ucc.ulyssis.org/mail, email will be saved to the ''Maildir'' folder within your account. A substantial amount of email, especially with large attachments, may grow to quite a significant size. You can verify the contents of your mailbox easily by logging in on https://webmail.ulyssis.org using your ULYSSIS account credentials. You can then remove those emails that are no longer useful, and don't forget to empty the trash. To remove the entire mailbox, you can simply remove the Maildir folder from your account (using ncdu, FileZilla, or another tool). To empty the trash manually, you can remove the ''Maildir/.Trash'' folder. If you no longer wish to use you mailbox, don't forget to change the configuration on https://ucc.ulyssis.org/mail to forward your messages, since you may receive relevant information about your account through this address. * Old websites: if you have older websites on your account that you are no longer using, it might be worth removing them in their entirety. If the deleted website uses a database (this will always be the case if your using WordPress, MediaWiki or another popular CMS), then you should also delete those through our control panel: https://ucc.ulyssis.org (either the MySQL or PostgreSQL sections). If this website had an associated (sub)domain, please send us an email to have it removed. Also keep in mind that old websites may pose a security risk, so it's never good to leave them lying about. * Unused images: in the case of many CMSs (WordPress, Drupal, ...), removing an image from a post will not delete it. For example, in the case of WordPress it will still be available through the [https://wordpress.com/support/media/deleting-files/ Media Library]. In order to reclaim the disk space used by the image, you will have to delete it there as well. Similarly, MediaWiki offers a list of ''unused files'' as a special page available in the list of ''Special Pages''. * Large images: images and especially pictures are often several MBs in size and often have a large resolution. While this is great for editing and printing, such large sizes are not all that useful for inclusion in a webpage. They can make your site load slower and use more disk space without a significant increase in quality. You should therefore consider resizing images before uploading them or installing a plugin, module or extension that reduces their size on upload. However, make sure to watch out for plugins that keep the original image around as this will not reduce but increase your disk usage. For a tutorial on how to resize images, you can take a look at https://wordpress.com/support/media/image-optimization/. This tutorial is geared towards WordPress, but is also applicable in general. If you are using MediaWiki, we have written a plugin that reduces the size of various type of files. You can find more details on [[Setting up MediaWiki#Extensions|Setting up MediaWiki - Extensions]]. * Backups: ULYSSIS makes daily backups of all account data, including databases, and keeps them for at least a month. It is therefore not necessary to make automated backups of your own, for example with plugins such as [https://nl.wordpress.org/plugins/updraftplus/ Updraft] for WordPress. Although it is a good practice to make backups whenever you are making large changes to your site, it is not necessary to keep them after you have verified that your site works correctly. * Anything missing on this list? Feel free to contact us on <code>ulyssis@ulyssis.org</code> with your suggestions. [[Category:Files]] [[Category:Account]] 22b45f9ca910a38278b60ce95d41c1c8d34995ac 1240 1239 2021-03-08T07:28:33Z Pcy 37 fix spelling etc wikitext text/x-wiki __TOC__ This page discusses what happens when you use more disk space than has been allotted to your account (your quota) and how to reduce your disk usage. You may have been pointed here through an automatic email notification you are running over your quota, or through our support. This page is also useful if you want to reduce your disk usage even if you're not using more than your quota. You can check your current disk usage as well as your quota on https://ucc.ulyssis.org/quota. This page first discusses what happens when you use more disk space than is available to your account type (so you therefore go over your quota). This is followed by a detailed manual on how to use the command line tool ''ncdu'' to look for the files and folders that may be causing trouble within your account. Finally, there's a list of examples of common causes for large disk space usage. == What happens when I go over my quota? == If you are using more disk space than the allowed quota for your account type for more than seven consecutive days (the so-called grace period), you will no longer be able to write any additional files or extend existing files. You will probably no longer be able to edit websites on your account or it might even stop working outright. If you haven't configured a forwarder for your <code>''username''@ulyssis.org</code> email address, you will lose emails sent to this address. The grace period of seven days is intended for you to have time to reduce your disk space. You will receive an email every day reminding you that you are using too much disk space. In order to prevent impact on other users in cases where disk usage within an account suddenly and substantially surges, an additional quota slightly higher than your normal quota is imposed, independent of any grace period. == Identifying which files & folders use the most disk space == It is not always easy to immediately identify what is taking up space on your account. Sadly, there are no dependable cross-platform tools to help with this. Instead, we will be using the command line tool ''ncdu'', which runs directly on one of our shell servers. You do not need to be proficient with command line interfaces in order to use this tool, the step-by-step manual below will guide you through the process. However, should you get stuck, do not hesitate to contact us at <code>ulyssis@ulyssis.org</code>. * Connect through SSH to one of the shell servers: https://docs.ulyssis.org/Accessing_shell_servers_over_SSH * Type in <code>ncdu</code> and press enter. You will then see that <code>ncdu</code> is scanning your account. * Once <code>ncdu</code> has finished scanning, it will display which files or folders located directly in your home directory are using the most disk space. When the filename stars with <code>/</code> it is a folder. The results are ordered by size, so it makes most sense to start with the top items. * You can select different files/folders using the '''up and down arrow keys''', navigate the directory structure using either the '''enter and backspace''' keys or the '''left and right''' arrows to move in and out of folders, quit ncdu by pressing '''q''' and delete a file or folder with '''d'''. Be careful to not delete files you still need as you will need to contact us in order to restore them from a backup. * You can check your progress on https://ucc.ulyssis.org/quota. The percentage and values displayed are always current and accurate, there is no delay.[[File:Disk usage ncdu.png|thumb|760x760px]] === Common sources of unnecessary disk usage === * Your ULYSSIS mailbox: Depending on your account settings, your ''@ulyssis.org'' email account may be used as a forwarder or an inbox. When set to ''Inbox'' on https://ucc.ulyssis.org/mail, email will be saved to the ''Maildir'' folder within your account. A substantial amount of email, especially with large attachments, may grow to quite a significant size. You can verify the contents of your mailbox easily by logging in on https://webmail.ulyssis.org using your ULYSSIS account credentials. You can then remove those emails that are no longer useful, and don't forget to empty the trash. To remove the entire mailbox, you can simply remove the Maildir folder from your account (using ncdu, FileZilla, or another tool). To empty the trash manually, you can remove the ''Maildir/.Trash'' folder. If you no longer wish to use you mailbox, don't forget to change the configuration on https://ucc.ulyssis.org/mail to forward your messages, since you may receive relevant information about your account through this address. * Old websites: if you have older websites on your account that you are no longer using, it might be worth removing them in their entirety. If the deleted website uses a database (this will always be the case if your using WordPress, MediaWiki or another popular CMS), then you should also delete those through our control panel: https://ucc.ulyssis.org (either the MySQL or PostgreSQL sections). If this website had an associated (sub)domain, please send us an email to have it removed. Also keep in mind that old websites may pose a security risk, so it's never good to leave them lying about. * Unused images: in the case of many CMSes (WordPress, Drupal, ...), removing an image from a post will not delete it. For example, in the case of WordPress it will still be available through the [https://wordpress.com/support/media/deleting-files/ Media Library]. In order to reclaim the disk space used by the image, you will have to delete it there as well. Similarly, MediaWiki offers a list of ''unused files'' as a special page available in the list of ''Special Pages''. * Large images: images and especially pictures are often several MBs in size and often have a large resolution. While this is great for editing and printing, such large sizes are not all that useful for inclusion in a webpage. They can make your site load slower and use more disk space without a significant increase in quality. You should therefore consider resizing images before uploading them or installing a plugin, module or extension that reduces their size on upload. However, make sure to watch out for plugins that keep the original image around as this will not reduce but increase your disk usage. For a tutorial on how to resize images, you can take a look at https://wordpress.com/support/media/image-optimization/. This tutorial is geared towards WordPress, but is also applicable in general. If you are using MediaWiki, we have written a plugin that reduces the size of various types of files. You can find more details on [[Setting up MediaWiki#Extensions|Setting up MediaWiki - Extensions]]. * Backups: ULYSSIS makes daily backups of all account data, including databases, and keeps them for at least a month. It is therefore not necessary to make automated backups of your own, for example with plugins such as [https://nl.wordpress.org/plugins/updraftplus/ Updraft] for WordPress. Although it is a good practice to make backups whenever you are making large changes to your site, it is not necessary to keep them after you have verified that your site works correctly. * Anything missing on this list? Feel free to contact us on <code>ulyssis@ulyssis.org</code> with your suggestions. [[Category:Files]] [[Category:Account]] 644a071b509651c04903342535a182990698006b 1241 1240 2021-03-15T09:33:37Z Bert 8 /* Common sources of unnecessary disk usage */ wikitext text/x-wiki __TOC__ This page discusses what happens when you use more disk space than has been allotted to your account (your quota) and how to reduce your disk usage. You may have been pointed here through an automatic email notification you are running over your quota, or through our support. This page is also useful if you want to reduce your disk usage even if you're not using more than your quota. You can check your current disk usage as well as your quota on https://ucc.ulyssis.org/quota. This page first discusses what happens when you use more disk space than is available to your account type (so you therefore go over your quota). This is followed by a detailed manual on how to use the command line tool ''ncdu'' to look for the files and folders that may be causing trouble within your account. Finally, there's a list of examples of common causes for large disk space usage. == What happens when I go over my quota? == If you are using more disk space than the allowed quota for your account type for more than seven consecutive days (the so-called grace period), you will no longer be able to write any additional files or extend existing files. You will probably no longer be able to edit websites on your account or it might even stop working outright. If you haven't configured a forwarder for your <code>''username''@ulyssis.org</code> email address, you will lose emails sent to this address. The grace period of seven days is intended for you to have time to reduce your disk space. You will receive an email every day reminding you that you are using too much disk space. In order to prevent impact on other users in cases where disk usage within an account suddenly and substantially surges, an additional quota slightly higher than your normal quota is imposed, independent of any grace period. == Identifying which files & folders use the most disk space == It is not always easy to immediately identify what is taking up space on your account. Sadly, there are no dependable cross-platform tools to help with this. Instead, we will be using the command line tool ''ncdu'', which runs directly on one of our shell servers. You do not need to be proficient with command line interfaces in order to use this tool, the step-by-step manual below will guide you through the process. However, should you get stuck, do not hesitate to contact us at <code>ulyssis@ulyssis.org</code>. * Connect through SSH to one of the shell servers: https://docs.ulyssis.org/Accessing_shell_servers_over_SSH * Type in <code>ncdu</code> and press enter. You will then see that <code>ncdu</code> is scanning your account. * Once <code>ncdu</code> has finished scanning, it will display which files or folders located directly in your home directory are using the most disk space. When the filename stars with <code>/</code> it is a folder. The results are ordered by size, so it makes most sense to start with the top items. * You can select different files/folders using the '''up and down arrow keys''', navigate the directory structure using either the '''enter and backspace''' keys or the '''left and right''' arrows to move in and out of folders, quit ncdu by pressing '''q''' and delete a file or folder with '''d'''. Be careful to not delete files you still need as you will need to contact us in order to restore them from a backup. * You can check your progress on https://ucc.ulyssis.org/quota. The percentage and values displayed are always current and accurate, there is no delay.[[File:Disk usage ncdu.png|thumb|760x760px]] === Common sources of unnecessary disk usage === * Your ULYSSIS mailbox: Depending on your account settings, your ''@ulyssis.org'' email account may be used as a forwarder or an inbox. When set to ''Inbox'' on https://ucc.ulyssis.org/mail, email will be saved to the ''Maildir'' folder within your account. A substantial amount of email, especially with large attachments, may grow to quite a significant size. You can verify the contents of your mailbox easily by logging in on https://webmail.ulyssis.org using your ULYSSIS account credentials. You can then remove those emails that are no longer useful, and don't forget to empty the trash. To remove the entire mailbox, you can simply remove the Maildir folder from your account (using ncdu, FileZilla, or another tool). To empty the trash manually, you can remove the ''Maildir/.Trash'' folder. If you no longer wish to use you mailbox, don't forget to change the configuration on https://ucc.ulyssis.org/mail to forward your messages, since you may receive relevant information about your account through this address. * Old websites: if you have older websites on your account that you are no longer using, it might be worth removing them in their entirety. If the deleted website uses a database (this will always be the case if your using WordPress, MediaWiki or another popular CMS), then you should also delete those through our control panel: https://ucc.ulyssis.org (either the MySQL or PostgreSQL sections). If this website had an associated (sub)domain, please send us an email to have it removed. Also keep in mind that old websites may pose a security risk, so it's never good to leave them lying about. * Unused images: in the case of many CMSes (WordPress, Drupal, ...), removing an image from a post will not delete it. For example, in the case of WordPress it will still be available through the Media Library. You can easily find these [https://wordpress.com/support/media/2/#unattached-files unattached files]. In order to reclaim the disk space used by the image, you will have to [https://wordpress.com/support/trash/#permanently-deleting-an-upload delete] it there as well. Similarly, MediaWiki offers a list of ''unused files'' as a special page available in the list of ''Special Pages''. Keep in mind that WordPress or MediaWiki might not always be aware an image or other file is used when it has not been added through its interfaces or through a third party plugin. * Large images: images and especially pictures are often several MBs in size and often have a large resolution. While this is great for editing and printing, such large sizes are not all that useful for inclusion in a webpage. They can make your site load slower and use more disk space without a significant increase in quality. You should therefore consider resizing images before uploading them or installing a plugin, module or extension that reduces their size on upload. However, make sure to watch out for plugins that keep the original image around as this will not reduce but increase your disk usage. For a tutorial on how to resize images, you can take a look at https://wordpress.com/support/media/image-optimization/. This tutorial is geared towards WordPress, but is also applicable in general. If you are using MediaWiki, we have written a plugin that reduces the size of various types of files. You can find more details on [[Setting up MediaWiki#Extensions|Setting up MediaWiki - Extensions]]. * Backups: ULYSSIS makes daily backups of all account data, including databases, and keeps them for at least a month. It is therefore not necessary to make automated backups of your own, for example with plugins such as [https://nl.wordpress.org/plugins/updraftplus/ Updraft] for WordPress. Although it is a good practice to make backups whenever you are making large changes to your site, it is not necessary to keep them after you have verified that your site works correctly. * Anything missing on this list? Feel free to contact us on <code>ulyssis@ulyssis.org</code> with your suggestions. [[Category:Files]] [[Category:Account]] 9dd8e90529cd53775e3fca7f848a8e0cfb3a3faf 0 73 1242 765 2021-03-17T00:33:27Z Yoa 30 wikitext text/x-wiki We often get the question at our LaTeX workshop how to properly install the kulemt package. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading "kulemt-tds.zip" from https://eng.kuleuven.be/docs/kulemt. == One-time use == Most people will only use this package once, for their master thesis. In this case, you can just put the necessary files in the same folder as your LaTeX project. The easiest way to accomplish this, is to unzip the downloaded file and in the unzipped folder, navigate to the directory "tex/latex/kulemt". Here, copy the following files to the same directory as your LaTeX project: kulemt.cfg, kulemt.cls, kulemtx.sty, logokul.eps and logokuleng.eps. == User-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package in a central location where LaTeX can find it autonomously. When using TeXLive, as we recommend, this involves a bit more work. First, you should find where to install the packages for your user. This is called the TEXMFHOME. The default location of this folder is: * For Windows: the folder "texmf" in your %USERPROFILE% (C:\Users\YourUsername for Windows Vista and up). * For Linux: "~/texmf" * For OS X/macOS: "~/Library/texmf" It is possible that this folder needs to be created first. From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location (note: the directory itself, not only its contents). If this does not work, or if you want to check the directory first, please refer to the section [[#Finding the TEXMFHOME]] at the bottom of this document. For a more technical overview, you can follow the general guidelines provided by the department: ftp://ftp.esat.kuleuven.be/latex/kulemt/README.html. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English}, % in case of a Dutch master udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> == Finding the TEXMFHOME == In case the default location for the TEXMFHOME as stated above does not work, you can find the correct directory through command-line. In Linux and macOS, look for an app called "Terminal". In Windows, search for "cmd" using the start menu. The program has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf If you have found this folder, copy the entire "tex" directory from the extracted kulemt-tds.zip to this location, as stated before. Create the folder if needed. == Troubleshooting == The kulemt package requires the memoir package. Make sure you have this package. We recommend installing the texlive-full package on Ubuntu. When you use the installer from [ftp://ftp.ulyssis.org/LaTeX-Workshop/installers/ our FTP server] for Windows or OS X/macOS, you will automatically have the entire LaTeX suite. [[Category:Tutorials]] 9b7b01904bbfb7ae7bc8b386f6accca4ca52580e 0 47 1243 1179 2021-03-25T15:50:57Z Casper 39 wikitext text/x-wiki This page will go through a basic setup of MediaWiki. It is based on [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wikipage], and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. This tutorial we'll use a ULYSSIS-account with username "me". == Putting setup-files in place == First we'll have to download the setup file which you can find over at [http://www.mediawiki.org/wiki/Download the official MediaWiki website]. It's an archived file, so you need to extract it first and put the files in a subdirectory of your "document root". The default is just a www directory in your home folder. Putting your files in document_root/wiki/ will make your wiki be located at usersname.ulyssis.be/wiki/. If you prefer, you can do this all graphically using the manual [[Accessing_your_files]]. If you prefer the command line; <pre> homeuser@home:~$ ssh me@ssh1.ulyssis.org enter super secret password: me@zap:~$ wget https://releases.wikimedia.org/mediawiki/1.35/mediawiki-1.35.1.zip me@zap:~$ unzip mediawiki-1.35.1.zip me@zap:~$ mv mediawiki-1.35.1 www/wiki me@zap:~$ rm -r mediawiki-1.35.1.zip </pre> ==Setting up database== Like the [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wiki] tells us, we have three different options to choose from; PostgreSQL, MySQL and SQLite. It's easy to set a PostgreSQL or MySQL database; just go to the UCC. For this tutorial we will continue with a MySQL database (PostgreSQL installation steps are quite similar). Let us visit https://ucc.ulyssis.org/mysql; if this is your first time using MySQL you'll need to create a new account by putting in a super secret password. The wizard will create your MySQL account with the same name as your user-account. We'll also create a new database with an appropriate name by clicking on 'Add database'. In this tutorial we will choose; "wiki", notice that it will be prepended with our username, so we'll end up with a new database named "me_wiki". ==Setup your wiki== If all went well, you can access your website at http://username.ulyssis.be/the_folder_you_used and start the setup wizard. In our example, will surf to http://me.ulyssis.be/wiki. The wizard will guide you through some configuration options. Most of them our pretty straight-forward. When in doubt, you can always click the question mark wich will show you some sensible and recommended default... We'll just discuss the page were the wizard asks you for the database. In our example; <pre> Database host: mysql.ulyssis.org Database name: me_wiki // The name of our database; i.e. the name we chose, prepended by our username. Database table prefix: // We can leave this blank. Database user: me // This is the name of our MySQL-user, which was named after our ULYSSIS-username. Database password: supersecretpassword // Please note that this is not your ULYSSIS-password, but the password you used in UCC when creating the MySQL user! </pre> ==Creating the wiki== After the setup wizard is complete, you can begin the installation procedure. If all went well, you'll be greeted by a page which congratulates you with your new installation. ==Finishing up installation== The setup will offer you a configuration file (containing some settings you specified) that you need to download to your server (more specifically in directory where your MediaWiki-files reside in). You again can do this graphically, or if you prefer a terminal; <pre> homeuser@home:~$ scp path_to_file/LocalSettings.php me@ssh1.ulyssis.org:~/www/wiki enter super secret password: </pre> After this is done, you can finally start using your wiki. Please refer to [http://www.mediawiki.org/wiki/MediaWiki the original MediaWiki documentation] for a more detailed or advanced information. == Extending MediaWiki == By default, every MediaWiki installation looks and works identical. While that is convenient for users, it can be less than ideal if you need specific functionality or wish to adapt your wiki to your style. === Extensions === Extensions add functionality to a wiki, such as more fine-grained authentication, extra layout elements for articles or text filters. An overview of what kinds of extensions are possible can be found on [https://www.mediawiki.org/wiki/Manual:Extensions the official manual]. Some noteworthy extensions can be used to prevent spam or unauthorised access. You can find more information on [[Preventing spam on MediaWiki]] and [[Securing MediaWiki using Centrale KU Leuven Login]]. We've also found that users sometimes have problems with high amounts of disk space usage. To help those users out, we've developed a MediaWiki extension that can automatically reduce file size of new uploads. Specifically it's possible to compress PDFs, convert inefficient image formats such as BMP and TIFF to PNG, loslessly compress PNG, lossy compress JPG, resize images and strip EXIF data. You can find more details on https://github.com/ULYSSIS-KUL/CompressUploads === Skins === Skins are similar to themes, templates or styles within other software. By default MediaWiki uses the well known Vector skin. But other skins are available. Sadly, MediaWiki doesn't maintain a complete list of all available skins and whether they work with recent releases, so it may take a bit of perseverance. General information on Skins is available on the [https://www.mediawiki.org/wiki/Manual:Skins Official Manual]. Besides that there's the [https://www.mediawiki.org/wiki/Manual:Gallery_of_user_styles the user style gallery] and [https://www.mediawiki.org/wiki/Category:All_skins the list of skins]. [[Category:CMSs]] e5c5513d7c1d0e31281336c554d51499fc524d5a 0 5 1244 1202 2021-03-27T16:24:51Z Bert 8 /* Windows */ wikitext text/x-wiki Next to running commands, you can also use the shell servers to access your files. There are several methods to do this, some graphical, some not. The former definitely are the easiest option to go for. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Connecting== {{notice|Keep in mind|Our automatic security systems may temporarily prevent you from connecting over SSH/SFTP if you try to connect several times with the wrong username and/or password. This will result in the connection being refused. You can switch between sftp://ssh1.ulyssis.org and sftp://ssh2.ulyssis.org when this happens or wait 10 minutes. More information on our security measures is available on [[ULYSSIS security measures]]}} ===Linux=== Linux normally gives you the option to connect to a server graphically. On Ubuntu, in "Files", choose "Connect to server." using the following options: <ul> <li>Server Address: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> </ul> If you are connecting for the first time, you will need to accept the identity of the server. Enter your username and password and connect, if necessary, unlock your keyring by entering your computer's password. This will open up a file browser connected to the remote server. Here, you can create new files, delete files, upload files (by copying or dragging them in the file browser), download files (by copying or dragging them from the file browser), change file rights etc. If your distribution does not contain an option to connect to a server, you can use [https://filezilla-project.org/ FileZilla], which is completely free. See the instructions under [[Accessing_your_files#Windows|Windows]]. [[File:UbuntuConnectToServer.png]] ===Windows=== Windows doesn't support native remote file browsers, so you will have to download a program first. A good option is [https://filezilla-project.org/download.php?show_all=1 FileZilla], which is completely free. Download it, install it and run it. ==== Using the quickconnect bar ==== <ul> <li>Host: sftp://ssh1.ulyssis.org or sftp://ssh2.ulyssis.org</li> <li>Username: your username</li> <li>Password: your password</li> <li>Port: 22 (you can leave this blank)</li> <li>Connect to ULYSSIS by clicking on Quickconnect</li> </ul> [[File:FileZillaQuickconnect.png]] ==== Using the site manager ==== <ul> <li>Go to Files, Site Manager...</li> <li>Add a new site</li> <li>Host: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: 22 (you can leave this blank)</li> <li>Protocol (dropdown menu): SFTP - SSH File Transfer Protocol</li> <li>Logon Type (dropdown menu): Normal <li>User: your username</li> <li>Password: your password</li> </ul> [[File:FileZillaSiteManager.png]] ===Mac=== ''[https://filezilla-project.org/ FileZilla], which was mentioned above, is also available for Mac. To use it, follow [[#Windows|the instructions for Windows]]. You can also opt for [http://cyberduck.io/ Cyberduck], though. In that case, follow the instructions below.'' Download the free and open source program [http://cyberduck.io/ Cyberduck] Follow the installations instructions and afterwards open Cyberduck in your Applications folder. Click on 'Open Connection' in the left top corner. <ul> <li>Dropdown menu: SFTP (SSH File Transfer Protocol)</li> <li>Server: ssh1.ulyssis.org or ssh2.ulyssis.org</li> <li>Port: you can leave the default value</li> <li>Username: your username</li> <li>Password: your password</li> </ul> [[File:maccyberduck3.png]] Click on 'Connect' and you're done. By dragging and dropping you can manipulate files from and to your Mac. If you want to connect again later on, you can just click the Bookmarks icon on the top left. Next you click on History. And then you can double click to re-open the connection. ==Using FileZilla== When you connect to a server using FileZilla, the following layout will appear: [[File:Base_layout.png|700px]] As you can see, the local files are located on the left-hand side, while the remote (server) files are located on the right-hand side. File navigation and paths are also present. [[File:Layout.png|700px]] To transfer a file or folder, you can drag and drop it, either from the local side to the remote side, or from the remote side to the local side. These operations represent uploading and downloading respectively. [[File:Transfer.png|700px]] You can also press enter while selecting a file, or double-click a file, to transfer it. [[File:Transfer2.png|700px]] To open a folder, you can double-click it, or press enter while selecting it. [[File:Open.png|700px]] You can delete files or folders by pressing the delete button while selecting them, or by right-clicking and clicking 'delete'. [[File:Delete.png|700px]] To create files or folders remotely, you can right-click the remote window and click 'create directory' or 'create new file'. [[File:Create_directory.png|700px]] [[File:Create_file.png|700px]] As you can see, the menu has some more interesting options, for example 'rename' or 'view/edit'. ==Non-graphical methods== You can also use a terminal (on Linux) or Putty (on Windows) to access your files. Connect to the server as described above, and use commands as <code>cd</code>, <code>ls</code>, <code>mkdir</code>, <code>rm</code>, <code>nano</code> or <code>chmod</code> to manage your files. You can also use <code>scp</code> (secure copy) to copy files from and to the servers (don't use <code>ssh</code> first). For example, to copy a file called <code>file.txt</code> to your home dir on the server, use (with <code>username</code> your username and <code>/home/user/username</code> your home dir as described above): scp file.txt username@ssh1.ulyssis.org:/home/user/username For other examples and more info, see http://www.hypexr.org/linux_scp_help.php. [[Category:Files]] [[Category:Shell]] 5063744c95d279e792c3640640171b76cec8e41d 0 19 1245 1178 2021-03-30T19:13:28Z Bert 8 wikitext text/x-wiki Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mailbox regularly, because all important information will be sent to this address. You can check your e-mail using webmail or an email client of your own. It is also possible to configure your email address in UCC to automatically [[Forwarders|forward]] all correspondence to another address. ==Webmail== You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to login. ==POP and IMAP access== You can access your ulyssis mail with POP or IMAP. The configuration parameters are: * '''server''': <code>mail.ulyssis.org</code> * '''port''': 993 * '''username''': ''your ULYSSIS username'' * '''password''': ''your ULYSSIS password'' * '''security''': SSL ==SMTP== ULYSSIS doesn't offer SMTP. Instead, you can use KULeuven's SMTP server: * '''server''': <code>smtps.kuleuven.be</code> * '''port''': 443 * '''username''': ''your student id'' * '''password''': ''your KULeuven password'' * '''security''': SSL == Advanced == Your emails are stored within your account under ~/Maildir. These files can of course be read with a command line email client such as alpine or mutt. We support sendmail style local delivery using .forward. More information is available in the official documentation of [https://www.sendmail.org/~ca/email/doc8.9/op-sh-2.html#sh-2.8 Sendmail] and [http://www.postfix.org/local.8.html Postfix]. While it's possible to use .forward to simply forward email to other addresses, we recommend only using it when the same feature is not available through our control panel [https://ucc.ulyssis.org UCC]. Specifically, .forward can be used to pass emails to other applications. In the past, a popular application to pass email through was procmail. However, procmail has not seen development for about 2 decades, and its developer suggests not using it anymore. So while some users may find procmail filters useful, we do not support or suggest its use anymore. A detailed manual for procmail is available on the [https://wiki.archlinux.org/index.php/Procmail ArchWiki]. [[Category:Mail]] 29c882eea10ea4655b5791ec703782880d868ff6 0 3 1246 1234 2021-04-08T18:17:17Z Vincenttc 21 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Reducing disk usage|Help, my account uses too much disk space]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] * [[Secure file permissions]] * [[Reducing disk usage]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2020]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Sending email from websites]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL/TLS|Getting SSL/TLS (HTTPS security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Claiming a port]] * [[ULYSSIS security measures]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] * [[Spam]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up WordPress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] * [[Using PHPPgAdmin]] * [[Using Adminer]] * [[Making Backups]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 7062654e5d72ad27d6f6290f2e4a665ccb78810f 6 158 1248 2021-04-13T14:13:22Z Wtas 42 wikitext text/x-wiki Quick Connect screen for Cyberduck 78bee56ec012d9298d9b8b40512f780233ad9495 6 159 1249 2021-04-13T14:22:14Z Allys 44 wikitext text/x-wiki Showing where people have to enable auto-updates 350138310465120bd432c88d5f519d68ce84b187 6 160 1250 2021-04-13T14:57:55Z Allys 44 wikitext text/x-wiki Showing where you can enable auto-updates fb62b5a043b9ff108de8446edee72aa9a3b559ab 6 161 1251 2021-04-13T15:00:08Z Wtas 42 wikitext text/x-wiki Adding a bookmark in Cyberduck 7d9cb3b8b1b14ad6e566698db367ab10650040b9 6 162 1252 2021-04-13T15:27:53Z Allys 44 wikitext text/x-wiki explanation for auto updates plugins d5cdf99d6380caef5ef50526012b88a4c1e85b1c 6 163 1254 2021-04-13T16:02:19Z Allys 44 wikitext text/x-wiki explanation for how to toggle auto-update your themes feaa56932fa981529974364d195d26ff4e267ec5 0 164 1255 2021-04-13T16:14:59Z Allys 44 Making of this page wikitext text/x-wiki === Automatic updates for WordPress === * Go to '''Dashboard''' at the upper left of the screen and go to '''updates''' * Toggle <u>Enable automatic updates for all new versions of WordPress</u> [[File:Enable WordPress updates.png|left|frameless|630x630px]] === Automatic updates for plugins === * Navigate to '''Plugins''' in the left sidebar and select '''Installed plugins''' * In the dropdown menu select '''Enable Auto-updates'''. [[File:Explanation for auto-updates plugins.png|center|frameless]] * Check the boxes next to the plugins you want to update automatically * Press '''Apply''' next to the previously mentioned dropdown menu === Automatic updates for themes === * Navigate to '''Appearance''' in the left sidebar and select '''Themes''' * Click on the theme thumbnail and select <u>Enable auto-updates</u>, this must be done for every theme separately [[File:Auto-update themes.png|center|frameless|781x781px]] 709cef68a0d63aaa023947289853e9f2a3e06f4e 1256 1255 2021-04-13T16:15:32Z Allys 44 wikitext text/x-wiki === Automatic updates for WordPress === * Go to '''Dashboard''' at the upper left of the screen and go to '''updates''' * Toggle <u>Enable automatic updates for all new versions of WordPress</u> [[File:Enable WordPress updates.png|frameless|630x630px|alt=|center]] === Automatic updates for plugins === * Navigate to '''Plugins''' in the left sidebar and select '''Installed plugins''' * In the dropdown menu select '''Enable Auto-updates'''. [[File:Explanation for auto-updates plugins.png|center|frameless]] * Check the boxes next to the plugins you want to update automatically * Press '''Apply''' next to the previously mentioned dropdown menu === Automatic updates for themes === * Navigate to '''Appearance''' in the left sidebar and select '''Themes''' * Click on the theme thumbnail and select <u>Enable auto-updates</u>, this must be done for every theme separately [[File:Auto-update themes.png|center|frameless|781x781px]] 1de0cd1ff3e8b716ac4b9cc795081d9d1def0ee6 1266 1256 2021-04-17T13:25:30Z Allys 44 Bert zijn tips toegepast wikitext text/x-wiki It is very important to keep your website and plugins up to date.. Not updating a WordPress website or its plugins can lead to safety risks. The updates can be automated manually or automatically. Automatic updates are very easy as there is no need to update daily or at least weekly. If you were to update it manually, this would be the case. It is also safer as WordPress is often at risk only a few days after each update. Keeping it up to date avoids security risks, sometimes regarding cybercriminals, and ensure your own safety. The instructions for updating manually are found at the bottom of the page, after the instructions for automatic updates. === Automatic updates for WordPress === * Go to '''Dashboard''' at the upper left of the screen and go to '''updates''' * Toggle <u>Enable automatic updates for all new versions of WordPress</u> [[File:Enable WordPress updates.png|frameless|630x630px|alt=|center]] === Automatic updates for plugins === * Navigate to '''Plugins''' in the left sidebar and select '''Installed plugins''' * In the dropdown menu select '''Enable Auto-updates'''. [[File:Auto updates for plugins.png|frameless]] * Check the boxes next to the plugins you want to update automatically * Press '''Apply''' next to the previously mentioned dropdown menu === Automatic updates for themes === * Navigate to '''Appearance''' in the left sidebar and select '''Themes''' * Click on the theme thumbnail and select <u>Enable auto-updates</u>, this must be done for every theme separately [[File:Auto-update themes.png|center|frameless|781x781px]] === Manually updating Wordpress, plugins and themes === * If there is an update, there will be a notification in the left bar of the interface. [[File:Needed updates .png|frameless]] * Go to '''Dashboard''' at the upper left of the screen and go to '''updates''' * All updates will be visible on this page, click the '''Update Plugins''' or '''Update Version''' Button 364ccf4e32a02dcd007fa60b59513305a07cc041 1267 1266 2021-04-17T13:26:04Z Allys 44 wikitext text/x-wiki It is very important to keep your website and plugins up to date.. Not updating a WordPress website or its plugins can lead to safety risks. The updates can be automated manually or automatically. Automatic updates are very easy as there is no need to update daily or at least weekly. If you were to update it manually, this would be the case. It is also safer as WordPress is often at risk only a few days after each update. Keeping it up to date avoids security risks, sometimes regarding cybercriminals, and ensure your own safety. The instructions for updating manually are found at the bottom of the page, after the instructions for automatic updates. === Automatic updates for WordPress === * Go to '''Dashboard''' at the upper left of the screen and go to '''updates''' * Toggle <u>Enable automatic updates for all new versions of WordPress</u> [[File:Enable WordPress updates.png|frameless|630x630px|alt=|center]] === Automatic updates for plugins === * Navigate to '''Plugins''' in the left sidebar and select '''Installed plugins''' * In the dropdown menu select '''Enable Auto-updates'''. [[File:Auto updates for plugins.png|frameless]] * Check the boxes next to the plugins you want to update automatically * Press '''Apply''' next to the previously mentioned dropdown menu === Automatic updates for themes === * Navigate to '''Appearance''' in the left sidebar and select '''Themes''' * Click on the theme thumbnail and select <u>Enable auto-updates</u>, this must be done for every theme separately [[File:Auto-update themes.png|center|frameless|781x781px]] === Manually updating Wordpress, plugins and themes === * If there is an update, there will be a notification in the left bar of the interface. [[File:Needed updates .png|frameless]] * Go to '''Dashboard''' at the upper left of the screen and go to '''updates''' * All updates will be visible on this page, click the '''Update Plugins''' or '''Update Version''' Button 3a39ba74dc3fddacbdc63c176ffe42ced56cbaa6 1268 1267 2021-04-17T13:26:28Z Allys 44 wikitext text/x-wiki It is very important to keep your website and plugins up to date.. Not updating a WordPress website or its plugins can lead to safety risks. The updates can be automated manually or automatically. Automatic updates are very easy as there is no need to update daily or at least weekly. If you were to update it manually, this would be the case. It is also safer as WordPress is often at risk only a few days after each update. Keeping it up to date avoids security risks, sometimes regarding cybercriminals, and ensure your own safety. The instructions for updating manually are found at the bottom of the page, after the instructions for automatic updates. === Automatic updates for WordPress === * Go to '''Dashboard''' at the upper left of the screen and go to '''updates''' * Toggle <u>Enable automatic updates for all new versions of WordPress</u> [[File:Enable WordPress updates.png|frameless|630x630px|alt=|center]] === Automatic updates for plugins === * Navigate to '''Plugins''' in the left sidebar and select '''Installed plugins''' * In the dropdown menu select '''Enable Auto-updates'''. [[File:Auto updates for plugins.png|frameless]] * Check the boxes next to the plugins you want to update automatically * Press '''Apply''' next to the previously mentioned dropdown menu === Automatic updates for themes === * Navigate to '''Appearance''' in the left sidebar and select '''Themes''' * Click on the theme thumbnail and select <u>Enable auto-updates</u>, this must be done for every theme separately [[File:Auto-update themes.png|center|frameless|781x781px]] === Manually updating Wordpress, plugins and themes === * If there is an update, there will be a notification in the left bar of the interface. [[File:Needed updates .png|frameless]] * Go to '''Dashboard''' at the upper left of the screen and go to '''updates''' * All updates will be visible on this page, click the '''Update Plugins''' or '''Update Version''' Button 6e50020f1e9263b4b3329ec007758794c843b633 1269 1268 2021-04-17T13:41:30Z Allys 44 wikitext text/x-wiki It is very important to keep your website and plugins up to date.. Not updating a WordPress website or its plugins can lead to safety risks. The updates can be automated manually or automatically. Automatic updates are very easy as there is no need to update daily or at least weekly. If you were to update it manually, this would be the case. It is also safer as WordPress is often at risk only a few days after each update. Keeping it up to date avoids security risks, sometimes regarding cybercriminals, and ensure your own safety. The instructions for updating manually are found at the bottom of the page, after the instructions for automatic updates. === Automatic updates for WordPress === * Go to '''Dashboard''' at the upper left of the screen and go to '''updates''' * Toggle <u>Enable automatic updates for all new versions of WordPress</u> [[File:Enable WordPress updates.png|frameless|630x630px|alt=|center]] === Automatic updates for plugins === * Navigate to '''Plugins''' in the left sidebar and select '''Installed plugins''' * In the dropdown menu select '''Enable Auto-updates'''. [[File:Auto updates for plugins.png|frameless]] * Check the boxes next to the plugins you want to update automatically * Press '''Apply''' next to the previously mentioned dropdown menu === Automatic updates for themes === * Navigate to '''Appearance''' in the left sidebar and select '''Themes''' * Click on the theme thumbnail and select <u>Enable auto-updates</u>, this must be done for every theme separately [[File:Auto-update themes.png|center|frameless|781x781px]] === Manually updating Wordpress, plugins and themes === * If there is an update, there will be a notification in the left bar of the interface. [[File:Needed updates .png|frameless]] * Go to '''Dashboard''' at the upper left of the screen and go to '''updates''' * All updates will be visible on this page. First check the boxes next to the plugins you want to update * Now click the '''Update Plugins''' button. The same can be done for the WordPress version and the themes. 421626b9d71739cfdcd01c6e20e55b873efa0333 1270 1269 2021-04-19T00:22:58Z Bert 8 wikitext text/x-wiki It is very important to keep your website and plugins up to date.. Not updating a WordPress website or its plugins can lead to safety risks. The updates can be automated manually or automatically. Automatic updates are very easy as there is no need to update daily or at least weekly. If you were to update it manually, this would be the case. It is also safer as WordPress is often at risk only a few days after each update. Keeping it up to date avoids security risks, sometimes regarding cybercriminals, and ensure your own safety. The instructions for updating manually are found at the bottom of the page, after the instructions for automatic updates. == Automatic updates == === Automatic updates for WordPress === * Go to '''Dashboard''' at the upper left of the screen and go to '''updates''' * Toggle <u>Enable automatic updates for all new versions of WordPress</u> [[File:Enable WordPress updates.png|frameless|630x630px|alt=|center]] === Automatic updates for plugins === * Navigate to '''Plugins''' in the left sidebar and select '''Installed plugins''' * In the dropdown menu select '''Enable Auto-updates'''. [[File:Auto updates for plugins.png|frameless]] * Check the boxes next to the plugins you want to update automatically * Press '''Apply''' next to the previously mentioned dropdown menu === Automatic updates for themes === * Navigate to '''Appearance''' in the left sidebar and select '''Themes''' * Click on the theme thumbnail and select <u>Enable auto-updates</u>, this must be done for every theme separately [[File:Auto-update themes.png|center|frameless|781x781px]] == Manually updating WordPress, plugins and themes == * If there is an update, there will be a notification in the left bar of the interface. [[File:Needed updates .png|frameless]] * Go to '''Dashboard''' at the upper left of the screen and go to '''updates''' * All updates will be visible on this page. First check the boxes next to the plugins you want to update * Now click the '''Update Plugins''' button. The same can be done for the WordPress version and the themes. 94581b05d16f83c7cbb9f3efd760333e42a74c3c 1271 1270 2021-04-19T00:36:58Z Bert 8 wikitext text/x-wiki Maintaining de software of your website is crucial to ensure everything remains operational and secure. Making sure to perform updates on a regular basis is an important part of that. Beyond fixing security bugs, updates of WordPress as well as its plugins and themes, may introduce new useful features and ensures that no problems arise when we upgrade our servers every two years. While consistently applying updates has many benefits, the most important aspect for you as an account holder and ULYSSIS as the server maintainer is of course that the information on your website is safe and that your visitors can safely visit your website. We therefore advise that all users enable full updating automation within WordPress. This way, you no longer need to perform updates yourself, but the entire process will be automated. The instructions within this manual primarily go into how to fully automate the process, but you can also find instructions on manual updates. Do keep in mind that security issues, especially in popular plugins or WordPress itself, are often exploited by cybercriminals within a few days after the release of a fix. == Automatic updates == === Automatic updates for WordPress === * Go to '''Dashboard''' at the upper left of the screen and go to '''updates''' * Toggle <u>Enable automatic updates for all new versions of WordPress</u> [[File:Enable WordPress updates.png|frameless|630x630px|alt=|center]] === Automatic updates for plugins === * Navigate to '''Plugins''' in the left sidebar and select '''Installed plugins''' * In the dropdown menu select '''Enable Auto-updates'''. [[File:Auto updates for plugins.png|frameless]] * Check the boxes next to the plugins you want to update automatically * Press '''Apply''' next to the previously mentioned dropdown menu === Automatic updates for themes === * Navigate to '''Appearance''' in the left sidebar and select '''Themes''' * Click on the theme thumbnail and select <u>Enable auto-updates</u>, this must be done for every theme separately [[File:Auto-update themes.png|center|frameless|781x781px]] == Manually updating WordPress, plugins and themes == * If there is an update, there will be a notification in the left bar of the interface. [[File:Needed updates .png|frameless]] * Go to '''Dashboard''' at the upper left of the screen and go to '''updates''' * All updates will be visible on this page. First check the boxes next to the plugins you want to update * Now click the '''Update Plugins''' button. The same can be done for the WordPress version and the themes. 1b3dfed9dd8ba92e43d9571b2c5ef136294e3aac 1272 1271 2021-04-19T00:38:24Z Bert 8 wikitext text/x-wiki Maintaining de software of your website is crucial to ensure everything remains operational and secure. Making sure to perform updates on a regular basis is an important part of that. Beyond fixing security bugs, updates of WordPress as well as its plugins and themes, may introduce new useful features and ensures that no problems arise when we upgrade our servers every two years. While consistently applying updates has many benefits, the most important aspect for you as an account holder and ULYSSIS as the server maintainer is of course that the information on your website is safe and that your visitors can safely visit your website. We therefore advise that all users enable full updating automation within WordPress. This way, you no longer need to perform updates yourself, but the entire process will be automated. The instructions within this manual primarily go into how to fully automate the process, but you can also find instructions on manual updates. Do keep in mind that security issues, especially in popular plugins or WordPress itself, are often exploited by cybercriminals within a few days after the release of a fix. == Automatic updates == === Automatic updates for WordPress === * Go to '''Dashboard''' at the upper left of the screen and go to '''updates''' * Toggle <u>Enable automatic updates for all new versions of WordPress</u> [[File:Enable WordPress updates.png|frameless|500x500px|alt=|center]] === Automatic updates for plugins === * Navigate to '''Plugins''' in the left sidebar and select '''Installed plugins''' * In the dropdown menu select '''Enable Auto-updates'''. [[File:Auto updates for plugins.png|frameless]] * Check the boxes next to the plugins you want to update automatically * Press '''Apply''' next to the previously mentioned dropdown menu === Automatic updates for themes === * Navigate to '''Appearance''' in the left sidebar and select '''Themes''' * Click on the theme thumbnail and select <u>Enable auto-updates</u>, this must be done for every theme separately [[File:Auto-update themes.png|center|frameless|781x781px]] == Manually updating WordPress, plugins and themes == * If there is an update, there will be a notification in the left bar of the interface. [[File:Needed updates .png|frameless]] * Go to '''Dashboard''' at the upper left of the screen and go to '''updates''' * All updates will be visible on this page. First check the boxes next to the plugins you want to update * Now click the '''Update Plugins''' button. The same can be done for the WordPress version and the themes. 118d8b88c9f2dbc5f69c551f58cd84d33507d51c 1281 1272 2021-04-20T08:26:36Z Allys 44 wikitext text/x-wiki Maintaining the software of your website is crucial to ensure everything remains operational and secure. Making sure to perform updates on a regular basis is an important part of that. Beyond fixing security bugs, updates of WordPress as well as its plugins and themes, may introduce new useful features and ensures that no problems arise when we upgrade our servers every two years. While consistently applying updates has many benefits, the most important aspect for you as an account holder and ULYSSIS as the server maintainer is of course that the information on your website is safe and that your visitors can safely visit your website. We therefore advise that all users enable full updating automation within WordPress. This way, you no longer need to perform updates yourself, but the entire process will be automated. The instructions within this manual primarily go into how to fully automate the process, but you can also find instructions on manual updates. Do keep in mind that security issues, especially in popular plugins or WordPress itself, are often exploited by cybercriminals within a few days after the release of a fix. == Automatic updates == === Automatic updates for WordPress === * Go to '''Dashboard''' at the upper left of the screen and go to '''updates''' * Toggle <u>Enable automatic updates for all new versions of WordPress</u> [[File:Enable WordPress updates.png|frameless|500x500px|alt=|center]] === Automatic updates for plugins === * Navigate to '''Plugins''' in the left sidebar and select '''Installed plugins''' * In the dropdown menu select '''Enable Auto-updates'''. * Check the boxes next to the plugins you want to update automatically [[File:Auto updates for plugins.png|frameless]] * Press '''Apply''' next to the previously mentioned dropdown menu === Automatic updates for themes === * Navigate to '''Appearance''' in the left sidebar and select '''Themes''' * Click on the theme thumbnail and select <u>Enable auto-updates</u>, this must be done for every theme separately [[File:Auto-update themes.png|center|frameless|781x781px]] == Manually updating WordPress, plugins and themes == * If there is an update, there will be a notification in the left bar of the interface. [[File:Needed updates .png|frameless]] * Go to '''Dashboard''' at the upper left of the screen and go to '''updates''' * All updates will be visible on this page. First check the boxes next to the plugins you want to update * Now click the '''Update Plugins''' button. The same can be done for the WordPress version and the themes. f8b1f2f8dda18493ee404cc37968c91fff549cc7 1282 1281 2021-04-20T12:08:19Z Allys 44 wikitext text/x-wiki Maintaining the software of your website is crucial to ensure everything remains operational and secure. Making sure to perform updates on a regular basis is an important part of that. Beyond fixing security bugs, updates of WordPress as well as its plugins and themes, may introduce new useful features and ensures that no problems arise when we upgrade our servers every two years. While consistently applying updates has many benefits, the most important aspect for you as an account holder and ULYSSIS as the server maintainer is of course that the information on your website is safe and that your visitors can safely visit your website. We therefore advise that all users enable full updating automation within WordPress. This way, you no longer need to perform updates yourself, but the entire process will be automated. The instructions within this manual primarily go into how to fully automate the process, but you can also find instructions on manual updates. Do keep in mind that security issues, especially in popular plugins or WordPress itself, are often exploited by cybercriminals within a few days after the release of a fix. == Automatic updates == === Automatic updates for WordPress === * Go to '''Dashboard''' at the upper left of the screen and go to '''updates''' * Toggle <u>Enable automatic updates for all new versions of WordPress</u> [[File:Enable WordPress updates.png|frameless|500x500px|alt=|center]] === Automatic updates for plugins === * Navigate to '''Plugins''' in the left sidebar and select '''Installed plugins''' * In the dropdown menu select '''Enable Auto-updates'''. * Check the boxes next to the plugins you want to update automatically [[File:Auto updates for plugins.png|frameless]] * Press '''Apply''' next to the previously mentioned dropdown menu === Automatic updates for themes === * Navigate to '''Appearance''' in the left sidebar and select '''Themes''' * Click on the theme thumbnail and select <u>Enable auto-updates</u>. This must be done for each theme separately [[File:Auto-update themes.png|center|frameless|781x781px]] == Manually updating WordPress, plugins and themes == * Pending updates will be displayed as a notification in the left bar of the interface. [[File:Needed updates .png|frameless]] * Go to '''Dashboard''' at the upper left of the screen and go to '''updates''' * All updates will be visible on this page. First check the boxes next to the plugins you want to update * Now click the '''Update Plugins''' button. The same can be done for the WordPress version and the themes. 64fe586d91c6862440aab14c733bbe1d62670674 1285 1282 2021-04-20T15:00:14Z Allys 44 wikitext text/x-wiki Maintaining the software of your website is crucial to ensure everything remains operational and secure. Making sure to perform updates on a regular basis is an important part of that. Beyond fixing security bugs, updates of WordPress as well as its plugins and themes, may introduce new useful features and ensures that no problems arise when we upgrade our servers every two years. While consistently applying updates has many benefits, the most important aspect for you as an account holder and ULYSSIS as the server maintainer is of course that the information on your website is safe and that your visitors can safely visit your website. We therefore advise that all users enable full updating automation within WordPress. This way, you no longer need to perform updates yourself, but the entire process will be automated. The instructions within this manual primarily go into how to fully automate the process, but you can also find instructions on manual updates. Do keep in mind that security issues, especially in popular plugins or WordPress itself, are often exploited by cybercriminals within a few days after the release of a fix. == Automatic updates == === Automatic updates for WordPress === * Go to '''Dashboard''' at the upper left of the screen and go to '''updates'''. * Toggle <u>Enable automatic updates for all new versions of WordPress</u>. [[File:Enable WordPress updates.png|frameless|500x500px|alt=|center]] === Automatic updates for plugins === * Navigate to '''Plugins''' in the left sidebar and select '''Installed plugins'''. * In the dropdown menu select '''Enable Auto-updates'''. * Check the boxes next to the plugins you want to update automatically. [[File:Auto updates for plugins.png|frameless]] * Press '''Apply''' next to the previously mentioned dropdown menu. === Automatic updates for themes === * Navigate to '''Appearance''' in the left sidebar and select '''Themes'''. * Click on the theme thumbnail and select <u>Enable auto-updates</u>. This must be done for each theme separately. [[File:Auto-update themes.png|center|frameless|781x781px]] == Manually updating WordPress, plugins and themes == * Pending updates will be displayed as a notification in the left bar of the interface. [[File:Needed updates .png|frameless]] * Go to '''Dashboard''' at the upper left of the screen and go to '''updates'''. * All updates will be visible on this page. First check the boxes next to the plugins you want to update. * Now click the '''Update Plugins''' button. The same can be done for the WordPress version and the themes. bb140411a1e91f229db192627f1dce2cb91d041c 1286 1285 2021-04-21T12:28:00Z Allys 44 Feedback uit mails. wikitext text/x-wiki Maintaining the software of your website is crucial to ensure everything remains operational and secure. Making sure to perform updates on a regular basis is an important part of that. Beyond fixing security bugs, updates of WordPress as well as its plugins and themes, may introduce new useful features and ensures that no problems arise when we upgrade our servers every two years. While consistently applying updates has many benefits, the most important aspect for you as an account holder and ULYSSIS as the server maintainer is of course that the information on your website is safe and that your visitors can safely visit your website. We therefore advise that all users enable full updating automation within WordPress. This way, you no longer need to perform updates yourself, but the entire process will be automated. The instructions within this manual primarily go into how to fully automate the process, but you can also find instructions on manual updates. Do keep in mind that security issues, especially in popular plugins or WordPress itself, are often exploited by cybercriminals within a few days after the release of a fix. == Automatic updates == The idea is to log into WordPress' admin dashboard to undergo the following steps. This dashboard is also where you create and edit your pages. === Automatic updates for WordPress === * Go to '''Dashboard''' at the upper left of the screen and go to '''updates'''. * Toggle <u>''Enable automatic updates for all new versions of WordPress''</u>. [[File:Enable WordPress updates.png|frameless|500x500px|alt=|center]] === Automatic updates for plugins === * Navigate to '''Plugins''' in the left sidebar and select '''Installed plugins'''. * In the dropdown menu select '''Enable Auto-updates'''. * Check the boxes next to the plugins you want to update automatically. [[File:Auto updates for plugins.png|frameless]] * Press '''Apply''' next to the previously mentioned dropdown menu. === Automatic updates for themes === * Navigate to '''Appearance''' in the left sidebar and select '''Themes'''. * Click on the theme thumbnail and select <u>''Enable auto-updates''</u>. This must be done for each theme separately. [[File:Auto-update themes.png|center|frameless|781x781px]] == Manually updating WordPress, plugins and themes == We still do not recommend updating manually as it is mote time consuming and a bigger security risk. The following steps are only for updating plugins, but you can perform manual updates for themes and for WordPress itself in a similar way on the respective sections of the updates page. * Pending updates will be displayed as a notification in the left bar of the interface. [[File:Needed updates .png|frameless]] * Go to '''Dashboard''' at the upper left of the screen and go to '''updates'''. * All updates will be visible on this page. First check the boxes next to the plugins you want to update. * Now click the '''Update Plugins''' button. b27ed25e6271fe6b9b5985afe39c829f556184bb 1287 1286 2021-04-22T10:19:15Z Allys 44 wikitext text/x-wiki Maintaining the software of your website is crucial to ensure everything remains operational and secure. Making sure to perform updates on a regular basis is an important part of that. Beyond fixing security bugs, updates of WordPress as well as its plugins and themes, may introduce new useful features and ensures that no problems arise when we upgrade our servers every two years. While consistently applying updates has many benefits, the most important aspect for you as an account holder and ULYSSIS as the server maintainer is of course that the information on your website is safe and that your visitors can safely visit your website. We therefore advise that all users enable full updating automation within WordPress. This way, you no longer need to perform updates yourself, but the entire process will be automated. The instructions within this manual primarily go into how to fully automate the process, but you can also find instructions on manual updates. Do keep in mind that security issues, especially in popular plugins or WordPress itself, are often exploited by cybercriminals within a few days after the release of a fix. == Automatic updates == The idea is to log into WordPress' admin dashboard to undergo the following steps. This dashboard is also where you create and edit your pages. === Automatic updates for WordPress === * Go to '''Dashboard''' at the upper left of the screen and go to '''updates'''. * Toggle ''<nowiki/>'Enable automatic updates for all new versions of WordPress'''. [[File:Enable WordPress updates.png|frameless|500x500px|alt=|center]] === Automatic updates for plugins === * Navigate to '''Plugins''' in the left sidebar and select '''Installed plugins'''. * In the dropdown menu select '''Enable Auto-updates'''. * Check the boxes next to the plugins you want to update automatically. [[File:Auto updates for plugins.png|frameless]] * Press '''Apply''' next to the previously mentioned dropdown menu. === Automatic updates for themes === * Navigate to '''Appearance''' in the left sidebar and select '''Themes'''. * Click on the theme thumbnail and select ''<nowiki/>'Enable auto-updates'''. This must be done for each theme separately. [[File:Auto-update themes.png|center|frameless|781x781px]] == Manually updating WordPress, plugins and themes == We still do not recommend updating manually as it is mote time consuming and a bigger security risk. The following steps are only for updating plugins, but you can perform manual updates for themes and for WordPress itself in a similar way on the respective sections of the updates page. * Pending updates will be displayed as a notification in the left bar of the interface. [[File:Needed updates .png|frameless]] * Go to '''Dashboard''' at the upper left of the screen and go to '''updates'''. * All updates will be visible on this page. First check the boxes next to the plugins you want to update. * Now click the '''Update Plugins''' button. 449d8bd41c1dbdd49a83966dfdfed37ba49c30bb 1288 1287 2021-04-22T11:00:50Z Allys 44 /* Automatic updates */ wikitext text/x-wiki Maintaining the software of your website is crucial to ensure everything remains operational and secure. Making sure to perform updates on a regular basis is an important part of that. Beyond fixing security bugs, updates of WordPress as well as its plugins and themes, may introduce new useful features and ensures that no problems arise when we upgrade our servers every two years. While consistently applying updates has many benefits, the most important aspect for you as an account holder and ULYSSIS as the server maintainer is of course that the information on your website is safe and that your visitors can safely visit your website. We therefore advise that all users enable full updating automation within WordPress. This way, you no longer need to perform updates yourself, but the entire process will be automated. The instructions within this manual primarily go into how to fully automate the process, but you can also find instructions on manual updates. Do keep in mind that security issues, especially in popular plugins or WordPress itself, are often exploited by cybercriminals within a few days after the release of a fix. == Automatic updates == The idea is to log into WordPress' admin dashboard to undergo the following steps. If you can't find an admin or login link on your website itself (often in the footer), you can simply add /wpadmin behind the main URL of your website. This is also where you create and edit your pages. === Automatic updates for WordPress === * Go to '''Dashboard''' at the upper left of the screen and go to '''updates'''. * Toggle ''<nowiki/>'Enable automatic updates for all new versions of WordPress'''. [[File:Enable WordPress updates.png|frameless|500x500px|alt=|center]] === Automatic updates for plugins === * Navigate to '''Plugins''' in the left sidebar and select '''Installed plugins'''. * In the dropdown menu select '''Enable Auto-updates'''. * Check the boxes next to the plugins you want to update automatically. [[File:Auto updates for plugins.png|frameless]] * Press '''Apply''' next to the previously mentioned dropdown menu. === Automatic updates for themes === * Navigate to '''Appearance''' in the left sidebar and select '''Themes'''. * Click on the theme thumbnail and select ''<nowiki/>'Enable auto-updates'''. This must be done for each theme separately. [[File:Auto-update themes.png|center|frameless|781x781px]] == Manually updating WordPress, plugins and themes == We still do not recommend updating manually as it is mote time consuming and a bigger security risk. The following steps are only for updating plugins, but you can perform manual updates for themes and for WordPress itself in a similar way on the respective sections of the updates page. * Pending updates will be displayed as a notification in the left bar of the interface. [[File:Needed updates .png|frameless]] * Go to '''Dashboard''' at the upper left of the screen and go to '''updates'''. * All updates will be visible on this page. First check the boxes next to the plugins you want to update. * Now click the '''Update Plugins''' button. d23cf5ce032f4adb6887594a114c7d95b4a0afc5 1289 1288 2021-04-22T11:07:03Z Allys 44 /* Automatic updates */ wikitext text/x-wiki Maintaining the software of your website is crucial to ensure everything remains operational and secure. Making sure to perform updates on a regular basis is an important part of that. Beyond fixing security bugs, updates of WordPress as well as its plugins and themes, may introduce new useful features and ensures that no problems arise when we upgrade our servers every two years. While consistently applying updates has many benefits, the most important aspect for you as an account holder and ULYSSIS as the server maintainer is of course that the information on your website is safe and that your visitors can safely visit your website. We therefore advise that all users enable full updating automation within WordPress. This way, you no longer need to perform updates yourself, but the entire process will be automated. The instructions within this manual primarily go into how to fully automate the process, but you can also find instructions on manual updates. Do keep in mind that security issues, especially in popular plugins or WordPress itself, are often exploited by cybercriminals within a few days after the release of a fix. == Automatic updates == To undergo the following steps you log into WordPress' admin dashboard. This is also where you create and edit your pages. If you can't find an admin or login link on your website itself (often in the footer), you can simply add /wpadmin behind the main URL of your website. === Automatic updates for WordPress === * Go to '''Dashboard''' at the upper left of the screen and go to '''updates'''. * Toggle ''<nowiki/>'Enable automatic updates for all new versions of WordPress'''. [[File:Enable WordPress updates.png|frameless|500x500px|alt=|center]] === Automatic updates for plugins === * Navigate to '''Plugins''' in the left sidebar and select '''Installed plugins'''. * In the dropdown menu select '''Enable Auto-updates'''. * Check the boxes next to the plugins you want to update automatically. [[File:Auto updates for plugins.png|frameless]] * Press '''Apply''' next to the previously mentioned dropdown menu. === Automatic updates for themes === * Navigate to '''Appearance''' in the left sidebar and select '''Themes'''. * Click on the theme thumbnail and select ''<nowiki/>'Enable auto-updates'''. This must be done for each theme separately. [[File:Auto-update themes.png|center|frameless|781x781px]] == Manually updating WordPress, plugins and themes == We still do not recommend updating manually as it is mote time consuming and a bigger security risk. The following steps are only for updating plugins, but you can perform manual updates for themes and for WordPress itself in a similar way on the respective sections of the updates page. * Pending updates will be displayed as a notification in the left bar of the interface. [[File:Needed updates .png|frameless]] * Go to '''Dashboard''' at the upper left of the screen and go to '''updates'''. * All updates will be visible on this page. First check the boxes next to the plugins you want to update. * Now click the '''Update Plugins''' button. 50b94fc2a96855eeb613a7dbf166016c6fe0d08d 1290 1289 2021-04-22T11:08:42Z Allys 44 De komma wikitext text/x-wiki Maintaining the software of your website is crucial to ensure everything remains operational and secure. Making sure to perform updates on a regular basis is an important part of that. Beyond fixing security bugs, updates of WordPress as well as its plugins and themes, may introduce new useful features and ensures that no problems arise when we upgrade our servers every two years. While consistently applying updates has many benefits, the most important aspect for you as an account holder and ULYSSIS as the server maintainer is of course that the information on your website is safe and that your visitors can safely visit your website. We therefore advise that all users enable full updating automation within WordPress. This way, you no longer need to perform updates yourself, but the entire process will be automated. The instructions within this manual primarily go into how to fully automate the process, but you can also find instructions on manual updates. Do keep in mind that security issues, especially in popular plugins or WordPress itself, are often exploited by cybercriminals within a few days after the release of a fix. == Automatic updates == To undergo the following steps, you log into WordPress' admin dashboard. This is also where you create and edit your pages. If you can't find an admin or login link on your website itself (often in the footer), you can simply add /wpadmin behind the main URL of your website. === Automatic updates for WordPress === * Go to '''Dashboard''' at the upper left of the screen and go to '''updates'''. * Toggle ''<nowiki/>'Enable automatic updates for all new versions of WordPress'''. [[File:Enable WordPress updates.png|frameless|500x500px|alt=|center]] === Automatic updates for plugins === * Navigate to '''Plugins''' in the left sidebar and select '''Installed plugins'''. * In the dropdown menu select '''Enable Auto-updates'''. * Check the boxes next to the plugins you want to update automatically. [[File:Auto updates for plugins.png|frameless]] * Press '''Apply''' next to the previously mentioned dropdown menu. === Automatic updates for themes === * Navigate to '''Appearance''' in the left sidebar and select '''Themes'''. * Click on the theme thumbnail and select ''<nowiki/>'Enable auto-updates'''. This must be done for each theme separately. [[File:Auto-update themes.png|center|frameless|781x781px]] == Manually updating WordPress, plugins and themes == We still do not recommend updating manually as it is mote time consuming and a bigger security risk. The following steps are only for updating plugins, but you can perform manual updates for themes and for WordPress itself in a similar way on the respective sections of the updates page. * Pending updates will be displayed as a notification in the left bar of the interface. [[File:Needed updates .png|frameless]] * Go to '''Dashboard''' at the upper left of the screen and go to '''updates'''. * All updates will be visible on this page. First check the boxes next to the plugins you want to update. * Now click the '''Update Plugins''' button. 52f7bfcfd34218be52119973c49f033f347e6e99 1291 1290 2021-04-22T11:32:32Z Vincenttc 21 /* Manually updating WordPress, plugins and themes */ wikitext text/x-wiki Maintaining the software of your website is crucial to ensure everything remains operational and secure. Making sure to perform updates on a regular basis is an important part of that. Beyond fixing security bugs, updates of WordPress as well as its plugins and themes, may introduce new useful features and ensures that no problems arise when we upgrade our servers every two years. While consistently applying updates has many benefits, the most important aspect for you as an account holder and ULYSSIS as the server maintainer is of course that the information on your website is safe and that your visitors can safely visit your website. We therefore advise that all users enable full updating automation within WordPress. This way, you no longer need to perform updates yourself, but the entire process will be automated. The instructions within this manual primarily go into how to fully automate the process, but you can also find instructions on manual updates. Do keep in mind that security issues, especially in popular plugins or WordPress itself, are often exploited by cybercriminals within a few days after the release of a fix. == Automatic updates == To undergo the following steps, you log into WordPress' admin dashboard. This is also where you create and edit your pages. If you can't find an admin or login link on your website itself (often in the footer), you can simply add /wp-admin behind the main URL of your website. === Automatic updates for WordPress === * Go to '''Dashboard''' at the upper left of the screen and go to '''updates'''. * Toggle ''<nowiki/>'Enable automatic updates for all new versions of WordPress'''. [[File:Enable WordPress updates.png|frameless|500x500px|alt=|center]] === Automatic updates for plugins === * Navigate to '''Plugins''' in the left sidebar and select '''Installed plugins'''. * In the dropdown menu select '''Enable Auto-updates'''. * Check the boxes next to the plugins you want to update automatically. [[File:Auto updates for plugins.png|frameless]] * Press '''Apply''' next to the previously mentioned dropdown menu. === Automatic updates for themes === * Navigate to '''Appearance''' in the left sidebar and select '''Themes'''. * Click on the theme thumbnail and select ''<nowiki/>'Enable auto-updates'''. This must be done for each theme separately. [[File:Auto-update themes.png|center|frameless|781x781px]] == Manually updating WordPress, plugins and themes == We still do not recommend updating manually as it is more time consuming and a bigger security risk. The following steps are only for updating plugins, but you can perform manual updates for themes and for WordPress itself in a similar way on the respective sections of the updates page. * Pending updates will be displayed as a notification in the left bar of the interface. [[File:Needed updates .png|frameless]] * Go to '''Dashboard''' at the upper left of the screen and go to '''updates'''. * All updates will be visible on this page. First check the boxes next to the plugins you want to update. * Now click the '''Update Plugins''' button. 9f8d1af9d9a112d0f9ed8f2c7a7a008ac360df1d 1292 1291 2021-04-22T11:58:49Z Allys 44 wikitext text/x-wiki Maintaining the software of your website is crucial to ensure everything remains operational and secure. Making sure to perform updates on a regular basis is an important part of that. Beyond fixing security bugs, updates of WordPress as well as its plugins and themes, may introduce new useful features and ensures that no problems arise when we upgrade our servers. While consistently applying updates has many benefits, the most important aspect for you as an account holder is of course that the information on your website is safe and that your visitors can safely visit your website. We therefore advise that all users enable full updating automation within WordPress. This way, you no longer need to perform updates yourself, but the entire process will be automated. The instructions within this manual primarily go into how to fully automate the process, but you can also find instructions on manual updates. Do keep in mind that security issues, especially in popular plugins or WordPress itself, are often exploited by cybercriminals within a few days after the release of a fix. == Automatic updates == In order to enable automatic updates, you will need to log in to your site's WordPress admin dashboard. This is also where you create and edit your pages. If you can't find an admin or login link on your website itself (often in the footer), you can simply add /wp-admin behind the main URL of your website. === Automatic updates for WordPress === * Go to '''Dashboard''' at the upper left of the screen and go to '''updates'''. * Toggle ''<nowiki/>'Enable automatic updates for all new versions of WordPress'''. [[File:Enable WordPress updates.png|frameless|500x500px|alt=|center]] === Automatic updates for plugins === * Navigate to '''Plugins''' in the left sidebar and select '''Installed plugins'''. * In the dropdown menu select '''Enable Auto-updates'''. * Check the boxes next to the plugins you want to update automatically. [[File:Auto updates for plugins.png|frameless]] * Press '''Apply''' next to the previously mentioned dropdown menu. === Automatic updates for themes === * Navigate to '''Appearance''' in the left sidebar and select '''Themes'''. * Click on the theme thumbnail and select ''<nowiki/>'Enable auto-updates'''. This must be done for each theme separately. [[File:Auto-update themes.png|center|frameless|781x781px]] == Manually updating WordPress, plugins and themes == We still do not recommend updating manually as it is more time consuming and a bigger security risk. The following steps are only for updating plugins, but you can perform manual updates for themes and for WordPress itself in a similar way on the respective sections of the updates page. * Pending updates will be displayed as a notification in the left bar of the interface. [[File:Needed updates .png|frameless]] * Go to '''Dashboard''' at the upper left of the screen and go to '''updates'''. * All updates will be visible on this page. First check the boxes next to the plugins you want to update. * Now click the '''Update Plugins''' button. c06b7bb865f1634af908d683718170108c62d733 1293 1292 2021-04-22T15:01:39Z Allys 44 intro changes van simon wikitext text/x-wiki Maintaining the software of your website is crucial to ensure everything remains operational and secure. Performing regular updates is an important part of this maintenance. Beyond fixing security bugs, updates of WordPress as well as its plugins and themes, may introduce new useful features and guarantees that no problems arise when we upgrade our servers. While consistently applying updates has many benefits, the most important aspect for you as an account holder is of course that the information on your website is secure and that your visitors can safely visit your website. We therefore advise and strongly encourage all users to completely enable automatic updates within WordPress. This way, you no longer need to perform updates yourself, but the entire process will be automated. The instructions within this manual pprimarily focus on how to fully enable automatic updates, but you can also find instructions on manual updates. Do keep in mind that security issues, especially in popular plugins or WordPress itself, are often exploited by cybercriminals within a few days after the release of a fix. == Automatic updates == In order to enable automatic updates, you will need to log in to your site's WordPress admin dashboard. This is also where you create and edit your pages. If you can't find an admin or login link on your website itself (often in the footer), you can simply add /wp-admin behind the main URL of your website. === Automatic updates for WordPress === * Go to '''Dashboard''' at the upper left of the screen and go to '''updates'''. * Toggle ''<nowiki/>'Enable automatic updates for all new versions of WordPress'''. [[File:Enable WordPress updates.png|frameless|500x500px|alt=|center]] === Automatic updates for plugins === * Navigate to '''Plugins''' in the left sidebar and select '''Installed plugins'''. * In the dropdown menu select '''Enable Auto-updates'''. * Check the boxes next to the plugins you want to update automatically. [[File:Auto updates for plugins.png|frameless]] * Press '''Apply''' next to the previously mentioned dropdown menu. === Automatic updates for themes === * Navigate to '''Appearance''' in the left sidebar and select '''Themes'''. * Click on the theme thumbnail and select ''<nowiki/>'Enable auto-updates'''. This must be done for each theme separately. [[File:Auto-update themes.png|center|frameless|781x781px]] == Manually updating WordPress, plugins and themes == We still do not recommend updating manually as it is more time consuming and a bigger security risk. The following steps are only for updating plugins, but you can perform manual updates for themes and for WordPress itself in a similar way on the respective sections of the updates page. * Pending updates will be displayed as a notification in the left bar of the interface. [[File:Needed updates .png|frameless]] * Go to '''Dashboard''' at the upper left of the screen and go to '''updates'''. * All updates will be visible on this page. First check the boxes next to the plugins you want to update. * Now click the '''Update Plugins''' button. 2c8834b1a89574917af0bc1e12ca38c7a68bb6ce 6 165 1258 2021-04-14T15:09:21Z Wtas 42 wikitext text/x-wiki Connection interface for Cyberduck 6997bfd247525db1ad8fa68bf272f862a8e8f24e 1259 1258 2021-04-14T15:14:02Z Wtas 42 Wtas uploaded a new version of [[File:Cyberduck connection interface.png]] wikitext text/x-wiki Connection interface for Cyberduck 6997bfd247525db1ad8fa68bf272f862a8e8f24e 6 166 1264 2021-04-17T13:11:58Z Allys 44 wikitext text/x-wiki Update needen bij manual updaten 486bb331043ea159ca4597860ed231c7df81160c 6 167 1265 2021-04-17T13:19:18Z Allys 44 wikitext text/x-wiki picture for explanation of auto updates for plugins fae9a41b908b0faf757ac3da49668b134fb46005 0 9 1275 713 2021-04-19T14:40:06Z Alexander 38 wikitext text/x-wiki You can find all your apache logs (like the access.log and error.log) on all of our shell servers in the directory: /var/log/apache_user/''username'' For more information on how to access your files, please visit [[Accessing your files]]. So if your username is ''foobar'' then you can easily access your logs this way: foobar@zap:~$ cd /var/log/apache_user/foobar foobar@zap:/var/log/apache_user/foobar$ ls foobar.ulyssis.be foobar@zap:/var/log/apache_user/foobar$ cd foobar.ulyssis.be foobar@zap:/var/log/apache_user/foobar/foobar.ulyssis.be$ ls access-2014-05-07.log error-2014-05-07.log foobar@zap:/var/log/apache_user/foobar/foobar.ulyssis.be$ tail error-2014-05-07.log [Wed May 07 01:27:14 2014] [error] [client 10.0.0.1] File does not exist: /home/user/foobar/www/favicon.ico If you can't find your username inside of <code>/var/log/apache_user</code>, don't worry. If you enter it with <code>cd foobar</code>, it will automatically appear. ==With FileZilla== You can also access the log files with an SFTP client, like FileZilla. Just enter <tt>/var/log/apache_user/''username''</tt> (replace ''username'' with your username) on the right hand side, where it says "Remote site", and press <tt>Enter</tt>: [[File:Logs.png]] [[Category:Webserver]] 02ec34dff04abbf1b35e85d2f5a770135271b091 0 11 1276 866 2021-04-19T14:56:42Z Alexander 38 wikitext text/x-wiki As described in [[Using your webspace|https://docs.ulyssis.org/Using_your_webspace]], you have your own ULYSSIS domain name that you can use. If you wish, you can also register another domain name. ULYSSIS isn't a domain name registrar, so you'll have to use an external registrar. For example, you can find a list of all registrars for .be at [http://dns.be dns.be]. {{notice|Caution!|Please don't configure your domain to use ns4.ulyssis.student.kuleuven.be, not only will it not work, it may result in unpredictable behaviour.}} If you have registered your own domain and you want to use it with your ULYSSIS account, you need to: # Point your domain name to the following ULYSSIS nameservers: ## ns.ulyssis.student.kuleuven.be ## ns3.ulyssis.student.kuleuven.be ## Optionally: ns2.ulyssis.student.kuleuven.be # Mail us at ulyssis@ulyssis.org, with the following details: ## Your ULYSSIS username ## The domain name you registered ## The directory that you want the domain to point at. This could be your <code>www</code> folder, but any other folder within your home directory is possible. ## Whether you want to receive e-mail at that domain name via ULYSSIS. Note that we need to request this with ICTS, so this will take a while. Please do keep in mind that, just like any change to an account, this can only be requested by the account holder. You can find more information about DNS at http://en.wikipedia.org/wiki/Domain_Name_System. [[Category:Webserver]] 1c9b91de3aab1cb2c548e5b451e8eb5df64ee6d1 0 29 1277 1033 2021-04-19T16:16:19Z Bert 8 wikitext text/x-wiki To register an account, follow these steps: [[File:UCC Request New Account.png|thumb|right]] * Go to https://ucc.ulyssis.org/accounts and log in using your Central KU Leuven Account. * Select the kind of account you wish to register: ** Most people will want to register a '''regular account''' for '''personal use'''. ** If you are a recognised '''faculty union''' (kring), assembly or '''faculty consultative bodies''' (facultair overlegorgaan) you are entitled to this free account. We verify this using the list of recognised faculty unions (kringen) from LOKO on http://loko.be/verenigingen/ and list of recognised faculty consultative bodies from the Studentenraad KU Leuven on https://www.sturakuleuven.be/onze-werking/facultaire-overlegorganen/ . Recognised organisations are not entitled to a free account (see below). ** If you are a '''recognised organisation''' by LOKO or the KU Leuven itself you are entitled to an organisation account, wich has a reduced price. We verify this using the list of recognised faculty unions (kringen) from LOKO on http://loko.be/verenigingen/ , the recognised ensembles and sports teams by KU Leuven on https://www.kuleuven.be/cultuur/doehetzelf/ensembles and https://www.kuleuven.be/sport/sportaanbod/studenten/universitaire-ploegen * After picking your account type you have to choose which options you want, as well as a username and a language. * Accept the ULYSSIS terms of use and confirm your order. * An email will be sent to your KU Leuven email address to confirm your order alongside a request for payment. * As soon as we have received and processed your payment, your account will be activated and you will receive instructions to set a password. [[Category:Account]] d01281419abf297a663c15217b22f97fc0dce490 1278 1277 2021-04-19T16:54:10Z Bert 8 wikitext text/x-wiki To register an account, follow these steps: [[File:UCC Request New Account.png|thumb|right]] * Go to https://ucc.ulyssis.org/accounts and log in using your Central KU Leuven Account. * Select the kind of account you wish to register: ** Most people will want to register a '''regular account''' for '''personal use'''. ** If you are a recognised '''faculty union''' (kring), assembly or '''faculty consultative bodies''' (facultair overlegorgaan) you are entitled to this free account. We verify this using the list of recognised faculty unions (kringen) from LOKO on http://loko.be/verenigingen/ and list of recognised faculty consultative bodies from the Studentenraad KU Leuven on https://www.sturakuleuven.be/onze-werking/facultaire-overlegorganen/ . Recognised organisations are not entitled to a free account (see below). ** If you are a '''recognised organisation''' by LOKO or the KU Leuven itself you are entitled to an organisation account, which has a reduced price. We verify this using the list of recognised faculty unions (kringen) from LOKO on http://loko.be/verenigingen/ and the recognised [https://www.kuleuven.be/cultuur/doehetzelf/ensembles music] and performing arts ensembles by KU Leuven. * After picking your account type you have to choose which options you want, as well as a username and a language. * Accept the ULYSSIS terms of use and confirm your order. * An email will be sent to your KU Leuven email address to confirm your order alongside a request for payment. * As soon as we have received and processed your payment, your account will be activated and you will receive instructions to set a password. [[Category:Account]] f3a1587d1d13382eebc39b3e5efbf33fb6e2f263 1279 1278 2021-04-19T16:55:01Z Bert 8 wikitext text/x-wiki To register an account, follow these steps: [[File:UCC Request New Account.png|thumb|right]] * Go to https://ucc.ulyssis.org/accounts and log in using your Central KU Leuven Account. * Select the kind of account you wish to register: ** Most people will want to register a '''regular account''' for '''personal use'''. ** If you are a recognised '''faculty union''' (kring), assembly or '''faculty consultative bodies''' (facultair overlegorgaan) you are entitled to this free account. We verify this using the list of recognised faculty unions (kringen) from LOKO on http://loko.be/verenigingen/ and list of recognised faculty consultative bodies from the Studentenraad KU Leuven on https://www.sturakuleuven.be/onze-werking/facultaire-overlegorganen/ . Recognised organisations are not entitled to a free account (see below). ** If you are a '''recognised organisation''' by LOKO or the KU Leuven itself you are entitled to an organisation account, which has a reduced price. We verify this using the list of faculty unions (kringen) recognised by [http://loko.be/verenigingen/ LOKO]and the list of recognised [https://www.kuleuven.be/cultuur/doehetzelf/ensembles music] and [https://www.kuleuven.be/cultuur/doehetzelf/podium.htm performing arts] ensembles by KU Leuven. * After picking your account type you have to choose which options you want, as well as a username and a language. * Accept the ULYSSIS terms of use and confirm your order. * An email will be sent to your KU Leuven email address to confirm your order alongside a request for payment. * As soon as we have received and processed your payment, your account will be activated and you will receive instructions to set a password. [[Category:Account]] 31848e77f529b058215e2857dc567bef15235251 1280 1279 2021-04-19T16:55:11Z Bert 8 wikitext text/x-wiki To register an account, follow these steps: [[File:UCC Request New Account.png|thumb|right]] * Go to https://ucc.ulyssis.org/accounts and log in using your Central KU Leuven Account. * Select the kind of account you wish to register: ** Most people will want to register a '''regular account''' for '''personal use'''. ** If you are a recognised '''faculty union''' (kring), assembly or '''faculty consultative bodies''' (facultair overlegorgaan) you are entitled to this free account. We verify this using the list of recognised faculty unions (kringen) from LOKO on http://loko.be/verenigingen/ and list of recognised faculty consultative bodies from the Studentenraad KU Leuven on https://www.sturakuleuven.be/onze-werking/facultaire-overlegorganen/ . Recognised organisations are not entitled to a free account (see below). ** If you are a '''recognised organisation''' by LOKO or the KU Leuven itself you are entitled to an organisation account, which has a reduced price. We verify this using the list of faculty unions (kringen) recognised by [http://loko.be/verenigingen/ LOKO] and the list of recognised [https://www.kuleuven.be/cultuur/doehetzelf/ensembles music] and [https://www.kuleuven.be/cultuur/doehetzelf/podium.htm performing arts] ensembles by KU Leuven. * After picking your account type you have to choose which options you want, as well as a username and a language. * Accept the ULYSSIS terms of use and confirm your order. * An email will be sent to your KU Leuven email address to confirm your order alongside a request for payment. * As soon as we have received and processed your payment, your account will be activated and you will receive instructions to set a password. [[Category:Account]] 8dea5ab273107acbf0cd26d6a8e2d97c43b54bc4 0 10 1283 1213 2021-04-20T13:04:04Z Pcy 37 /* Let's Encrypt */ fullchain verduidelijking wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty consultative bodies (facultaire overlegorganen) recognized by Studentenraad KU Leuven as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. We are not eligible to request SSL/TLS certificates for individuals with a personal account, nor research groups or staff associations. We suggest those latter groups request certificates from KU Leuven ICTS directly or consider Let's Encrypt or another third party service. Before sending us a request, the following steps have to be performed: * Set up the site that needs SSL if that's not already the case * Make sure our nameservers are being used for the involved domain(s), as explained on [[Adding domain names]] * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir -p ~/letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain (the CA file; "full chain", not the regular chain) ├── mydomain.be.crt (the cert file; "public key") └── mydomain.be.key (the key file; "private key") If you already possess the necessary files, renaming and copying them accordingly is sufficient. '''You still have to email us to install your certificate.''' More information in the last section on this page. Otherwise, you can generate or renew your certificates using acme.sh. This is explained in the next section. ==== Generating certificates ==== {{notice|If you use a <code>.htaccess</code> file in the webroot of the domain name, make sure to add the following lines at the top of the file:|<pre><IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule></pre>}} Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll show how to use the acme.sh program to generate certificates on the ULYSSIS servers. '''If you already followed this section to generate certificates, skip to the next section on renewing certificates.''' Firstly, execute the following commands to download the acme.sh script in your home directory and make it executable: curl -o ~/acme.sh https://raw.githubusercontent.com/acmesh-official/acme.sh/master/acme.sh chmod +x ~/acme.sh Next, determine for which domains and subdomains you want to generate a certificate. You will need to generate a single certificate for each domain and subdomain which points to the same folder on your account (in most cases this is <code>www</code> in your home directory). The following example command will generate a certificate for <code>mydomain.be</code> and <code>www.mydomain.be</code> which points to the <code>www</code> folder in the home directory. '''Change the parameters''' as explained below before executing this command! ~/acme.sh --issue --cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt --key-file ~/letsencrypt/mydomain.be/mydomain.be.key --ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain -m "email@mydomain.be" -w ~/www -d mydomain.be -d www.mydomain.be The explanation of these many parameters is as follows: * <code>--issue</code> tells acme.sh to generate a new certificate. * <code>--cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt</code> tells acme.sh to store the certificate file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. '''This folder should already exist''', please refer to the previous section if you have not created this folder yet. * <code>--key-file ~/letsencrypt/mydomain.be/mydomain.be.key</code> tells acme.sh to store the key file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>--ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain</code> tells acme.sh to store the CA file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>-m "email@mydomain.be"</code> tells acme.sh the email address associated with the certificate. Let's Encrypt will remind this email address (if provided) when the certificate is close to expiring. * <code>-w ~/www</code> tells acme.sh where the domains in this certificate point to. Make sure to change the <code>www</code> part if the domains point to a different folder in your home directory. * <code>-d mydomain.be</code> and <code>-d www.mydomain.be</code> tell acme.sh that the certificate should protect <code>mydomain.be</code> and <code>www.mydomain.be</code>. The first domain name will be the "main domain", which is important for renewing. You should '''add all domain names''' pointing to the <code>-w</code> folder. After executing this command with the right parameters, your certificate should be generated successfully. When you have to renew the certificate in the future, you should follow the instructions in the next section. '''Don't forget to email us to install your new certificate.''' More information in the last section on this page. ==== Renewing certificates ==== To renew the certificates of <code>mydomain.be</code>, just execute: ~/acme.sh --renew -d mydomain.be For the <code>-d</code> parameter, you have to provide the '''first''' domain name you provided when generating the certificate (in the previous section, this was <code>mydomain.be</code>. If you are not sure which domain name to use, you can execute the command: ~/acme.sh --list This will generate a list of available certificates, which looks a bit like this: Main_Domain KeyLength SAN_Domains CA Created Renew mydomain.be "" www.mydomain.be LetsEncrypt.org ... ... ... ... ... ... ... ... In this example, the main domain is <code>mydomain.be</code>. The renewed certificates will automatically be copied to the files you provided in the command to generate the certificates (see previous section). '''After renewing the certificate, you have to email us to install your certificate.''' More information in the next section. ==== Getting your certificates installed ==== Check whether everything is stored correctly by executing the following command: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once all steps are done and if you are the '''account holder''', '''you can send us an email clearly stating the account name, for which domains we need to add certificates and where the files are stored'''. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL, so make sure you follow this procedure carefully. [[Category:Webserver]] 245759f6ff7988d6d432f2b362cb2c5eece87e57 1284 1283 2021-04-20T13:12:23Z Vincenttc 21 Reverted edits by [[Special:Contributions/Pcy|Pcy]] ([[User talk:Pcy|talk]]) to last revision by [[User:Bert|Bert]] wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty consultative bodies (facultaire overlegorganen) recognized by Studentenraad KU Leuven as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. We are not eligible to request SSL/TLS certificates for individuals with a personal account, nor research groups or staff associations. We suggest those latter groups request certificates from KU Leuven ICTS directly or consider Let's Encrypt or another third party service. Before sending us a request, the following steps have to be performed: * Set up the site that needs SSL if that's not already the case * Make sure our nameservers are being used for the involved domain(s), as explained on [[Adding domain names]] * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir -p ~/letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain (the CA file) ├── mydomain.be.crt (the cert file; "public key") └── mydomain.be.key (the key file; "private key") If you already possess the necessary files, renaming and copying them accordingly is sufficient. '''You still have to email us to install your certificate.''' More information in the last section on this page. Otherwise, you can generate or renew your certificates using acme.sh. This is explained in the next section. ==== Generating certificates ==== {{notice|If you use a <code>.htaccess</code> file in the webroot of the domain name, make sure to add the following lines at the top of the file:|<pre><IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule></pre>}} Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll show how to use the acme.sh program to generate certificates on the ULYSSIS servers. '''If you already followed this section to generate certificates, skip to the next section on renewing certificates.''' Firstly, execute the following commands to download the acme.sh script in your home directory and make it executable: curl -o ~/acme.sh https://raw.githubusercontent.com/acmesh-official/acme.sh/master/acme.sh chmod +x ~/acme.sh Next, determine for which domains and subdomains you want to generate a certificate. You will need to generate a single certificate for each domain and subdomain which points to the same folder on your account (in most cases this is <code>www</code> in your home directory). The following example command will generate a certificate for <code>mydomain.be</code> and <code>www.mydomain.be</code> which points to the <code>www</code> folder in the home directory. '''Change the parameters''' as explained below before executing this command! ~/acme.sh --issue --cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt --key-file ~/letsencrypt/mydomain.be/mydomain.be.key --ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain -m "email@mydomain.be" -w ~/www -d mydomain.be -d www.mydomain.be The explanation of these many parameters is as follows: * <code>--issue</code> tells acme.sh to generate a new certificate. * <code>--cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt</code> tells acme.sh to store the certificate file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. '''This folder should already exist''', please refer to the previous section if you have not created this folder yet. * <code>--key-file ~/letsencrypt/mydomain.be/mydomain.be.key</code> tells acme.sh to store the key file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>--ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain</code> tells acme.sh to store the CA file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>-m "email@mydomain.be"</code> tells acme.sh the email address associated with the certificate. Let's Encrypt will remind this email address (if provided) when the certificate is close to expiring. * <code>-w ~/www</code> tells acme.sh where the domains in this certificate point to. Make sure to change the <code>www</code> part if the domains point to a different folder in your home directory. * <code>-d mydomain.be</code> and <code>-d www.mydomain.be</code> tell acme.sh that the certificate should protect <code>mydomain.be</code> and <code>www.mydomain.be</code>. The first domain name will be the "main domain", which is important for renewing. You should '''add all domain names''' pointing to the <code>-w</code> folder. After executing this command with the right parameters, your certificate should be generated successfully. When you have to renew the certificate in the future, you should follow the instructions in the next section. '''Don't forget to email us to install your new certificate.''' More information in the last section on this page. ==== Renewing certificates ==== To renew the certificates of <code>mydomain.be</code>, just execute: ~/acme.sh --renew -d mydomain.be For the <code>-d</code> parameter, you have to provide the '''first''' domain name you provided when generating the certificate (in the previous section, this was <code>mydomain.be</code>. If you are not sure which domain name to use, you can execute the command: ~/acme.sh --list This will generate a list of available certificates, which looks a bit like this: Main_Domain KeyLength SAN_Domains CA Created Renew mydomain.be "" www.mydomain.be LetsEncrypt.org ... ... ... ... ... ... ... ... In this example, the main domain is <code>mydomain.be</code>. The renewed certificates will automatically be copied to the files you provided in the command to generate the certificates (see previous section). '''After renewing the certificate, you have to email us to install your certificate.''' More information in the next section. ==== Getting your certificates installed ==== Check whether everything is stored correctly by executing the following command: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once all steps are done and if you are the '''account holder''', '''you can send us an email clearly stating the account name, for which domains we need to add certificates and where the files are stored'''. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL, so make sure you follow this procedure carefully. [[Category:Webserver]] ac0cb4b727810f8740d892f8ff6bdb8a588b7ea8 0 164 1294 1293 2021-04-23T13:01:30Z Allys 44 wikitext text/x-wiki Maintaining the software of your website is crucial to ensure everything remains operational and secure. Performing regular updates is an important part of this maintenance. Beyond fixing security bugs, updates of WordPress, as well as its plugins and themes, may introduce new useful features and guarantees that no problems arise when we upgrade our servers. While consistently applying updates has many benefits, the most important aspect for you as an asministrator is of course that the information on your website is secure and that your visitors can safely visit your website. We therefore advise and strongly encourage all users to completely enable automatic updates within WordPress. This way, you no longer need to perform updates yourself, but the entire process will be automated. The instructions within this manual primarily focus on how to fully enable automatic updates, but you can also find instructions on manual updates. Do keep in mind that security issues, especially in popular plugins or WordPress itself, are often exploited by cybercriminals within a few days after the release of a fix. == Automatic updates == In order to enable automatic updates, you will need to log in to your site's WordPress admin dashboard. This is also where you create and edit your pages. If you can't find an admin or login link on your website itself (often at the bottom of any page), you can simply add /wp-admin behind the main URL of your website. === Automatic updates for WordPress === * Go to '''Dashboard''' at the upper left of the screen and go to '''updates'''. * Toggle ''<nowiki/>'Enable automatic updates for all new versions of WordPress'''. [[File:Enable WordPress updates.png|frameless|500x500px|alt=|center]] === Automatic updates for plugins === * Navigate to '''Plugins''' in the left sidebar and select '''Installed plugins'''. * In the dropdown menu select '''Enable Auto-updates'''. * Check the boxes next to the plugins you want to update automatically. [[File:Auto updates for plugins.png|frameless]] * Press '''Apply''' next to the previously mentioned dropdown menu. === Automatic updates for themes === * Navigate to '''Appearance''' in the left sidebar and select '''Themes'''. * Click on the theme thumbnail and select ''<nowiki/>'Enable auto-updates'''. This must be done for each theme separately. [[File:Auto-update themes.png|center|frameless|781x781px]] == Manually updating WordPress, plugins and themes == We still do not recommend updating manually as it is more time consuming and a bigger security risk. The following steps are only for updating plugins, but you can perform manual updates for themes and for WordPress itself in a similar way on the respective sections of the updates page. * Pending updates will be displayed as a notification in the left bar of the interface. [[File:Needed updates .png|frameless]] * Go to '''Dashboard''' at the upper left of the screen and go to '''updates'''. * All updates will be visible on this page. First check the boxes next to the plugins you want to update. * Now click the '''Update Plugins''' button. 7ae1fd0dcffca6213fd16c04df0e6a2847f76f53 1295 1294 2021-04-23T13:07:12Z Allys 44 wikitext text/x-wiki Maintaining the software of your website is crucial to ensure everything remains operational and secure. Performing regular updates is an important part of this maintenance. Beyond fixing security bugs, updates of WordPress, as well as its plugins and themes, may introduce new useful features and guarantees that no problems arise when we upgrade our servers. While consistently applying updates has many benefits, the most important aspect for you as an administrator is of course that the information on your website is secure and that your visitors can safely visit your website. We therefore advise and strongly encourage all users to completely enable automatic updates within WordPress. This way, you no longer need to perform updates yourself, but the entire process will be automated. The instructions within this manual primarily focus on how to fully enable automatic updates, but you can also find instructions on manual updates. Do keep in mind that security issues, especially in popular plugins or WordPress itself, are often exploited by cybercriminals within a few days after the release of a fix. == Automatic updates == In order to enable automatic updates, you will need to log in to your site's WordPress admin dashboard. This is also where you create and edit your pages. If you can't find an admin or login link on your website itself (often at the bottom of any page), you can simply add /wp-admin behind the main URL of your website. === Automatic updates for WordPress === * Go to '''Dashboard''' at the upper left of the screen and go to '''updates'''. * Toggle ''<nowiki/>'Enable automatic updates for all new versions of WordPress'''. [[File:Enable WordPress updates.png|frameless|500x500px|alt=|center]] === Automatic updates for plugins === * Navigate to '''Plugins''' in the left sidebar and select '''Installed plugins'''. * In the dropdown menu select '''Enable Auto-updates'''. * Check the boxes next to the plugins you want to update automatically. [[File:Auto updates for plugins.png|frameless]] * Press '''Apply''' next to the previously mentioned dropdown menu. === Automatic updates for themes === * Navigate to '''Appearance''' in the left sidebar and select '''Themes'''. * Click on the theme thumbnail and select ''<nowiki/>'Enable auto-updates'''. This must be done for each theme separately. [[File:Auto-update themes.png|center|frameless|781x781px]] == Manually updating WordPress, plugins and themes == We still do not recommend updating manually as it is more time consuming and a bigger security risk. The following steps are only for updating plugins, but you can perform manual updates for themes and for WordPress itself in a similar way on the respective sections of the updates page. * Pending updates will be displayed as a notification in the left bar of the interface. [[File:Needed updates .png|frameless]] * Go to '''Dashboard''' at the upper left of the screen and go to '''updates'''. * All updates will be visible on this page. First check the boxes next to the plugins you want to update. * Now click the '''Update Plugins''' button. 95c37b80ad0b323f0c088d9ea3b93646b04ec5e7 1296 1295 2021-04-23T13:18:21Z Allys 44 wikitext text/x-wiki Maintaining the software of your website is crucial to ensure everything remains operational and secure. Performing regular updates is an important part of this maintenance. Beyond fixing security bugs, updates of WordPress, as well as its plugins and themes, may introduce new useful features and guarantees that no problems arise when we upgrade our servers. While consistently applying updates has many benefits, the most important aspect for you as an account holder is of course that the information on your website is secure and that your visitors can safely visit your website. We therefore advise and strongly encourage all users to completely enable automatic updates within WordPress. This way, you no longer need to perform updates yourself, but the entire process will be automated. The instructions within this manual primarily focus on how to fully enable automatic updates, but you can also find instructions on manual updates. Do keep in mind that security issues, especially in popular plugins or WordPress itself, are often exploited by cybercriminals within a few days after the release of a fix. == Automatic updates == In order to enable automatic updates, you will need to log in to your site's WordPress admin dashboard. This is also where you create and edit your pages. If you can't find an admin or login link on your website itself (often at the bottom of any page), you can simply add /wp-admin behind the main URL of your website. === Automatic updates for WordPress === * Go to '''Dashboard''' at the upper left of the screen and go to '''updates'''. * Toggle ''<nowiki/>'Enable automatic updates for all new versions of WordPress'''. [[File:Enable WordPress updates.png|frameless|500x500px|alt=|center]] === Automatic updates for plugins === * Navigate to '''Plugins''' in the left sidebar and select '''Installed plugins'''. * In the dropdown menu select '''Enable Auto-updates'''. * Check the boxes next to the plugins you want to update automatically. [[File:Auto updates for plugins.png|frameless]] * Press '''Apply''' next to the previously mentioned dropdown menu. === Automatic updates for themes === * Navigate to '''Appearance''' in the left sidebar and select '''Themes'''. * Click on the theme thumbnail and select ''<nowiki/>'Enable auto-updates'''. This must be done for each theme separately. [[File:Auto-update themes.png|center|frameless|781x781px]] == Manually updating WordPress, plugins and themes == We still do not recommend updating manually as it is more time consuming and a bigger security risk. The following steps are only for updating plugins, but you can perform manual updates for themes and for WordPress itself in a similar way on the respective sections of the updates page. * Pending updates will be displayed as a notification in the left bar of the interface. [[File:Needed updates .png|frameless]] * Go to '''Dashboard''' at the upper left of the screen and go to '''updates'''. * All updates will be visible on this page. First check the boxes next to the plugins you want to update. * Now click the '''Update Plugins''' button. 3c7dcb9a9bdc88fa9417d425dc9f5d9189757ad9 1297 1296 2021-04-24T15:00:39Z Allys 44 wikitext text/x-wiki Maintaining the software of your website is crucial to ensure everything remains operational and secure. Performing regular updates is an important part of this maintenance. Beyond fixing security bugs, updates of WordPress, as well as its plugins and themes, may introduce new useful features and guarantees that no problems arise when we upgrade our servers. While consistently applying updates has many benefits, the most important aspect for you as an account holder is of course that the information on your website is secure and that your visitors can safely visit your website. We therefore advise and strongly encourage all users to completely enable automatic updates within WordPress. This way, you no longer need to perform updates yourself, but the entire process will be automated. The instructions within this manual primarily focus on how to fully enable automatic updates, but you can also find instructions on manual updates here. Do keep in mind that security issues, especially in popular plugins or WordPress itself, are often exploited by cybercriminals within a few days after the release of a fix. == Automatic updates == In order to enable automatic updates, you will need to log in to your site's WordPress admin dashboard. This is also where you create and edit your pages. If you can't find an admin or login link on your website itself (often at the bottom of any page), you can simply add /wp-admin behind the main URL of your website. === Automatic updates for WordPress === * Go to '''Dashboard''' at the upper left of the screen and go to '''updates'''. * Toggle ''<nowiki/>'Enable automatic updates for all new versions of WordPress'''. If your automatic updates are already turned on, you will see ''This site is automatically kept up to date with each new version of WordPress''. [[File:Enable WordPress updates.png|frameless|500x500px|alt=|center]] === Automatic updates for plugins === * Navigate to '''Plugins''' in the left sidebar and select '''Installed plugins'''. * In the dropdown menu select '''Enable Auto-updates'''. * Check the boxes next to the plugins you want to update automatically. [[File:Auto updates for plugins.png|frameless]] * Press '''Apply''' next to the previously mentioned dropdown menu. * Do not forget to enable automatic updates every time you install a new plugin. === Automatic updates for themes === * Navigate to '''Appearance''' in the left sidebar and select '''Themes'''. * Click on the theme thumbnail and select ''<nowiki/>'Enable auto-updates'''. This must be done for each theme separately. [[File:Auto-update themes.png|center|frameless|781x781px]] * Do not forget to enable automatic updates every time you install a new theme. == Manually updating WordPress, plugins and themes == We still do not recommend updating manually as it is more time consuming and a bigger security risk. The following steps are only for updating plugins, but you can perform manual updates for themes and for WordPress itself in a similar way on the respective sections of the updates page. * Pending updates will be displayed as a notification in the left bar of the interface. [[File:Needed updates .png|frameless]] * Go to '''Dashboard''' at the upper left of the screen and go to '''updates'''. * All updates will be visible on this page. First check the boxes next to the plugins you want to update. * Now click the '''Update Plugins''' button. e546a63816cd0d600bbe9ab39031291caa4a71ac 1298 1297 2021-04-24T15:09:19Z Allys 44 Allys moved page [[WordPress updates]] to [[Updating WordPress]] wikitext text/x-wiki Maintaining the software of your website is crucial to ensure everything remains operational and secure. Performing regular updates is an important part of this maintenance. Beyond fixing security bugs, updates of WordPress, as well as its plugins and themes, may introduce new useful features and guarantees that no problems arise when we upgrade our servers. While consistently applying updates has many benefits, the most important aspect for you as an account holder is of course that the information on your website is secure and that your visitors can safely visit your website. We therefore advise and strongly encourage all users to completely enable automatic updates within WordPress. This way, you no longer need to perform updates yourself, but the entire process will be automated. The instructions within this manual primarily focus on how to fully enable automatic updates, but you can also find instructions on manual updates here. Do keep in mind that security issues, especially in popular plugins or WordPress itself, are often exploited by cybercriminals within a few days after the release of a fix. == Automatic updates == In order to enable automatic updates, you will need to log in to your site's WordPress admin dashboard. This is also where you create and edit your pages. If you can't find an admin or login link on your website itself (often at the bottom of any page), you can simply add /wp-admin behind the main URL of your website. === Automatic updates for WordPress === * Go to '''Dashboard''' at the upper left of the screen and go to '''updates'''. * Toggle ''<nowiki/>'Enable automatic updates for all new versions of WordPress'''. If your automatic updates are already turned on, you will see ''This site is automatically kept up to date with each new version of WordPress''. [[File:Enable WordPress updates.png|frameless|500x500px|alt=|center]] === Automatic updates for plugins === * Navigate to '''Plugins''' in the left sidebar and select '''Installed plugins'''. * In the dropdown menu select '''Enable Auto-updates'''. * Check the boxes next to the plugins you want to update automatically. [[File:Auto updates for plugins.png|frameless]] * Press '''Apply''' next to the previously mentioned dropdown menu. * Do not forget to enable automatic updates every time you install a new plugin. === Automatic updates for themes === * Navigate to '''Appearance''' in the left sidebar and select '''Themes'''. * Click on the theme thumbnail and select ''<nowiki/>'Enable auto-updates'''. This must be done for each theme separately. [[File:Auto-update themes.png|center|frameless|781x781px]] * Do not forget to enable automatic updates every time you install a new theme. == Manually updating WordPress, plugins and themes == We still do not recommend updating manually as it is more time consuming and a bigger security risk. The following steps are only for updating plugins, but you can perform manual updates for themes and for WordPress itself in a similar way on the respective sections of the updates page. * Pending updates will be displayed as a notification in the left bar of the interface. [[File:Needed updates .png|frameless]] * Go to '''Dashboard''' at the upper left of the screen and go to '''updates'''. * All updates will be visible on this page. First check the boxes next to the plugins you want to update. * Now click the '''Update Plugins''' button. e546a63816cd0d600bbe9ab39031291caa4a71ac 1306 1298 2021-04-25T07:53:09Z Allys 44 added categories wikitext text/x-wiki Maintaining the software of your website is crucial to ensure everything remains operational and secure. Performing regular updates is an important part of this maintenance. Beyond fixing security bugs, updates of WordPress, as well as its plugins and themes, may introduce new useful features and guarantees that no problems arise when we upgrade our servers. While consistently applying updates has many benefits, the most important aspect for you as an account holder is of course that the information on your website is secure and that your visitors can safely visit your website. We therefore advise and strongly encourage all users to completely enable automatic updates within WordPress. This way, you no longer need to perform updates yourself, but the entire process will be automated. The instructions within this manual primarily focus on how to fully enable automatic updates, but you can also find instructions on manual updates here. Do keep in mind that security issues, especially in popular plugins or WordPress itself, are often exploited by cybercriminals within a few days after the release of a fix. == Automatic updates == In order to enable automatic updates, you will need to log in to your site's WordPress admin dashboard. This is also where you create and edit your pages. If you can't find an admin or login link on your website itself (often at the bottom of any page), you can simply add /wp-admin behind the main URL of your website. === Automatic updates for WordPress === * Go to '''Dashboard''' at the upper left of the screen and go to '''updates'''. * Toggle ''<nowiki/>'Enable automatic updates for all new versions of WordPress'''. If your automatic updates are already turned on, you will see ''This site is automatically kept up to date with each new version of WordPress''. [[File:Enable WordPress updates.png|frameless|500x500px|alt=|center]] === Automatic updates for plugins === * Navigate to '''Plugins''' in the left sidebar and select '''Installed plugins'''. * In the dropdown menu select '''Enable Auto-updates'''. * Check the boxes next to the plugins you want to update automatically. [[File:Auto updates for plugins.png|frameless]] * Press '''Apply''' next to the previously mentioned dropdown menu. * Do not forget to enable automatic updates every time you install a new plugin. === Automatic updates for themes === * Navigate to '''Appearance''' in the left sidebar and select '''Themes'''. * Click on the theme thumbnail and select ''<nowiki/>'Enable auto-updates'''. This must be done for each theme separately. [[File:Auto-update themes.png|center|frameless|781x781px]] * Do not forget to enable automatic updates every time you install a new theme. == Manually updating WordPress, plugins and themes == We still do not recommend updating manually as it is more time consuming and a bigger security risk. The following steps are only for updating plugins, but you can perform manual updates for themes and for WordPress itself in a similar way on the respective sections of the updates page. * Pending updates will be displayed as a notification in the left bar of the interface. [[File:Needed updates .png|frameless]] * Go to '''Dashboard''' at the upper left of the screen and go to '''updates'''. * All updates will be visible on this page. First check the boxes next to the plugins you want to update. * Now click the '''Update Plugins''' button. [[Category:CMSs]] [[Category:Security & anti-spam]] 4add251ec8726d05b4543b61829dde9242ba2211 0 168 1299 2021-04-24T15:09:19Z Allys 44 Allys moved page [[WordPress updates]] to [[Updating WordPress]] wikitext text/x-wiki #REDIRECT [[Updating WordPress]] 2997d9cc0772b46d2f556cde759e9c1d7fd8ad4d 0 55 1300 1119 2021-04-24T19:13:22Z Bert 8 wikitext text/x-wiki == Restricting comments == By default, WordPress allows anyone to comment freely on any post you make on your website. While this makes sense when you maintain a blog, it makes less sense when you're using WordPress as the basis for your student organization's website or for something with little to no reader interaction. We therefore advise those with a WordPress installation to consider restricting comments by following these instructions: * Navigate to the WordPress admin dashboard and login * Go to Settings and then Discussion * In almost all cases, you will want to disable link notifications, pingbacks and trackbacks, as these are almost exclusively used for spam nowadays * Consider disabling comments altogether as well ** If you wish to enable some form of comments, consider restricting to logged in users, or require your approval. You may in that case also want to automate spam detection (see below). * It's possible in WordPress to disable comments as a general setting, but still have it enabled on individual posts or pages. Make sure to delete the default test post and page, as well as to look at the discussion setting on every existing post and page. If you can't find this setting, it may be hidden, but available under the "Screen Options" button at the top of the page. == Detecting spam == As mentioned above, it's better in most cases to simply not allow comments or to restrict them very heavily than having to deal with spam. If you have no other choice, there are some options available to help you out. It's important to keep in mind that both options below rely on external service providers for some aspects of their spam detection. === Akismet === Akismet is a plugin by the main company behind WordPress, Automattic. The plugin sends every comment that is posted to an Akismet server, which uses pattern matching, URL detection and other techniques to evaluate whether it's spam or not. Because of its focus on WordPress comments, it is very accurate and can also block spam that was composed and posted by an actual human, as opposed to CAPTCHA which aims to block automated posting only. Keep in mind that Akismet is only free for non-commercial purposes. To use Akismet follow these instructions: * Navigate to the Wordpress admin dashboard and login * Go to Plugins and select Add New * If Akismet Anti-Spam isn't already on the "Featured" page, then search for "akismet" * Install and activate the plugin * You will then be redirected to a settings page, where you can setup an Akismet account and configure your settings. === Google's reCAPTCHA === CAPTCHA, originally from a complicated acronym, is a term used for different kinds of challenges to prevent automated scripts from trying to comment, register or login on websites. reCAPTCHA is a project owned by Google that is quite successful at designing these challenges. You probably know reCAPTCHA as the "I'm not a robot" checkbox you often have to press. More details are available on https://google.com/recaptcha There are several different plugins that make it possible to add reCAPTCHA to WordPress. You can follow these instructions to get started: * Navigate to the WordPress admin dashboard and login * Go to Plugins and select Add New * Search for "recaptcha" * Many of the plugins you will get are well-suited for this task. At the time of writing, ULYSSIS has been using "ReCaptcha Integration for WordPress" for a while. There is however no reason why other plugins won't be suitable. * Install and activate the plugin of your choice * You will then usually be redirected to a settings page, where you will need to enter the keys to use reCAPTCHA. You can register these on https://www.google.com/recaptcha/admin * Make sure to also check other configuration options, not all plugins will necessarily protect comment forms by default * Usually, you can find settings for your different plugins under the settings menu, if you wish to make changes in the future [[Category:Security & anti-spam]] [[Category:CMSs]] ef5af34f7fbba544af4968218090605a08691d20 0 98 1301 1209 2021-04-24T19:16:18Z Bert 8 wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for login through the Central KU Leuven Login (Shibboleth). The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Central KU Leuven Login) enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest/download/MediaWikiShibboleth.zip github]. Unzip the zip file in the <code>extensions/</code> directory in your MediaWiki installation folder. Make sure there is now a <code>MediaWikiShibboleth</code> folder in <code>extensions/</code>. Finally, locate the <code>LocalSettings.php</code> file in your MediaWiki installation folder and add the following lines to it: wfLoadExtension('MediaWikiShibboleth'); $wgGroupPermissions['*']['createaccount'] = false; $wgRevokePermissions['Shibboleth']['editmyprivateinfo'] = true; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 2 lines of the previous paragraph. This really defeats the purpose of the extension though. ==Configuration== MediaWikiShibboleth has some configuration options which allow for restricting who can log in to your wiki. These restrictions are cumulative. For example, it is possible to allow only students enrolled in a specific degree or programme to log in. These options work especially well with restricting the access of the wiki to logged-in users only. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code>LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code>LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code>LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow students enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code>LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. === Translations === It's possible to translate and modify all public MediaWikiShibboleth messages. The translations can be found in the <code>extensions/MediaWikiShibboleth/i18n/</code>. Dutch (<code>nl.json</code>) and English (<code>en.json</code>) translations are already provided. Even the provided translations can be customized, and we strongly advise you to do so, in order to match them with your Wiki situation. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Login without Central KU Leuven login" to expand a login menu. The new log in page looks like this with "Login without Central KU Leuven login" expanded: [[File:Login.png]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png]] [[Category:Security & anti-spam]] [[Category:CMSs]] 1384032c65e5f5e2359eba77e0e05884ae40026a 0 54 1302 781 2021-04-24T19:16:52Z Bert 8 wikitext text/x-wiki Because MediaWiki allows for unrestricted page editing by anonymous users and unrestricted account creation, MediaWiki websites often suffer from automated spam problems. There are 2 main ways to prevent spam on MediaWiki: using a captcha to block automated edits, or restricting account creation to trusted users. == Using captcha == === About ReCaptcha === Google introduced a new generation of ReCaptcha, called NoCaptcha in 2014. Using the MediaWiki extension ConfirmEdit, NoCaptcha can be used to prevent spam on wikis. ConfirmEdit is bundled with MediaWiki by default, but to enable NoCaptcha, you will have to get an API key from Google. === Installation === The NoCaptcha ConfirmEdit extension requires MediaWiki 1.26 or higher. First, you have to get an API key from Google. Go to Google's ReCaptcha [https://www.google.com/recaptcha/admin administrator page] and register your website. You will need to select '''reCAPTCHA v2''', and '''"I'm not a robot" Checkbox'''. After registering your website, you will be presented with a public '''site key''' and a private '''secret key'''. Now you have to install and configure the ConfirmEdit extension. Locate the <code>LocalSettings.php</code> file in your MediaWiki installation folder and add the following lines to it: wfLoadExtensions([ 'ConfirmEdit', 'ConfirmEdit/ReCaptchaNoCaptcha' ]); $wgCaptchaClass = 'ReCaptchaNoCaptcha'; $wgReCaptchaSiteKey = ''''your public/site key here''''; $wgReCaptchaSecretKey = ''''your private/secret key here''''; $wgCaptchaTriggers['edit'] = true; // Trigger captcha for page edits. $wgCaptchaTriggers['create'] = true; // Trigger captcha for page creation. $wgCaptchaTriggers['addurl'] = true; // Trigger captcha for page edits containing URLs. $wgCaptchaTriggers['createaccount'] = true; // Trigger captcha for account creation. $wgCaptchaTriggers['badlogin'] = true; // Trigger captcha for login hacking attempts. More information about the configuration options for advanced usage can be found here: https://www.mediawiki.org/wiki/Extension:ConfirmEdit#Configuration == Restricting account creation == Because MediaWiki allows unregistered (anonymous) users to edit pages, this technique obviously relies on restricting page edits to logged-in users. To enable this, locate the <code>LocalSettings.php</code> file in your MediaWiki installation folder and add the following lines to it: $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createtalk'] = false; $wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['writeapi'] = false; Now only registered users can edit or create pages. However, the problem is not solved, as bots can automatically create an account to perform the spamming. There are 3 options to prevent this. === Centrale KU Leuven Login === Wikis connected to the KU Leuven Association can install an extension to use the Centrale KU Leuven Login. For more information about this option, there is the documentation page [[Securing MediaWiki using Centrale KU Leuven Login]]. === Sysop account creation === Account creation can be restricted to only website administrators ('sysop'). Add the following line to <code>LocalSettings.php</code>: $wgGroupPermissions['*']['createaccount'] = false; === Account creation queue === Using the extension [https://www.mediawiki.org/wiki/Extension:ConfirmAccount ConfirmAccount], account creation has to be manually confirmed by website administrators. Users are still able to create an account, but the account has to be confirmed before the user can log in. For more information, installation instructions and configuration, refer to the link above. [[Category:Security & anti-spam]] [[Category:CMSs]] 808eb5592aebaff1dd46829d6b2564bda963198c 0 56 1303 873 2021-04-24T19:17:17Z Bert 8 wikitext text/x-wiki ==Google's recaptcha== ===What is recaptcha and how/will it help prevent spam ?=== For answers to those questions you can look at google's page about recaptcha (https://google.com/recaptcha) ===Installation=== This installation guide requires drupal '''6,7 or preferably 8''' (or higher). '''Note this installation requires captcha and recaptcha, these are different plugins and not a type error.''' * Go to drupal's captcha page and download the appropriate version at the bottom of the page (https://www.drupal.org/project/captcha) * Go to drupal's recaptcha page and download the appropriate version at the bottom of the page (https://www.drupal.org/project/recaptcha) ** Extract the archives into '''sites/all/modules/[recaptcha/captcha]'''respectively and relative to your own drupal installation '''(this folder may need to be created manually)''' * Now navigate to your drupal administration page in your browser (/admin/modules) ** Search for captcha and enable it ** Search for recaptcha and enable it * Once complete it is '''critical''' to configure your captcha setting in the web interface (/admin/config/people/captcha) '''and do not forget to enable the captcha-points (/admin/config/people/captcha/captcha-points). [[Category:Security & anti-spam]] [[Category:CMSs]] 59523355b142c217c7e7a435ed47a9f95a2f839c 0 57 1304 872 2021-04-24T19:17:30Z Bert 8 wikitext text/x-wiki ==Google's recaptcha== ===What is recaptcha and how does/will it help prevent spam ?=== For answers to those questions you can look at google's page about recaptcha (https://google.com/recaptcha) ===Installation=== This installation guide requires joomla '''3.4''' (or higher). * Go to google's recaptcha administrator page(https://www.google.com/recaptcha/admin) and register your site **example of public and private key (https://i.imgur.com/vGJKEXx.png) * Navigate to the admin panel of your joomla instalation ** Select plugins from the extentions panel in the top menu. * Search for recaptcha in the search box ** Enable recaptcha by clicking on the status icon next to recaptcha * One complete it is '''critical''' that you configure your recaptcha properly ** Go to recaptcha's configuration page by selecting recaptcha in the above mentioned panel ** '''make sure you select version 2 (default is version 1)''' ** Fill in the required keys you got on google's recaptcha's administrator page * Once done joomla will begin to require recaptcha's [[Category:Security & anti-spam]] [[Category:CMSs]] 835005c9e7b24cd8ea60f79e431d7a46ae660cb4 0 3 1305 1246 2021-04-25T07:50:31Z Allys 44 Added Updating WordPress wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Help, my account has been disabled]] * [[Reducing disk usage|Help, my account uses too much disk space]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] * [[Secure file permissions]] * [[Reducing disk usage]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2020]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Sending email from websites]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL/TLS|Getting SSL/TLS (HTTPS security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Claiming a port]] * [[ULYSSIS security measures]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] * [[Spam]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up WordPress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] * [[Updating WordPress]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] * [[Using PHPPgAdmin]] * [[Using Adminer]] * [[Making Backups]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 1e58b1e14525224ea5739f7106967dbb8cf3564f 1327 1305 2021-04-26T18:55:21Z Vincenttc 21 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Reducing disk usage|Help, my account uses too much disk space]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] * [[Secure file permissions]] * [[Reducing disk usage]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2020]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Sending email from websites]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL/TLS|Getting SSL/TLS (HTTPS security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Claiming a port]] * [[ULYSSIS security measures]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] * [[Spam]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up WordPress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] * [[Updating WordPress]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] * [[Using PHPPgAdmin]] * [[Using Adminer]] * [[Making Backups]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[KULoket agenda iCal feed]] </div> <div style="clear:both;"></div> </div> __NOTOC__ df6e89dd418a6dc8fc0abe1ebfb0b7b878a6a58d 6 169 1307 2021-04-25T15:04:52Z Wtas 42 wikitext text/x-wiki bookmark select with blur da8ef63867a228019d8b8ef6aea02cc37f4b3057 6 170 1308 2021-04-25T15:07:37Z Wtas 42 wikitext text/x-wiki dialog window asking to trust a fingerpint dbd085bb3a20dff9e3c7407aca5cbc44074ec7fe 6 171 1309 2021-04-25T15:22:33Z Wtas 42 wikitext text/x-wiki upload button for Cyberduck f2adff796d2d0dc27a51c77b98535f456e42da8a 6 172 1310 2021-04-25T15:41:55Z Wtas 42 wikitext text/x-wiki picture to explain dragging a file to upload it 07b81319ea1775d6a5dfc481f5d5c518e9596c85 6 173 1311 2021-04-25T16:16:26Z Wtas 42 wikitext text/x-wiki open a connection dialog 5abebaf710d916aa5bc5e1c889725c1b6fe434c9 6 174 1312 2021-04-25T16:24:09Z Wtas 42 wikitext text/x-wiki download grab with blur 53c9f2ff0851c357d05c1595748353c69ef3a5dc 6 175 1313 2021-04-25T16:37:08Z Wtas 42 wikitext text/x-wiki Navigating in Cyberduck 0dbedf98422e398de542e68b9b4805efa175a3c4 0 176 1315 2021-04-25T17:31:14Z Yoa 30 Created page with "The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their inst..." wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are very dense, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. With this out of the way, you can start the MediaWiki update process. == Downloading the latest version == Most likely, you arrived at this page after receiving an email from our [[Software Version Checker]]. This email might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the latest version. Of course, to update MediaWiki to this latest version, you will need to download the update. The MediaWiki downloads can be found [https://www.mediawiki.org/wiki/Download here]. Make sure to download the zip file for the latest version from the email and save it somewhere on your PC. == Making a backup == An important step in the update process is to create a backup of your data on the ULYSSIS server, to prevent data loss if something goes wrong. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. The backup step consists of roughly two parts: * Creating a backup of your wiki database. If you use MySQL or PostgreSQL, you can follow the instructions on [[Making Backups#A backup of your databases]]. If you use SQLite, please refer to [https://www.mediawiki.org/wiki/Manual:Upgrading#Back_up_existing_files_and_the_database the official instructions]. If you are not sure about your database type or the name of your wiki database, you can search the <code>LocalSettings.php</code> configuration file for the following lines: ## Database settings $wgDBtype = "<db_type>"; $wgDBserver = "<db_server>"; $wgDBname = "<db_name>"; $wgDBuser = "<user>"; $wgDBpassword = "<password>"; * Creating a backup of your wiki files. The easiest way to do this is to '''rename''' the directory containing your <code>LocalSettings.php</code> configuration file (your wiki location) to a new directory. For example, if <code>LocalSettings.php</code> is stored in <code><username>/www/wiki</code>, you should '''rename''' this directory to <code><username>/www/wiki_backup</code>, or something similar. == Extracting the new files == Now, you will need to extract the zip file you downloaded in step 1. This should result in a directory which looks something like: mediawiki-xxx/ ├── cache/ ├── docs/ ├── ... ├── api.php ├── autoload.php └── ... Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if your wiki was located at <code><username>/www/wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. Next, you should upload this directory to your ULYSSIS account, to the original location of your wiki. If you followed step 2 correctly, the old files should be moved to a backup directory. As a result, after uploading, your ULYSSIS acocunt should contain the new files in something like <code><username>/www/wiki</code>, and the old files in <code><username>/www/wiki_backup</code>. Please refer to [[Accessing your files]] if you don't know how to upload files. Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. Although only you know exactly which files these are, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The <code>images/</code> directory, which contains all the uploaded files to the wiki, unless you have chosen a different upload directory. In that case, you should copy the different upload directory. * In case you use a custom logo, this file also needs to be restored from backup. This logo is stored in <code>resources/assets/</code> or <code>images/</code>, depending on what you chose to use. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any modifications made to the old installation files, extensions, or skins. For example, this includes miscellaneous modifications to the configuration of extensions or skins. * Any <code>.htaccess</code> file, if present. 94eb01663c9e815f09ddb889f7b6eab43c3e1131 1316 1315 2021-04-25T19:34:46Z Yoa 30 wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are very dense, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. With this out of the way, you can start the MediaWiki update process. == Downloading the latest version == Most likely, you arrived at this page after receiving an email from our [[Software Version Checker]]. This email might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the latest version. Of course, to update MediaWiki to this latest version, you will need to download the update. The MediaWiki downloads can be found [https://www.mediawiki.org/wiki/Download here]. Make sure to download the zip file for the latest version from the email and save it somewhere on your PC. == Making a backup == An important step in the update process is to create a backup of your data on the ULYSSIS server, to prevent data loss if something goes wrong. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. The backup step consists of roughly two parts: * Creating a backup of your wiki database. If you use MySQL or PostgreSQL, you can follow the instructions on [[Making Backups#A backup of your databases]]. If you use SQLite, please refer to [https://www.mediawiki.org/wiki/Manual:Upgrading#Back_up_existing_files_and_the_database the official instructions]. If you are not sure about your database type or the name of your wiki database, you can search the <code>LocalSettings.php</code> configuration file for the following lines: ## Database settings $wgDBtype = "<db_type>"; $wgDBserver = "<db_server>"; $wgDBname = "<db_name>"; $wgDBuser = "<user>"; $wgDBpassword = "<password>"; * Creating a backup of your wiki files. The easiest way to do this is to '''rename''' the directory containing your <code>LocalSettings.php</code> configuration file (your wiki location) to a new directory. For example, if <code>LocalSettings.php</code> is stored in <code><username>/www/wiki</code>, you should '''rename''' this directory to <code><username>/www/wiki_backup</code>, or something similar. == Extracting the new files == Now, you will need to extract the zip file you downloaded in step 1. This should result in a directory which looks something like: mediawiki-xxx/ ├── cache/ ├── docs/ ├── ... ├── api.php ├── autoload.php └── ... Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if your wiki was located at <code><username>/www/wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. Next, you should upload this directory to your ULYSSIS account, to the original location of your wiki. If you followed step 2 correctly, the old files should be moved to a backup directory. As a result, after uploading, your ULYSSIS acocunt should contain the new files in something like <code><username>/www/wiki</code>, and the old files in <code><username>/www/wiki_backup</code>. Please refer to [[Accessing your files]] if you don't know how to upload files. Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. Although only you know exactly which files these are, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The <code>images/</code> directory, which contains all the uploaded files to the wiki, unless you have chosen a different upload directory. In that case, you should copy the different upload directory. * In case you use a custom logo, this file also needs to be restored from backup. This logo is stored in <code>resources/assets/</code> or <code>images/</code>, depending on what you chose to use. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any modifications made to the old installation files, extensions, or skins. For example, this includes miscellaneous modifications to the configuration of extensions or skins. * Any <code>.htaccess</code> file, if present. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == 8f26d69fc3a9b2eb35ded3864f295f2a5235a7ae 1317 1316 2021-04-25T19:48:19Z Yoa 30 /* Extracting the new files */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are very dense, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. With this out of the way, you can start the MediaWiki update process. == Downloading the latest version == Most likely, you arrived at this page after receiving an email from our [[Software Version Checker]]. This email might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the latest version. Of course, to update MediaWiki to this latest version, you will need to download the update. The MediaWiki downloads can be found [https://www.mediawiki.org/wiki/Download here]. Make sure to download the zip file for the latest version from the email and save it somewhere on your PC. == Making a backup == An important step in the update process is to create a backup of your data on the ULYSSIS server, to prevent data loss if something goes wrong. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. The backup step consists of roughly two parts: * Creating a backup of your wiki database. If you use MySQL or PostgreSQL, you can follow the instructions on [[Making Backups#A backup of your databases]]. If you use SQLite, please refer to [https://www.mediawiki.org/wiki/Manual:Upgrading#Back_up_existing_files_and_the_database the official instructions]. If you are not sure about your database type or the name of your wiki database, you can search the <code>LocalSettings.php</code> configuration file for the following lines: ## Database settings $wgDBtype = "<db_type>"; $wgDBserver = "<db_server>"; $wgDBname = "<db_name>"; $wgDBuser = "<user>"; $wgDBpassword = "<password>"; * Creating a backup of your wiki files. The easiest way to do this is to '''rename''' the directory containing your <code>LocalSettings.php</code> configuration file (your wiki location) to a new directory. For example, if <code>LocalSettings.php</code> is stored in <code><username>/www/wiki</code>, you should '''rename''' this directory to <code><username>/www/wiki_backup</code>, or something similar. == Extracting the new files == Now, you will need to extract the zip file you downloaded in step 1. This should result in a directory which looks something like: mediawiki-xxx/ ├── cache/ ├── docs/ ├── ... ├── api.php ├── autoload.php └── ... Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if your wiki was located at <code><username>/www/wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. Next, you should upload this directory to your ULYSSIS account, to the original location of your wiki. If you followed step 2 correctly, the old files should be moved to a backup directory. As a result, after uploading, your ULYSSIS acocunt should contain the new files in something like <code><username>/www/wiki</code>, and the old files in <code><username>/www/wiki_backup</code>. Please refer to [[Accessing your files]] if you don't know how to upload files. Because MediaWiki contains a lot of (small) files, this might take a long time, up to 30 minutes. Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. Although only you know exactly which files these are, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The <code>images/</code> directory, which contains all the uploaded files to the wiki, unless you have chosen a different upload directory. In that case, you should copy the different upload directory. * In case you use a custom logo, this file also needs to be restored from backup. This logo is stored in <code>resources/assets/</code> or <code>images/</code>, depending on what you chose to use. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any modifications made to the old installation files, extensions, or skins. For example, this includes miscellaneous modifications to the configuration of extensions or skins. * Any <code>.htaccess</code> file, if present. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == e9c5296ed6838fe5e48cd23a3bc43905efc65f6f 1318 1317 2021-04-25T20:08:16Z Yoa 30 D wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are very dense, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. With this out of the way, you can start the MediaWiki update process. == Downloading the latest version == Most likely, you arrived at this page after receiving an email from our [[Software Version Checker]]. This email might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the latest version. Of course, to update MediaWiki to this latest version, you will need to download the update. The MediaWiki downloads can be found [https://www.mediawiki.org/wiki/Download here]. Make sure to download the zip file for the latest version from the email and save it somewhere on your PC. == Making a backup == An important step in the update process is to create a backup of your data on the ULYSSIS server, to prevent data loss if something goes wrong. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. The backup step consists of roughly two parts: * Creating a backup of your wiki database. If you use MySQL or PostgreSQL, you can follow the instructions on [[Making Backups#A backup of your databases]]. If you use SQLite, please refer to [https://www.mediawiki.org/wiki/Manual:Upgrading#Back_up_existing_files_and_the_database the official instructions]. If you are not sure about your database type or the name of your wiki database, you can search the <code>LocalSettings.php</code> configuration file for the following lines: ## Database settings $wgDBtype = "<db_type>"; $wgDBserver = "<db_server>"; $wgDBname = "<db_name>"; $wgDBuser = "<user>"; $wgDBpassword = "<password>"; * Creating a backup of your wiki files. The easiest way to do this is to '''rename''' the directory containing your <code>LocalSettings.php</code> configuration file (your wiki location) to a new directory. For example, if <code>LocalSettings.php</code> is stored in <code><username>/www/wiki</code>, you should '''rename''' this directory to <code><username>/www/wiki_backup</code>, or something similar. == Extracting the new files == Now, you will need to extract the zip file you downloaded in step 1. This should result in a directory which looks something like: mediawiki-xxx/ ├── cache/ ├── docs/ ├── ... ├── api.php ├── autoload.php └── ... Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if your wiki was located at <code><username>/www/wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. Next, you should upload this directory to your ULYSSIS account, to the original location of your wiki. If you followed step 2 correctly, the old files should be moved to a backup directory. As a result, after uploading, your ULYSSIS acocunt should contain the new files in something like <code><username>/www/wiki</code>, and the old files in <code><username>/www/wiki_backup</code>. Please refer to [[Accessing your files]] if you don't know how to upload files. Because MediaWiki contains a lot of (small) files, this might take a long time, up to 30 minutes. Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. Although only you know exactly which files these are, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The <code>images/</code> directory, which contains all the uploaded files to the wiki, unless you have chosen a different upload directory. In that case, you should copy the different upload directory. * In case you use a custom logo, this file also needs to be restored from backup. This logo is stored in <code>resources/assets/</code> or <code>images/</code>, depending on what you chose to use. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any modifications made to the old installation files, extensions, or skins. For example, this includes miscellaneous modifications to the configuration of extensions or skins. * Any <code>.htaccess</code> file, if present. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. Unfortunately, this script must be executed using the command line. If you are not familiar with the command line or SSH, please read [[Accessing shell servers over SSH]] first. After connecting to your account using SSH, navigate to the directory containing your new wiki installation. For example, if your wiki is located at <code><username>/www/wiki</code>, execute: cd ~/www/wiki This directory should contain all your wiki files, such as <code>LocalSettings.php</code>. Now, navigate to the <code>maintenance/</code> directory: cd maintenance This directory contains the <code>update.php</code> file. To run this script, execute: php update.php The script will first display a 5 second countdown to execution, just in case you want to abort. After the countdown, you should not interrupt the execution of the script. If everything went well, you should see a lot of text, ended with: Done in x s. 75161865da4144625404f6de3554a4f662fb0b72 1319 1318 2021-04-25T20:08:26Z Yoa 30 /* Finalizing the update */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are very dense, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. With this out of the way, you can start the MediaWiki update process. == Downloading the latest version == Most likely, you arrived at this page after receiving an email from our [[Software Version Checker]]. This email might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the latest version. Of course, to update MediaWiki to this latest version, you will need to download the update. The MediaWiki downloads can be found [https://www.mediawiki.org/wiki/Download here]. Make sure to download the zip file for the latest version from the email and save it somewhere on your PC. == Making a backup == An important step in the update process is to create a backup of your data on the ULYSSIS server, to prevent data loss if something goes wrong. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. The backup step consists of roughly two parts: * Creating a backup of your wiki database. If you use MySQL or PostgreSQL, you can follow the instructions on [[Making Backups#A backup of your databases]]. If you use SQLite, please refer to [https://www.mediawiki.org/wiki/Manual:Upgrading#Back_up_existing_files_and_the_database the official instructions]. If you are not sure about your database type or the name of your wiki database, you can search the <code>LocalSettings.php</code> configuration file for the following lines: ## Database settings $wgDBtype = "<db_type>"; $wgDBserver = "<db_server>"; $wgDBname = "<db_name>"; $wgDBuser = "<user>"; $wgDBpassword = "<password>"; * Creating a backup of your wiki files. The easiest way to do this is to '''rename''' the directory containing your <code>LocalSettings.php</code> configuration file (your wiki location) to a new directory. For example, if <code>LocalSettings.php</code> is stored in <code><username>/www/wiki</code>, you should '''rename''' this directory to <code><username>/www/wiki_backup</code>, or something similar. == Extracting the new files == Now, you will need to extract the zip file you downloaded in step 1. This should result in a directory which looks something like: mediawiki-xxx/ ├── cache/ ├── docs/ ├── ... ├── api.php ├── autoload.php └── ... Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if your wiki was located at <code><username>/www/wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. Next, you should upload this directory to your ULYSSIS account, to the original location of your wiki. If you followed step 2 correctly, the old files should be moved to a backup directory. As a result, after uploading, your ULYSSIS acocunt should contain the new files in something like <code><username>/www/wiki</code>, and the old files in <code><username>/www/wiki_backup</code>. Please refer to [[Accessing your files]] if you don't know how to upload files. Because MediaWiki contains a lot of (small) files, this might take a long time, up to 30 minutes. Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. Although only you know exactly which files these are, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The <code>images/</code> directory, which contains all the uploaded files to the wiki, unless you have chosen a different upload directory. In that case, you should copy the different upload directory. * In case you use a custom logo, this file also needs to be restored from backup. This logo is stored in <code>resources/assets/</code> or <code>images/</code>, depending on what you chose to use. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any modifications made to the old installation files, extensions, or skins. For example, this includes miscellaneous modifications to the configuration of extensions or skins. * Any <code>.htaccess</code> file, if present. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. Unfortunately, this script must be executed using the command line. If you are not familiar with the command line or SSH, please read [[Accessing shell servers over SSH]] first. After connecting to your account using SSH, navigate to the directory containing your new wiki installation. For example, if your wiki is located at <code><username>/www/wiki</code>, execute: cd ~/www/wiki This directory should contain all your wiki files, such as <code>LocalSettings.php</code>. Now, navigate to the <code>maintenance/</code> directory: cd maintenance This directory contains the <code>update.php</code> file. To run this script, execute: php update.php The script will first display a 5 second countdown to execution, just in case you want to abort. After the countdown, you should not interrupt the execution of the script. If everything went well, you should see a lot of text, ending with: Done in x s. 9b9f946e89960dd18c6bd71ee62bc1b3342dca64 1320 1319 2021-04-25T20:11:05Z Yoa 30 /* Finalizing the update */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are very dense, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. With this out of the way, you can start the MediaWiki update process. == Downloading the latest version == Most likely, you arrived at this page after receiving an email from our [[Software Version Checker]]. This email might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the latest version. Of course, to update MediaWiki to this latest version, you will need to download the update. The MediaWiki downloads can be found [https://www.mediawiki.org/wiki/Download here]. Make sure to download the zip file for the latest version from the email and save it somewhere on your PC. == Making a backup == An important step in the update process is to create a backup of your data on the ULYSSIS server, to prevent data loss if something goes wrong. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. The backup step consists of roughly two parts: * Creating a backup of your wiki database. If you use MySQL or PostgreSQL, you can follow the instructions on [[Making Backups#A backup of your databases]]. If you use SQLite, please refer to [https://www.mediawiki.org/wiki/Manual:Upgrading#Back_up_existing_files_and_the_database the official instructions]. If you are not sure about your database type or the name of your wiki database, you can search the <code>LocalSettings.php</code> configuration file for the following lines: ## Database settings $wgDBtype = "<db_type>"; $wgDBserver = "<db_server>"; $wgDBname = "<db_name>"; $wgDBuser = "<user>"; $wgDBpassword = "<password>"; * Creating a backup of your wiki files. The easiest way to do this is to '''rename''' the directory containing your <code>LocalSettings.php</code> configuration file (your wiki location) to a new directory. For example, if <code>LocalSettings.php</code> is stored in <code><username>/www/wiki</code>, you should '''rename''' this directory to <code><username>/www/wiki_backup</code>, or something similar. == Extracting the new files == Now, you will need to extract the zip file you downloaded in step 1. This should result in a directory which looks something like: mediawiki-xxx/ ├── cache/ ├── docs/ ├── ... ├── api.php ├── autoload.php └── ... Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if your wiki was located at <code><username>/www/wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. Next, you should upload this directory to your ULYSSIS account, to the original location of your wiki. If you followed step 2 correctly, the old files should be moved to a backup directory. As a result, after uploading, your ULYSSIS acocunt should contain the new files in something like <code><username>/www/wiki</code>, and the old files in <code><username>/www/wiki_backup</code>. Please refer to [[Accessing your files]] if you don't know how to upload files. Because MediaWiki contains a lot of (small) files, this might take a long time, up to 30 minutes. Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. Although only you know exactly which files these are, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The <code>images/</code> directory, which contains all the uploaded files to the wiki, unless you have chosen a different upload directory. In that case, you should copy the different upload directory. * In case you use a custom logo, this file also needs to be restored from backup. This logo is stored in <code>resources/assets/</code> or <code>images/</code>, depending on what you chose to use. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any modifications made to the old installation files, extensions, or skins. For example, this includes miscellaneous modifications to the configuration of extensions or skins. * Any <code>.htaccess</code> file, if present. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. Unfortunately, this script must be executed using the command line. If you are not familiar with the command line or SSH, please read [[Accessing shell servers over SSH]] first. After connecting to your account using SSH, navigate to the directory containing your new wiki installation. For example, if your wiki is located at <code><username>/www/wiki</code>, execute: cd ~/www/wiki This directory should contain all your wiki files, such as <code>LocalSettings.php</code>. Now, navigate to the <code>maintenance/</code> directory: cd maintenance This directory contains the <code>update.php</code> file. To run this script, execute: php update.php The script will first display a 5 second countdown to execution, just in case you want to abort. After the countdown, you should not interrupt the execution of the script. If everything went well, you should see a lot of text, ending with: Done in x s. Congratulations! You successfully updated MediaWiki. If you did encounter any errors however, while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. 0ce580c308a4520d8361e1d96b648a28fd9e8a24 1321 1320 2021-04-25T20:36:08Z Yoa 30 /* Finalizing the update */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are very dense, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. With this out of the way, you can start the MediaWiki update process. == Downloading the latest version == Most likely, you arrived at this page after receiving an email from our [[Software Version Checker]]. This email might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the latest version. Of course, to update MediaWiki to this latest version, you will need to download the update. The MediaWiki downloads can be found [https://www.mediawiki.org/wiki/Download here]. Make sure to download the zip file for the latest version from the email and save it somewhere on your PC. == Making a backup == An important step in the update process is to create a backup of your data on the ULYSSIS server, to prevent data loss if something goes wrong. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. The backup step consists of roughly two parts: * Creating a backup of your wiki database. If you use MySQL or PostgreSQL, you can follow the instructions on [[Making Backups#A backup of your databases]]. If you use SQLite, please refer to [https://www.mediawiki.org/wiki/Manual:Upgrading#Back_up_existing_files_and_the_database the official instructions]. If you are not sure about your database type or the name of your wiki database, you can search the <code>LocalSettings.php</code> configuration file for the following lines: ## Database settings $wgDBtype = "<db_type>"; $wgDBserver = "<db_server>"; $wgDBname = "<db_name>"; $wgDBuser = "<user>"; $wgDBpassword = "<password>"; * Creating a backup of your wiki files. The easiest way to do this is to '''rename''' the directory containing your <code>LocalSettings.php</code> configuration file (your wiki location) to a new directory. For example, if <code>LocalSettings.php</code> is stored in <code><username>/www/wiki</code>, you should '''rename''' this directory to <code><username>/www/wiki_backup</code>, or something similar. == Extracting the new files == Now, you will need to extract the zip file you downloaded in step 1. This should result in a directory which looks something like: mediawiki-xxx/ ├── cache/ ├── docs/ ├── ... ├── api.php ├── autoload.php └── ... Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if your wiki was located at <code><username>/www/wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. Next, you should upload this directory to your ULYSSIS account, to the original location of your wiki. If you followed step 2 correctly, the old files should be moved to a backup directory. As a result, after uploading, your ULYSSIS acocunt should contain the new files in something like <code><username>/www/wiki</code>, and the old files in <code><username>/www/wiki_backup</code>. Please refer to [[Accessing your files]] if you don't know how to upload files. Because MediaWiki contains a lot of (small) files, this might take a long time, up to 30 minutes. Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. Although only you know exactly which files these are, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The <code>images/</code> directory, which contains all the uploaded files to the wiki, unless you have chosen a different upload directory. In that case, you should copy the different upload directory. * In case you use a custom logo, this file also needs to be restored from backup. This logo is stored in <code>resources/assets/</code> or <code>images/</code>, depending on what you chose to use. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any modifications made to the old installation files, extensions, or skins. For example, this includes miscellaneous modifications to the configuration of extensions or skins. * Any <code>.htaccess</code> file, if present. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. Unfortunately, this script must be executed using the command line. If you are not familiar with the command line or SSH, please read [[Accessing shell servers over SSH]] first. After connecting to your account using SSH, navigate to the directory containing your new wiki installation. For example, if your wiki is located at <code><username>/www/wiki</code>, execute: cd ~/www/wiki This directory should contain all your wiki files, such as <code>LocalSettings.php</code>. Now, navigate to the <code>maintenance/</code> directory: cd maintenance This directory contains the <code>update.php</code> file. To run this script, execute: php update.php The script will first display a 5 second countdown to execution, just in case you want to abort. After the countdown, you should not interrupt the execution of the script. If everything went well, you should see a lot of text, ending with: Done in x s. Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the backup installation: for example, if your backup is stored in <code><username>/www/wiki_backup</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing your files]]. If you did encounter any errors however, while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. 7b453b5e350e80ec98b039db5a293ba6490409f9 1322 1321 2021-04-25T20:36:31Z Yoa 30 /* Finalizing the update */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are very dense, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. With this out of the way, you can start the MediaWiki update process. == Downloading the latest version == Most likely, you arrived at this page after receiving an email from our [[Software Version Checker]]. This email might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the latest version. Of course, to update MediaWiki to this latest version, you will need to download the update. The MediaWiki downloads can be found [https://www.mediawiki.org/wiki/Download here]. Make sure to download the zip file for the latest version from the email and save it somewhere on your PC. == Making a backup == An important step in the update process is to create a backup of your data on the ULYSSIS server, to prevent data loss if something goes wrong. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. The backup step consists of roughly two parts: * Creating a backup of your wiki database. If you use MySQL or PostgreSQL, you can follow the instructions on [[Making Backups#A backup of your databases]]. If you use SQLite, please refer to [https://www.mediawiki.org/wiki/Manual:Upgrading#Back_up_existing_files_and_the_database the official instructions]. If you are not sure about your database type or the name of your wiki database, you can search the <code>LocalSettings.php</code> configuration file for the following lines: ## Database settings $wgDBtype = "<db_type>"; $wgDBserver = "<db_server>"; $wgDBname = "<db_name>"; $wgDBuser = "<user>"; $wgDBpassword = "<password>"; * Creating a backup of your wiki files. The easiest way to do this is to '''rename''' the directory containing your <code>LocalSettings.php</code> configuration file (your wiki location) to a new directory. For example, if <code>LocalSettings.php</code> is stored in <code><username>/www/wiki</code>, you should '''rename''' this directory to <code><username>/www/wiki_backup</code>, or something similar. == Extracting the new files == Now, you will need to extract the zip file you downloaded in step 1. This should result in a directory which looks something like: mediawiki-xxx/ ├── cache/ ├── docs/ ├── ... ├── api.php ├── autoload.php └── ... Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if your wiki was located at <code><username>/www/wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. Next, you should upload this directory to your ULYSSIS account, to the original location of your wiki. If you followed step 2 correctly, the old files should be moved to a backup directory. As a result, after uploading, your ULYSSIS acocunt should contain the new files in something like <code><username>/www/wiki</code>, and the old files in <code><username>/www/wiki_backup</code>. Please refer to [[Accessing your files]] if you don't know how to upload files. Because MediaWiki contains a lot of (small) files, this might take a long time, up to 30 minutes. Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. Although only you know exactly which files these are, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The <code>images/</code> directory, which contains all the uploaded files to the wiki, unless you have chosen a different upload directory. In that case, you should copy the different upload directory. * In case you use a custom logo, this file also needs to be restored from backup. This logo is stored in <code>resources/assets/</code> or <code>images/</code>, depending on what you chose to use. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any modifications made to the old installation files, extensions, or skins. For example, this includes miscellaneous modifications to the configuration of extensions or skins. * Any <code>.htaccess</code> file, if present. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. Unfortunately, this script must be executed using the command line. If you are not familiar with the command line or SSH, please read [[Accessing shell servers over SSH]] first. After connecting to your account using SSH, navigate to the directory containing your new wiki installation. For example, if your wiki is located at <code><username>/www/wiki</code>, execute: cd ~/www/wiki This directory should contain all your wiki files, such as <code>LocalSettings.php</code>. Now, navigate to the <code>maintenance/</code> directory: cd maintenance This directory contains the <code>update.php</code> file. To run this script, execute: php update.php The script will first display a 5 second countdown to execution, just in case you want to abort. After the countdown, you should not interrupt the execution of the script. If everything went well, you should see a lot of text, ending with: Done in x s. Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the backup installation: for example, if your backup is stored in <code><username>/www/wiki_backup</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. b9a8853983f43d747a65bb661ba719f4a579ab61 1323 1322 2021-04-26T12:32:24Z Yoa 30 wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are unnecessarily complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. If you arrived at this page after receiving an email from our [[Software Version Checker]]. This email might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to update to. However, if you already know where MediaWiki is installed, you can also just download the latest version from [https://www.mediawiki.org/wiki/Download the official page]. Make sure to download the zip file for the latest version from the email and save it somewhere on your PC. == Making a backup == An important step in the update process is to create a backup of your data on the ULYSSIS server, to prevent data loss if something goes wrong. The backup step consists of roughly two parts: * Creating a backup of your wiki database. If you use MySQL or PostgreSQL, you can follow the instructions on [[Making Backups#A backup of your databases]]. If you use SQLite, please refer to [https://www.mediawiki.org/wiki/Manual:Upgrading#Back_up_existing_files_and_the_database the official instructions]. If you are not sure about your database type or the name of your wiki database, you can search the <code>LocalSettings.php</code> configuration file for the following lines: ## Database settings $wgDBtype = "<db_type>"; $wgDBserver = "<db_server>"; $wgDBname = "<db_name>"; $wgDBuser = "<user>"; $wgDBpassword = "<password>"; * Creating a backup of your wiki files. The easiest way to do this is to '''rename''' the directory containing your <code>LocalSettings.php</code> configuration file (your wiki location) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_backup</code>, or something similar. == Installing the new files == Now, you will need to extract the zip file you downloaded in step 1. This should result in a directory which looks something like: mediawiki-xxx/ ├── cache/ ├── docs/ ├── ... ├── api.php ├── autoload.php └── ... Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if your wiki was located at <code>www/wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. Next, you should upload this directory to your ULYSSIS account, to the original location of your wiki. If you followed step 2 correctly, the old files should be moved to a backup directory. As a result, after uploading, your ULYSSIS acocunt should contain the new files in something like <code>www/wiki</code>, and the old files in <code>www/wiki_backup</code>. Please refer to [[Accessing your files]] if you don't know how to upload files. Because MediaWiki contains a lot of (small) files, this might take a long time, up to 30 minutes. Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. Although only you know exactly which files these are, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The <code>images/</code> directory, which contains all the uploaded files to the wiki, unless you have chosen a different upload directory. In that case, you should copy the different upload directory. * In case you use a custom logo, this file also needs to be restored from backup. This logo is stored in <code>resources/assets/</code> or <code>images/</code>, depending on what you chose to use. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any modifications made to the old installation files, extensions, or skins. For example, this includes miscellaneous modifications to the configuration of extensions or skins. * Any <code>.htaccess</code> file, if present. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. Unfortunately, this script must be executed using the command line. If you are not familiar with the command line or SSH, please read [[Accessing shell servers over SSH]] first. After connecting to your account using SSH, navigate to the directory containing your new wiki installation. For example, if your wiki is located at <code>www/wiki</code>, execute: cd ~/www/wiki This directory should contain all your wiki files, such as <code>LocalSettings.php</code>. Now, navigate to the <code>maintenance/</code> directory: cd maintenance This directory contains the <code>update.php</code> file. To run this script, execute: php update.php The script will first display a 5 second countdown to execution, just in case you want to abort. After the countdown, you should not interrupt the execution of the script. If everything went well, you should see a lot of text, ending with: Done in x s. Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the backup installation: for example, if your backup is stored in <code>www/wiki_backup</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. c565a428ab73fe454f5557aeec68ccb0f2eb1e6f 1324 1323 2021-04-26T12:38:58Z Yoa 30 /* Installing the new files */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are unnecessarily complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. If you arrived at this page after receiving an email from our [[Software Version Checker]]. This email might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to update to. However, if you already know where MediaWiki is installed, you can also just download the latest version from [https://www.mediawiki.org/wiki/Download the official page]. Make sure to download the zip file for the latest version from the email and save it somewhere on your PC. == Making a backup == An important step in the update process is to create a backup of your data on the ULYSSIS server, to prevent data loss if something goes wrong. The backup step consists of roughly two parts: * Creating a backup of your wiki database. If you use MySQL or PostgreSQL, you can follow the instructions on [[Making Backups#A backup of your databases]]. If you use SQLite, please refer to [https://www.mediawiki.org/wiki/Manual:Upgrading#Back_up_existing_files_and_the_database the official instructions]. If you are not sure about your database type or the name of your wiki database, you can search the <code>LocalSettings.php</code> configuration file for the following lines: ## Database settings $wgDBtype = "<db_type>"; $wgDBserver = "<db_server>"; $wgDBname = "<db_name>"; $wgDBuser = "<user>"; $wgDBpassword = "<password>"; * Creating a backup of your wiki files. The easiest way to do this is to '''rename''' the directory containing your <code>LocalSettings.php</code> configuration file (your wiki location) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_backup</code>, or something similar. == Installing the new files == Now, you will need to extract the zip file you downloaded in step 1. This should result in a directory which looks something like: mediawiki-xxx/ ├── cache/ ├── docs/ ├── ... ├── api.php ├── autoload.php └── ... Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if your wiki was located at <code>www/wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. Next, you should upload this directory to your ULYSSIS account, to the original location of your wiki. If you followed step 2 correctly, the old files should be moved to a backup directory. As a result, after uploading, your ULYSSIS acocunt should contain the new files in something like <code>www/wiki</code>, and the old files in <code>www/wiki_backup</code>. Please refer to [[Accessing your files]] if you don't know how to upload files. Because MediaWiki contains a lot of (small) files, this might take a long time, up to 15 minutes. Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. Although only you know exactly which files these are, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The <code>images/</code> directory, which contains all the uploaded files to the wiki, unless you have chosen a different upload directory. In that case, you should copy the different upload directory. * In case you use a custom logo, this file also needs to be restored from backup. This logo is stored in <code>resources/assets/</code> or <code>images/</code>, depending on what you chose to use. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any modifications made to the old installation files, extensions, or skins. For example, this includes miscellaneous modifications to the configuration of extensions or skins. * Any <code>.htaccess</code> file, if present. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. Unfortunately, this script must be executed using the command line. If you are not familiar with the command line or SSH, please read [[Accessing shell servers over SSH]] first. After connecting to your account using SSH, navigate to the directory containing your new wiki installation. For example, if your wiki is located at <code>www/wiki</code>, execute: cd ~/www/wiki This directory should contain all your wiki files, such as <code>LocalSettings.php</code>. Now, navigate to the <code>maintenance/</code> directory: cd maintenance This directory contains the <code>update.php</code> file. To run this script, execute: php update.php The script will first display a 5 second countdown to execution, just in case you want to abort. After the countdown, you should not interrupt the execution of the script. If everything went well, you should see a lot of text, ending with: Done in x s. Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the backup installation: for example, if your backup is stored in <code>www/wiki_backup</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. 76afe5cb09f324c1cf65cd4779f0086c9a49fb9e 1342 1324 2021-04-29T18:05:01Z Yoa 30 /* Installing the new files */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are unnecessarily complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. If you arrived at this page after receiving an email from our [[Software Version Checker]]. This email might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to update to. However, if you already know where MediaWiki is installed, you can also just download the latest version from [https://www.mediawiki.org/wiki/Download the official page]. Make sure to download the zip file for the latest version from the email and save it somewhere on your PC. == Making a backup == An important step in the update process is to create a backup of your data on the ULYSSIS server, to prevent data loss if something goes wrong. The backup step consists of roughly two parts: * Creating a backup of your wiki database. If you use MySQL or PostgreSQL, you can follow the instructions on [[Making Backups#A backup of your databases]]. If you use SQLite, please refer to [https://www.mediawiki.org/wiki/Manual:Upgrading#Back_up_existing_files_and_the_database the official instructions]. If you are not sure about your database type or the name of your wiki database, you can search the <code>LocalSettings.php</code> configuration file for the following lines: ## Database settings $wgDBtype = "<db_type>"; $wgDBserver = "<db_server>"; $wgDBname = "<db_name>"; $wgDBuser = "<user>"; $wgDBpassword = "<password>"; * Creating a backup of your wiki files. The easiest way to do this is to '''rename''' the directory containing your <code>LocalSettings.php</code> configuration file (your wiki location) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_backup</code>, or something similar. == Installing the new files == Now, you will need to extract the zip file you downloaded in step 1. This should result in a directory which looks something like: mediawiki-xxx/ ├── cache/ ├── docs/ ├── ... ├── api.php ├── autoload.php └── ... Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if your wiki was located at <code>www/wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. Next, you should upload this directory to your ULYSSIS account, to the original location of your wiki. If you followed step 2 correctly, the old files should be moved to a backup directory. As a result, after uploading, your ULYSSIS acocunt should contain the new files in something like <code>www/wiki</code>, and the old files in <code>www/wiki_backup</code>. Please refer to [[Accessing your files]] if you don't know how to upload files. Because MediaWiki contains a lot of (small) files, this might take a long time, up to 15 minutes. Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. Although only you know exactly which files these are, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * In case you use a custom logo or favicon, this file also needs to be restored from backup. You can find the locations of these files by checking the <code>$wgLogo</code> and <code>$wgFavicon</code> values in <code>LocalSettings.php</code>. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any modifications made to the old installation files, extensions, or skins. For example, this includes miscellaneous modifications to the configuration of extensions or skins. * Any <code>.htaccess</code> file, if present. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. Unfortunately, this script must be executed using the command line. If you are not familiar with the command line or SSH, please read [[Accessing shell servers over SSH]] first. After connecting to your account using SSH, navigate to the directory containing your new wiki installation. For example, if your wiki is located at <code>www/wiki</code>, execute: cd ~/www/wiki This directory should contain all your wiki files, such as <code>LocalSettings.php</code>. Now, navigate to the <code>maintenance/</code> directory: cd maintenance This directory contains the <code>update.php</code> file. To run this script, execute: php update.php The script will first display a 5 second countdown to execution, just in case you want to abort. After the countdown, you should not interrupt the execution of the script. If everything went well, you should see a lot of text, ending with: Done in x s. Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the backup installation: for example, if your backup is stored in <code>www/wiki_backup</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. b366bf294dd923ecbd374ce8ec91552c4e2d4e08 1343 1342 2021-04-29T18:10:49Z Yoa 30 wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. If you arrived at this page after receiving an email from our [[Software Version Checker]]. This email might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to update to. However, if you already know where MediaWiki is installed, you can also just download the latest version from [https://www.mediawiki.org/wiki/Download the official page]. Make sure to download the zip file for the latest version from the email and save it somewhere on your PC. == Making a backup == An important step in the update process is to create a backup of your data on the ULYSSIS server, to prevent data loss if something goes wrong. The backup step consists of roughly two parts: * Creating a backup of your wiki database. If you use MySQL or PostgreSQL, you can follow the instructions on [[Making Backups#A backup of your databases]]. If you use SQLite, please refer to [https://www.mediawiki.org/wiki/Manual:Upgrading#Back_up_existing_files_and_the_database the official instructions]. If you are not sure about your database type or the name of your wiki database, you can search the <code>LocalSettings.php</code> configuration file for the following lines: ## Database settings $wgDBtype = "<db_type>"; $wgDBserver = "<db_server>"; $wgDBname = "<db_name>"; $wgDBuser = "<user>"; $wgDBpassword = "<password>"; * Creating a backup of your wiki files. The easiest way to do this is to '''rename''' the directory containing your <code>LocalSettings.php</code> configuration file (your wiki location) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_backup</code>, or something similar. == Installing the new files == Now, you will need to extract the zip file you downloaded in step 1. This should result in a directory which looks something like: mediawiki-xxx/ ├── cache/ ├── docs/ ├── ... ├── api.php ├── autoload.php └── ... Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if your wiki was located at <code>www/wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. Next, you should upload this directory to your ULYSSIS account, to the original location of your wiki. If you followed step 2 correctly, the old files should be moved to a backup directory. As a result, after uploading, your ULYSSIS acocunt should contain the new files in something like <code>www/wiki</code>, and the old files in <code>www/wiki_backup</code>. Please refer to [[Accessing your files]] if you don't know how to upload files. Because MediaWiki contains a lot of (small) files, this might take a long time, up to 15 minutes. Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. Although only you know exactly which files these are, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * In case you use a custom logo or favicon, this file also needs to be restored from backup. You can find the locations of these files by checking the <code>$wgLogo</code> and <code>$wgFavicon</code> values in <code>LocalSettings.php</code>. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any modifications made to the old installation files, extensions, or skins. For example, this includes miscellaneous modifications to the configuration of extensions or skins. * Any <code>.htaccess</code> file, if present. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. Unfortunately, this script must be executed using the command line. If you are not familiar with the command line or SSH, please read [[Accessing shell servers over SSH]] first. After connecting to your account using SSH, navigate to the directory containing your new wiki installation. For example, if your wiki is located at <code>www/wiki</code>, execute: cd ~/www/wiki This directory should contain all your wiki files, such as <code>LocalSettings.php</code>. Now, navigate to the <code>maintenance/</code> directory: cd maintenance This directory contains the <code>update.php</code> file. To run this script, execute: php update.php The script will first display a 5 second countdown to execution, just in case you want to abort. After the countdown, you should not interrupt the execution of the script. If everything went well, you should see a lot of text, ending with: Done in x s. Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the backup installation: for example, if your backup is stored in <code>www/wiki_backup</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. f2bb994174ec284c8d1901218c018286b678c2f7 1344 1343 2021-05-01T22:04:58Z Yoa 30 /* Downloading the latest version */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. A table of all recent MediaWiki versions can be found on the [https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life the official page]. In this table, currently supported versions are in '''bold'''. If you arrived at this page after receiving an email from our [[Software Version Checker]]. This email might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our [[Software Version Checker]], you can simply choose any supported ('''bold''') version you want to update to. Click on the link of the newer version. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-xxx.tar.gz</code>. Download this file and save it somewhere on your PC. == Making a backup == An important step in the update process is to create a backup of your data on the ULYSSIS server, to prevent data loss if something goes wrong. The backup step consists of roughly two parts: * Creating a backup of your wiki database. If you use MySQL or PostgreSQL, you can follow the instructions on [[Making Backups#A backup of your databases]]. If you use SQLite, please refer to [https://www.mediawiki.org/wiki/Manual:Upgrading#Back_up_existing_files_and_the_database the official instructions]. If you are not sure about your database type or the name of your wiki database, you can search the <code>LocalSettings.php</code> configuration file for the following lines: ## Database settings $wgDBtype = "<db_type>"; $wgDBserver = "<db_server>"; $wgDBname = "<db_name>"; $wgDBuser = "<user>"; $wgDBpassword = "<password>"; * Creating a backup of your wiki files. The easiest way to do this is to '''rename''' the directory containing your <code>LocalSettings.php</code> configuration file (your wiki location) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_backup</code>, or something similar. == Installing the new files == Now, you will need to extract the zip file you downloaded in step 1. This should result in a directory which looks something like: mediawiki-xxx/ ├── cache/ ├── docs/ ├── ... ├── api.php ├── autoload.php └── ... Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if your wiki was located at <code>www/wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. Next, you should upload this directory to your ULYSSIS account, to the original location of your wiki. If you followed step 2 correctly, the old files should be moved to a backup directory. As a result, after uploading, your ULYSSIS acocunt should contain the new files in something like <code>www/wiki</code>, and the old files in <code>www/wiki_backup</code>. Please refer to [[Accessing your files]] if you don't know how to upload files. Because MediaWiki contains a lot of (small) files, this might take a long time, up to 15 minutes. Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. Although only you know exactly which files these are, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * In case you use a custom logo or favicon, this file also needs to be restored from backup. You can find the locations of these files by checking the <code>$wgLogo</code> and <code>$wgFavicon</code> values in <code>LocalSettings.php</code>. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any modifications made to the old installation files, extensions, or skins. For example, this includes miscellaneous modifications to the configuration of extensions or skins. * Any <code>.htaccess</code> file, if present. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. Unfortunately, this script must be executed using the command line. If you are not familiar with the command line or SSH, please read [[Accessing shell servers over SSH]] first. After connecting to your account using SSH, navigate to the directory containing your new wiki installation. For example, if your wiki is located at <code>www/wiki</code>, execute: cd ~/www/wiki This directory should contain all your wiki files, such as <code>LocalSettings.php</code>. Now, navigate to the <code>maintenance/</code> directory: cd maintenance This directory contains the <code>update.php</code> file. To run this script, execute: php update.php The script will first display a 5 second countdown to execution, just in case you want to abort. After the countdown, you should not interrupt the execution of the script. If everything went well, you should see a lot of text, ending with: Done in x s. Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the backup installation: for example, if your backup is stored in <code>www/wiki_backup</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. b7ba3c32a53c7491124bb1d40d9995755c041fcf 0 77 1325 729 2021-04-26T18:18:43Z Vincenttc 21 /* Adding the KU Leuven SMTP server in Thunderbird */ wikitext text/x-wiki You may want to send e-mail from Thunderbird using your @ulyssis.org-address, or another domain name that you use for your account. Thunderbird allows you to do this, but to configure this properly, you should not use your provider's SMTP server. They will add an extra header stating the original e-mail address the e-mail is sent from. Some e-mail clients show this information, which might be unwanted. The KU Leuven also provides an SMTP server which you can use as a student. It accepts e-mail originating from any e-mail adress, and can therefore be used for this purpose. It should be noted that this is an '''authenticated''' server, so any potential abuse can be tracked back to you. You should '''not''' use this for any malicious purpose. == Adding the KU Leuven SMTP server in Thunderbird == If you already have set up your KU Leuven e-mail in Thunderbird, you can skip this step and proceed to [[#Configure an identity for your e-mail account|Configure an identity for your e-mail account]] below. Go to your '''Account Settings''' (Edit > Account Settings or Tools > Account Settings, depending on your operating system). At the bottom of the left sidebar, you will find an entry named '''Outgoing Server (SMTP)'''. Click this to access your SMTP settings. In your SMTP settings, you should see a list of existing SMTP servers. We want to add a new entry, so click the '''Add...''' button. In the screen that pops up, fill in the settings as in the example screenshot below. Replace the displayed user name with your own student number. You will have to fill in the corresponding password on first use. [[File:Thunderbird-SMTPS.png]] == Configure an identity for your e-mail account == Back in the '''Account Settings''' screen, click on your e-mail address (not on any of its children). In the screen that opens, there will be a button '''Manage Identities...''' at the bottom. Click it. In the new screen, there will be one existing identity already: the default identity corresponding with your normal e-mail address. We want to add a new identity, so click the '''Add...''' button. In the screen that pops up, fill the name and e-mail address you wish to use. At the bottom, make sure you choose the SMTP server of your student account. This is shown in the image below. [[File:Thunderbird-Identity.png]] == Sending your first e-mail == When you compose a new e-mail, you can change the sender in the "From" field to the identity you just configured. If everything was installed correctly, Thunderbird will show you a pop-up to enter your KU Leuven password when you try to send the e-mail. In this pop-up, you can choose to save this password for later use. [[Category:Mail]] 34587add48adee5062db00e265afdf8979812811 0 13 1326 883 2021-04-26T18:53:35Z Vincenttc 21 /* Guest users */ wikitext text/x-wiki If you want to use [http://git-scm.com/ git] for version control to work privately on personal projects, or collaborate with others on projects, you can use GitLab for central repositories, and for tracking bugs. == Accessing GitLab == You can access our GitLab server at https://gitlab.ulyssis.org. You can log in with your standard ULYSSIS username and password. == Getting started with Git == If you want to get acquainted with git, these are good free resources: * [https://try.github.io Try Git]: an interactive introduction to git * [http://git-scm.com/book Pro Git]: a book that you can read for free online * [http://git-scm.com/docs The official Git reference documentation] == Guest users == If not everyone who works on your project has their own ULYSSIS account, you can request a Gitlab guest account via email. You simply send an email with the guest account's username (which will be prefixed with an underscore), full name, KU Leuven uid (m/s/r/u number) and email address to ulyssis@ulyssis.org and we will create it. Do keep in mind you bear full responsibility for all guests created for your account. [[Category:Versioning]] 9915a019f8a269d770ecdadc83f4d2ddaed20668 0 36 1328 1141 2021-04-26T19:03:29Z Vincenttc 21 wikitext text/x-wiki ULYSSIS doesn't support ftp, because it is insecure. However, we support sftp (ftp over ssh). This works similar as ssh. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. =Non-graphical methods= The most common way to transfer files is with a terminal by using the <code>scp</code> command. ==Copying file to host:== scp SourceFile user@host:directory/TargetFile If you want to copy an '''empty''' folder, you have to add -r, for example: scp -r SourceFolder user@host:directory/TargetFolder ==Copying file from host:== scp user@host:directory/SourceFile TargetFile If you want to copy an '''empty''' folder, you have to add -r, for example: scp -r user@host:directory/SourceFolder TargetFolder You don't need to use the full path to your file. You may you the relative path, starting from your home directory. For example: scp index.html user@ssh1.ulyssis.org:www/index.html You can find '''more info''' on the '''scp commands''' by using: man scp =Graphical methods= The graphical methods are explained in [[Accessing your files]]. [[Category:Files]] [[Category:Shell]] 23ad1ff05ed28b02a9a327ac9385d0412443cd9d 1329 1328 2021-04-26T19:03:59Z Vincenttc 21 wikitext text/x-wiki ULYSSIS doesn't support ftp, because it is insecure. However, we support sftp (ftp over ssh). This works similar as ssh. On the server, your files are located in <code>/home/group/username/</code>. For a normal user with username <code>username/</code> this will be <code>/home/user/username/</code>, for an organisation with username <code>organisation/</code> this will be <code>/home/org/organisation/</code> etc. ==Non-graphical methods== The most common way to transfer files is with a terminal by using the <code>scp</code> command. ===Copying file to host:=== scp SourceFile user@host:directory/TargetFile If you want to copy an '''empty''' folder, you have to add -r, for example: scp -r SourceFolder user@host:directory/TargetFolder ===Copying file from host:=== scp user@host:directory/SourceFile TargetFile If you want to copy an '''empty''' folder, you have to add -r, for example: scp -r user@host:directory/SourceFolder TargetFolder You don't need to use the full path to your file. You may you the relative path, starting from your home directory. For example: scp index.html user@ssh1.ulyssis.org:www/index.html You can find '''more info''' on the '''scp commands''' by using: man scp ==Graphical methods== The graphical methods are explained in [[Accessing your files]]. [[Category:Files]] [[Category:Shell]] 8cbcfff27468c5413a48b40c6a577cdc10c05441 0 15 1330 1214 2021-04-26T19:05:34Z Vincenttc 21 wikitext text/x-wiki You can transfer the account of your (faculty) organization to a new webmaster. The new webmaster must have a valid Central KU Leuven Login. Otherwise, the new webmaster will not be able to accept the account transfer. The instructions below must be executed by the current account owner. * Log in to [https://ucc.ulyssis.org/ UCC]. * Click 'Transfer account' in the menu on the right. * Enter the details of the new account owner. Ensure the KU Leuven email address is entered correctly. The new webmaster will receive an email to confirm the transfer. [[Category:Account]] c5ead73c75d0b0e9f6c21d51f496764200f94bd6 0 11 1331 1276 2021-04-26T19:08:28Z Vincenttc 21 wikitext text/x-wiki As described in [[Using your webspace|https://docs.ulyssis.org/Using_your_webspace]], you have your own ULYSSIS domain name that you can use. If you wish, you can also register another domain name. ULYSSIS isn't a domain name registrar, so you'll have to use an external registrar. For example, you can find a list of all registrars for .be at [http://dns.be dns.be]. {{notice|Caution!|Please don't configure your domain to use ns4.ulyssis.student.kuleuven.be, not only will it not work, it may result in unpredictable behaviour.}} If you have registered your own domain and you want to use it with your ULYSSIS account, you need to: # Point your domain name to the following ULYSSIS nameservers: #* ns.ulyssis.student.kuleuven.be #* ns3.ulyssis.student.kuleuven.be #* Optionally: ns2.ulyssis.student.kuleuven.be # Mail us at ulyssis@ulyssis.org, with the following details: #* Your ULYSSIS username #* The domain name you registered #* The directory that you want the domain to point at. This could be your <code>www</code> folder, but any other folder within your home directory is possible. #* Whether you want to receive e-mail at that domain name via ULYSSIS. Note that we need to request this with ICTS, so this will take a while. Please do keep in mind that, just like any change to an account, this can only be requested by the account holder. You can find more information about DNS at http://en.wikipedia.org/wiki/Domain_Name_System. [[Category:Webserver]] a33fc7191ca9515a82a394e05436cdd96579b17e 0 37 1332 1018 2021-04-27T08:56:31Z Bert 8 /* Restarting your application */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your framework and application. Just do a web search for "''framework'' mod_fcgid", where ''framework'' is the framework you're using, and you will find good instructions. There's a Django example below. You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <syntaxhighlight lang="apache">Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</syntaxhighlight> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. {{warning|Warning!|Do not place sensitive files inside the web accessible folder. Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.}} It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [[Managing_Cron_jobs | cronjob]] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than where it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> Or, for Python 3: <pre>virtualenv ~/.venv --python=python3</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <syntaxhighlight lang="python">#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </syntaxhighlight> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [https://flask.palletsprojects.com/en/1.1.x/deploying/fastcgi/ Flask documentation for FastCGI] [[Category:Webserver]] aa5cbf7ea7df48771b31354452c71ba5ce2ddab2 1333 1332 2021-04-27T10:01:50Z Bert 8 /* FastCGI */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your programming languae, framework or application. Just do a web search for "''keyword'' mod_fcgid", where ''keyword'' is the programming language, framework or application you're planning to use, and you will often find good instructions. We've included some examples below You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <syntaxhighlight lang="apache">Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</syntaxhighlight> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. {{warning|Warning!|Do not place sensitive files inside the web accessible folder. Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.}} It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [[Managing_Cron_jobs | cronjob]] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than where it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. ===Example: Django=== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> Or, for Python 3: <pre>virtualenv ~/.venv --python=python3</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <syntaxhighlight lang="python">#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </syntaxhighlight> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [https://flask.palletsprojects.com/en/1.1.x/deploying/fastcgi/ Flask documentation for FastCGI] [[Category:Webserver]] bc4378ae20f4f8148c6cc1528940d53d729dc1db 1334 1333 2021-04-27T10:14:30Z Bert 8 wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your programming languae, framework or application. Just do a web search for "''keyword'' mod_fcgid", where ''keyword'' is the programming language, framework or application you're planning to use, and you will often find good instructions. We've included some examples below You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <syntaxhighlight lang="apache">Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</syntaxhighlight> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. {{warning|Warning!|Do not place sensitive files inside the web accessible folder. Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.}} It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [[Managing_Cron_jobs | cronjob]] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than where it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. === Examples === ==== Python and Django ==== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [http://virtualenv.readthedocs.org/ virtualenv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>virtualenv ~/.venv</pre> Or, for Python 3: <pre>virtualenv ~/.venv --python=python3</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <syntaxhighlight lang="python">#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </syntaxhighlight> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [https://flask.palletsprojects.com/en/1.1.x/deploying/fastcgi/ Flask documentation for FastCGI] [[Category:Webserver]] 6306dcfb5c7a1a76afbd7e8781fa6e2ced93b966 1335 1334 2021-04-27T10:24:06Z Bert 8 /* Python and Django */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your programming languae, framework or application. Just do a web search for "''keyword'' mod_fcgid", where ''keyword'' is the programming language, framework or application you're planning to use, and you will often find good instructions. We've included some examples below You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <syntaxhighlight lang="apache">Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</syntaxhighlight> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. {{warning|Warning!|Do not place sensitive files inside the web accessible folder. Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.}} It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [[Managing_Cron_jobs | cronjob]] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than where it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. === Examples === ==== Python and Django ==== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a [https://docs.python.org/3/library/venv.html venv]. This tool is already preinstalled on our shell servers. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>python3 -m venv ~/.venv</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <syntaxhighlight lang="python">#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </syntaxhighlight> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [https://flask.palletsprojects.com/en/1.1.x/deploying/fastcgi/ Flask documentation for FastCGI] [[Category:Webserver]] 26de227a362ccf640ff31fe3af1c0d6bf4251b33 1336 1335 2021-04-27T10:25:02Z Bert 8 /* Python and Django */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your programming languae, framework or application. Just do a web search for "''keyword'' mod_fcgid", where ''keyword'' is the programming language, framework or application you're planning to use, and you will often find good instructions. We've included some examples below You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <syntaxhighlight lang="apache">Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</syntaxhighlight> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. {{warning|Warning!|Do not place sensitive files inside the web accessible folder. Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.}} It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [[Managing_Cron_jobs | cronjob]] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than where it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. === Examples === ==== Python and Django ==== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a virtual environment. You can use the following steps to get up and running with Django at ULYSSIS: <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>python3 -m venv ~/.venv</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <syntaxhighlight lang="python">#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </syntaxhighlight> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [https://flask.palletsprojects.com/en/1.1.x/deploying/fastcgi/ Flask documentation for FastCGI] [[Category:Webserver]] c540adc23347df4779cd6109dd0c05141fd584e3 1337 1336 2021-04-27T10:25:21Z Bert 8 /* Python and Django */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your programming languae, framework or application. Just do a web search for "''keyword'' mod_fcgid", where ''keyword'' is the programming language, framework or application you're planning to use, and you will often find good instructions. We've included some examples below You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <syntaxhighlight lang="apache">Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</syntaxhighlight> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. {{warning|Warning!|Do not place sensitive files inside the web accessible folder. Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.}} It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [[Managing_Cron_jobs | cronjob]] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than where it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. === Examples === ==== Python and Django ==== If you want to make a website using [https://www.djangoproject.com/ Django], we recommend that you use a virtual environment. You can use the following steps to get up and running with Django on your ULYSSIS hosting account. <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>python3 -m venv ~/.venv</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <syntaxhighlight lang="python">#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </syntaxhighlight> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [https://flask.palletsprojects.com/en/1.1.x/deploying/fastcgi/ Flask documentation for FastCGI] [[Category:Webserver]] 2b3a620edcb34d9f8ae2c2859f1a3a5b8be36c6b 1338 1337 2021-04-27T10:25:48Z Bert 8 /* Python and Django */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your programming languae, framework or application. Just do a web search for "''keyword'' mod_fcgid", where ''keyword'' is the programming language, framework or application you're planning to use, and you will often find good instructions. We've included some examples below You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <syntaxhighlight lang="apache">Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</syntaxhighlight> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. {{warning|Warning!|Do not place sensitive files inside the web accessible folder. Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.}} It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [[Managing_Cron_jobs | cronjob]] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than where it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. === Examples === ==== Python and Django ==== If you want to make a website using Python and [https://www.djangoproject.com/ Django], we recommend that you use a virtual environment. You can use the following steps to get up and running with Django on your ULYSSIS hosting account. <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>python3 -m venv ~/.venv</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <syntaxhighlight lang="python">#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </syntaxhighlight> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [https://flask.palletsprojects.com/en/1.1.x/deploying/fastcgi/ Flask documentation for FastCGI] [[Category:Webserver]] 8a72b48b06dae41d8de1091f26280af50a71e248 1339 1338 2021-04-27T15:50:59Z Bert 8 /* Examples */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your programming languae, framework or application. Just do a web search for "''keyword'' mod_fcgid", where ''keyword'' is the programming language, framework or application you're planning to use, and you will often find good instructions. We've included some examples below You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <syntaxhighlight lang="apache">Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</syntaxhighlight> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. {{warning|Warning!|Do not place sensitive files inside the web accessible folder. Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.}} It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [[Managing_Cron_jobs | cronjob]] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than where it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. === Examples === ==== Python and Django ==== If you want to make a website using Python and [https://www.djangoproject.com/ Django], we recommend that you use a virtual environment. You can use the following steps to get up and running with Django on your ULYSSIS hosting account. <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>python3 -m venv ~/.venv</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <syntaxhighlight lang="python">#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </syntaxhighlight> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [https://flask.palletsprojects.com/en/1.1.x/deploying/fastcgi/ Flask documentation for FastCGI] ==== Go ==== [[Category:Webserver]] 5f55251047d9a6e9fb38244bb7a7cf58f7b60561 1340 1339 2021-04-28T01:41:07Z Bert 8 /* Go */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <tt>.cgi</tt> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <tt>www</tt> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <tt>hello.cgi</tt>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your programming languae, framework or application. Just do a web search for "''keyword'' mod_fcgid", where ''keyword'' is the programming language, framework or application you're planning to use, and you will often find good instructions. We've included some examples below You'll want to treat this starter script as a <tt>mod_fcgid</tt> script, and usually, you'll want to redirect everything to this script, so you can use an <tt>.htaccess</tt> file that looks like this: <syntaxhighlight lang="apache">Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</syntaxhighlight> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <tt>.htaccess</tt> file. {{warning|Warning!|Do not place sensitive files inside the web accessible folder. Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.}} It is adviced to only place the fcgi starter script, <tt>.htaccess</tt> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [[Managing_Cron_jobs | cronjob]] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than where it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <tt>touch</tt>: <pre>touch starter.fcgi</pre> Replace ''starter.fcgi'' with the name of your starter script. === Examples === ==== Python and Django ==== If you want to make a website using Python and [https://www.djangoproject.com/ Django], we recommend that you use a virtual environment. You can use the following steps to get up and running with Django on your ULYSSIS hosting account. <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <tt>~/.venv</tt>, for example: <pre>python3 -m venv ~/.venv</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <tt>.htaccess</tt> file in your site's directory, e.g. the <tt>www</tt> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace ''user'' with org if you are an organization, and ''username'' with your ULYSSIS username): <syntaxhighlight lang="python">#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </syntaxhighlight> Call this script <tt>mysite.fcgi</tt>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [https://flask.palletsprojects.com/en/1.1.x/deploying/fastcgi/ Flask documentation for FastCGI] ==== Go ==== To make a website or web application in Go and host it on your ULYSSIS hosting account, you can use the standard library ''fcgi'' package. <ol> <li> [[Accessing shell servers over SSH|Log in to a shell server]]</li> <li> Put an .htaccess file in your site's directory (e.g. the www folder) with a reference to your executable. Here we've chosen mysite.fcgi, but you can adapt this to your liking. <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Write your code and compile the binary to mysite.fcgi. Below you can find a basic example of how to register two handlers (of which one is the fallback), then start the FastCGI client, and finally have a function (that's called as a goroutine) to check if the binary has been replaced so old processes don't stick around. <syntaxhighlight lang="go">package main import ( "fmt" "net/http" "net/http/fcgi" "os" "path/filepath" "time" ) func uri_interesting(w http.ResponseWriter, r *http.Request) { w.WriteHeader(http.StatusOK) fmt.Fprintln(w, "<h1>Oh, seems like this link isn't that interesting after all</h1>") fmt.Fprintln(w, "<p>Back to the <a href=\"/\">Homepage</a></p>") } func uri_default(w http.ResponseWriter, r *http.Request) { if r.URL.Path != "/" { w.WriteHeader(http.StatusNotFound) fmt.Fprintln(w, "<h1>This page doesn't exist</h1>") fmt.Fprintln(w, "<p>Back to the <a href=\"/\">Homepage</a></p>") } else { w.WriteHeader(http.StatusOK) fmt.Fprintln(w, "<h1>Welcome to this testwebsite!</h1>") fmt.Fprintln(w, "<p>This website is written in Go but doesn't really do much.") fmt.Fprintln(w, "Feel free to visit this <a href=\"/interesting/link\">Interesting link</a> or this <a href=\"/non-existent/link\">non-existent link</a>.</p>") } } func main() { go check_selfreplacement() http.HandleFunc("/interesting/link", uri_interesting) http.HandleFunc("/", uri_default) if err := fcgi.Serve(nil, nil); err != nil { panic(err) } } func check_selfreplacement() { fcgi_location, _ := os.Executable() fcgi_location, _ = filepath.EvalSymlinks(fcgi_location) start_stat, _ := os.Stat(fcgi_location) for { current_stat, _ := os.Stat(fcgi_location) if start_stat.ModTime() != current_stat.ModTime() { os.Exit(0) } time.Sleep(1 * time.Second) } } </syntaxhighlight> If you want to give this example a try, save it as mysite.fcgi.go and then use go build to compile it. </li> <li>Visit your website to verify everything works</li> </ol> [[Category:Webserver]] d6fb20acf7ada134a875a5248152093f89209c4e 1341 1340 2021-04-28T22:20:03Z Pcy 37 more uniform inline code snippet/keyword style, "that's called" -> "which is called" wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <code>.cgi</code> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <code>www</code> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <code>hello.cgi</code>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your programming languae, framework or application. Just do a web search for "''keyword'' mod_fcgid", where ''keyword'' is the programming language, framework or application you're planning to use, and you will often find good instructions. We've included some examples below You'll want to treat this starter script as a <code>mod_fcgid</code> script, and usually, you'll want to redirect everything to this script, so you can use an <code>.htaccess</code> file that looks like this: <syntaxhighlight lang="apache">Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</syntaxhighlight> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <code>.htaccess</code> file. {{warning|Warning!|Do not place sensitive files inside the web accessible folder. Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.}} It is adviced to only place the fcgi starter script, <code>.htaccess</code> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [[Managing_Cron_jobs | cronjob]] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than where it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django example below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <code>touch</code>: <pre>touch starter.fcgi</pre> Replace <code>starter.fcgi</code> with the name of your starter script. === Examples === ==== Python and Django ==== If you want to make a website using Python and [https://www.djangoproject.com/ Django], we recommend that you use a virtual environment. You can use the following steps to get up and running with Django on your ULYSSIS hosting account. <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <code>~/.venv</code>, for example: <pre>python3 -m venv ~/.venv</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <code>.htaccess</code> file in your site's directory, e.g. the <code>www</code> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace <code>user</code> with org if you are an organization, and <code>username</code> with your ULYSSIS username): <syntaxhighlight lang="python">#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </syntaxhighlight> Call this script <code>mysite.fcgi</code>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [https://flask.palletsprojects.com/en/1.1.x/deploying/fastcgi/ Flask documentation for FastCGI] ==== Go ==== To make a website or web application in Go and host it on your ULYSSIS hosting account, you can use the standard library ''fcgi'' package. <ol> <li> [[Accessing shell servers over SSH|Log in to a shell server]]</li> <li> Put an <code>.htaccess</code> file in your site's directory (e.g. the <code>www</code> folder) with a reference to your executable. Here we've chosen <code>mysite.fcgi</code>, but you can adapt this to your liking. <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Write your code, and compile the binary to <code>mysite.fcgi</code>. Below you can find a basic example of how to register two handlers (of which one is the fallback), then start the FastCGI client, and finally have a function (which is called as a goroutine) to check if the binary has been replaced so old processes don't stick around. <syntaxhighlight lang="go">package main import ( "fmt" "net/http" "net/http/fcgi" "os" "path/filepath" "time" ) func uri_interesting(w http.ResponseWriter, r *http.Request) { w.WriteHeader(http.StatusOK) fmt.Fprintln(w, "<h1>Oh, seems like this link isn't that interesting after all</h1>") fmt.Fprintln(w, "<p>Back to the <a href=\"/\">Homepage</a></p>") } func uri_default(w http.ResponseWriter, r *http.Request) { if r.URL.Path != "/" { w.WriteHeader(http.StatusNotFound) fmt.Fprintln(w, "<h1>This page doesn't exist</h1>") fmt.Fprintln(w, "<p>Back to the <a href=\"/\">Homepage</a></p>") } else { w.WriteHeader(http.StatusOK) fmt.Fprintln(w, "<h1>Welcome to this testwebsite!</h1>") fmt.Fprintln(w, "<p>This website is written in Go but doesn't really do much.") fmt.Fprintln(w, "Feel free to visit this <a href=\"/interesting/link\">Interesting link</a> or this <a href=\"/non-existent/link\">non-existent link</a>.</p>") } } func main() { go check_selfreplacement() http.HandleFunc("/interesting/link", uri_interesting) http.HandleFunc("/", uri_default) if err := fcgi.Serve(nil, nil); err != nil { panic(err) } } func check_selfreplacement() { fcgi_location, _ := os.Executable() fcgi_location, _ = filepath.EvalSymlinks(fcgi_location) start_stat, _ := os.Stat(fcgi_location) for { current_stat, _ := os.Stat(fcgi_location) if start_stat.ModTime() != current_stat.ModTime() { os.Exit(0) } time.Sleep(1 * time.Second) } } </syntaxhighlight> If you want to give this example a try, save it as <code>mysite.fcgi.go</code> and then use <code>go build</code> to compile it. </li> <li>Visit your website to verify everything works</li> </ol> [[Category:Webserver]] b79f298b58e1c67becac5b4c1004918458693a6f 0 176 1345 1344 2021-05-01T22:05:08Z Yoa 30 /* Downloading the latest version */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. A table of all recent MediaWiki versions can be found on the [https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life the official page]. In this table, currently supported versions are in '''bold'''. If you arrived at this page after receiving an email from our [[Software Version Checker]]. This email might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our [[Software Version Checker]], you can simply choose any supported ('''bold''') version you want to update to. Click on the link of the newer version. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-xxx.tar.gz</code>. Download this file and save it somewhere on your PC. == Making a backup == An important step in the update process is to create a backup of your data on the ULYSSIS server, to prevent data loss if something goes wrong. The backup step consists of roughly two parts: * Creating a backup of your wiki database. If you use MySQL or PostgreSQL, you can follow the instructions on [[Making Backups#A backup of your databases]]. If you use SQLite, please refer to [https://www.mediawiki.org/wiki/Manual:Upgrading#Back_up_existing_files_and_the_database the official instructions]. If you are not sure about your database type or the name of your wiki database, you can search the <code>LocalSettings.php</code> configuration file for the following lines: ## Database settings $wgDBtype = "<db_type>"; $wgDBserver = "<db_server>"; $wgDBname = "<db_name>"; $wgDBuser = "<user>"; $wgDBpassword = "<password>"; * Creating a backup of your wiki files. The easiest way to do this is to '''rename''' the directory containing your <code>LocalSettings.php</code> configuration file (your wiki location) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_backup</code>, or something similar. == Installing the new files == Now, you will need to extract the zip file you downloaded in step 1. This should result in a directory which looks something like: mediawiki-xxx/ ├── cache/ ├── docs/ ├── ... ├── api.php ├── autoload.php └── ... Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if your wiki was located at <code>www/wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. Next, you should upload this directory to your ULYSSIS account, to the original location of your wiki. If you followed step 2 correctly, the old files should be moved to a backup directory. As a result, after uploading, your ULYSSIS acocunt should contain the new files in something like <code>www/wiki</code>, and the old files in <code>www/wiki_backup</code>. Please refer to [[Accessing your files]] if you don't know how to upload files. Because MediaWiki contains a lot of (small) files, this might take a long time, up to 15 minutes. Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. Although only you know exactly which files these are, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * In case you use a custom logo or favicon, this file also needs to be restored from backup. You can find the locations of these files by checking the <code>$wgLogo</code> and <code>$wgFavicon</code> values in <code>LocalSettings.php</code>. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any modifications made to the old installation files, extensions, or skins. For example, this includes miscellaneous modifications to the configuration of extensions or skins. * Any <code>.htaccess</code> file, if present. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. Unfortunately, this script must be executed using the command line. If you are not familiar with the command line or SSH, please read [[Accessing shell servers over SSH]] first. After connecting to your account using SSH, navigate to the directory containing your new wiki installation. For example, if your wiki is located at <code>www/wiki</code>, execute: cd ~/www/wiki This directory should contain all your wiki files, such as <code>LocalSettings.php</code>. Now, navigate to the <code>maintenance/</code> directory: cd maintenance This directory contains the <code>update.php</code> file. To run this script, execute: php update.php The script will first display a 5 second countdown to execution, just in case you want to abort. After the countdown, you should not interrupt the execution of the script. If everything went well, you should see a lot of text, ending with: Done in x s. Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the backup installation: for example, if your backup is stored in <code>www/wiki_backup</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. 4e15bd3e17c8c7e4c6c36ed3692a54a88ee05ec3 1346 1345 2021-05-01T22:06:27Z Yoa 30 /* Downloading the latest version */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. A table of all recent MediaWiki versions can be found on the [https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life the official table]. In this table, currently supported versions are in '''bold'''. If you arrived at this page after receiving an email from our [[Software Version Checker]]. This email might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our [[Software Version Checker]], you can simply choose any supported ('''bold''') version from [https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life the table]. Click on the link of the newer version. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-xxx.tar.gz</code>. Download this file and save it somewhere on your PC. == Making a backup == An important step in the update process is to create a backup of your data on the ULYSSIS server, to prevent data loss if something goes wrong. The backup step consists of roughly two parts: * Creating a backup of your wiki database. If you use MySQL or PostgreSQL, you can follow the instructions on [[Making Backups#A backup of your databases]]. If you use SQLite, please refer to [https://www.mediawiki.org/wiki/Manual:Upgrading#Back_up_existing_files_and_the_database the official instructions]. If you are not sure about your database type or the name of your wiki database, you can search the <code>LocalSettings.php</code> configuration file for the following lines: ## Database settings $wgDBtype = "<db_type>"; $wgDBserver = "<db_server>"; $wgDBname = "<db_name>"; $wgDBuser = "<user>"; $wgDBpassword = "<password>"; * Creating a backup of your wiki files. The easiest way to do this is to '''rename''' the directory containing your <code>LocalSettings.php</code> configuration file (your wiki location) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_backup</code>, or something similar. == Installing the new files == Now, you will need to extract the zip file you downloaded in step 1. This should result in a directory which looks something like: mediawiki-xxx/ ├── cache/ ├── docs/ ├── ... ├── api.php ├── autoload.php └── ... Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if your wiki was located at <code>www/wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. Next, you should upload this directory to your ULYSSIS account, to the original location of your wiki. If you followed step 2 correctly, the old files should be moved to a backup directory. As a result, after uploading, your ULYSSIS acocunt should contain the new files in something like <code>www/wiki</code>, and the old files in <code>www/wiki_backup</code>. Please refer to [[Accessing your files]] if you don't know how to upload files. Because MediaWiki contains a lot of (small) files, this might take a long time, up to 15 minutes. Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. Although only you know exactly which files these are, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * In case you use a custom logo or favicon, this file also needs to be restored from backup. You can find the locations of these files by checking the <code>$wgLogo</code> and <code>$wgFavicon</code> values in <code>LocalSettings.php</code>. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any modifications made to the old installation files, extensions, or skins. For example, this includes miscellaneous modifications to the configuration of extensions or skins. * Any <code>.htaccess</code> file, if present. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. Unfortunately, this script must be executed using the command line. If you are not familiar with the command line or SSH, please read [[Accessing shell servers over SSH]] first. After connecting to your account using SSH, navigate to the directory containing your new wiki installation. For example, if your wiki is located at <code>www/wiki</code>, execute: cd ~/www/wiki This directory should contain all your wiki files, such as <code>LocalSettings.php</code>. Now, navigate to the <code>maintenance/</code> directory: cd maintenance This directory contains the <code>update.php</code> file. To run this script, execute: php update.php The script will first display a 5 second countdown to execution, just in case you want to abort. After the countdown, you should not interrupt the execution of the script. If everything went well, you should see a lot of text, ending with: Done in x s. Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the backup installation: for example, if your backup is stored in <code>www/wiki_backup</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. 0c87813825a9435421c233282f44a43c2f096b3b 1347 1346 2021-05-01T22:06:41Z Yoa 30 /* Downloading the latest version */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. A table of all recent MediaWiki versions can be found on the [https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life the official table]. In this table, currently supported versions are in '''bold'''. If you arrived at this page after receiving an email from our [[Software Version Checker]]. This email might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can simply choose any supported ('''bold''') version from [https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life the table]. Click on the link of the newer version. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-xxx.tar.gz</code>. Download this file and save it somewhere on your PC. == Making a backup == An important step in the update process is to create a backup of your data on the ULYSSIS server, to prevent data loss if something goes wrong. The backup step consists of roughly two parts: * Creating a backup of your wiki database. If you use MySQL or PostgreSQL, you can follow the instructions on [[Making Backups#A backup of your databases]]. If you use SQLite, please refer to [https://www.mediawiki.org/wiki/Manual:Upgrading#Back_up_existing_files_and_the_database the official instructions]. If you are not sure about your database type or the name of your wiki database, you can search the <code>LocalSettings.php</code> configuration file for the following lines: ## Database settings $wgDBtype = "<db_type>"; $wgDBserver = "<db_server>"; $wgDBname = "<db_name>"; $wgDBuser = "<user>"; $wgDBpassword = "<password>"; * Creating a backup of your wiki files. The easiest way to do this is to '''rename''' the directory containing your <code>LocalSettings.php</code> configuration file (your wiki location) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_backup</code>, or something similar. == Installing the new files == Now, you will need to extract the zip file you downloaded in step 1. This should result in a directory which looks something like: mediawiki-xxx/ ├── cache/ ├── docs/ ├── ... ├── api.php ├── autoload.php └── ... Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if your wiki was located at <code>www/wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. Next, you should upload this directory to your ULYSSIS account, to the original location of your wiki. If you followed step 2 correctly, the old files should be moved to a backup directory. As a result, after uploading, your ULYSSIS acocunt should contain the new files in something like <code>www/wiki</code>, and the old files in <code>www/wiki_backup</code>. Please refer to [[Accessing your files]] if you don't know how to upload files. Because MediaWiki contains a lot of (small) files, this might take a long time, up to 15 minutes. Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. Although only you know exactly which files these are, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * In case you use a custom logo or favicon, this file also needs to be restored from backup. You can find the locations of these files by checking the <code>$wgLogo</code> and <code>$wgFavicon</code> values in <code>LocalSettings.php</code>. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any modifications made to the old installation files, extensions, or skins. For example, this includes miscellaneous modifications to the configuration of extensions or skins. * Any <code>.htaccess</code> file, if present. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. Unfortunately, this script must be executed using the command line. If you are not familiar with the command line or SSH, please read [[Accessing shell servers over SSH]] first. After connecting to your account using SSH, navigate to the directory containing your new wiki installation. For example, if your wiki is located at <code>www/wiki</code>, execute: cd ~/www/wiki This directory should contain all your wiki files, such as <code>LocalSettings.php</code>. Now, navigate to the <code>maintenance/</code> directory: cd maintenance This directory contains the <code>update.php</code> file. To run this script, execute: php update.php The script will first display a 5 second countdown to execution, just in case you want to abort. After the countdown, you should not interrupt the execution of the script. If everything went well, you should see a lot of text, ending with: Done in x s. Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the backup installation: for example, if your backup is stored in <code>www/wiki_backup</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. 2a4505d7c531f4e18e4f26cc3a9d0b65d2f7519f 1349 1347 2021-05-01T22:11:22Z Yoa 30 /* Making a backup */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. A table of all recent MediaWiki versions can be found on the [https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life the official table]. In this table, currently supported versions are in '''bold'''. If you arrived at this page after receiving an email from our [[Software Version Checker]]. This email might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can simply choose any supported ('''bold''') version from [https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life the table]. Click on the link of the newer version. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-xxx.tar.gz</code>. Download this file and save it somewhere on your PC. == Making a backup == An important step in the update process is to create a backup of your data on the ULYSSIS server, to prevent data loss if something goes wrong. Additionally, this backup will be used to copy files from your old installation to the new installation. Consequently, '''this step is mandatory'''. The easiest way to create a backup is to '''rename''' the directory containing your <code>LocalSettings.php</code> configuration file (your wiki location) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_backup</code>, or something similar. [[File:Cyberduck rename.png|thumb|centre]] == Installing the new files == Now, you will need to extract the zip file you downloaded in step 1. This should result in a directory which looks something like: mediawiki-xxx/ ├── cache/ ├── docs/ ├── ... ├── api.php ├── autoload.php └── ... Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if your wiki was located at <code>www/wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. Next, you should upload this directory to your ULYSSIS account, to the original location of your wiki. If you followed step 2 correctly, the old files should be moved to a backup directory. As a result, after uploading, your ULYSSIS acocunt should contain the new files in something like <code>www/wiki</code>, and the old files in <code>www/wiki_backup</code>. Please refer to [[Accessing your files]] if you don't know how to upload files. Because MediaWiki contains a lot of (small) files, this might take a long time, up to 15 minutes. Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. Although only you know exactly which files these are, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * In case you use a custom logo or favicon, this file also needs to be restored from backup. You can find the locations of these files by checking the <code>$wgLogo</code> and <code>$wgFavicon</code> values in <code>LocalSettings.php</code>. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any modifications made to the old installation files, extensions, or skins. For example, this includes miscellaneous modifications to the configuration of extensions or skins. * Any <code>.htaccess</code> file, if present. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. Unfortunately, this script must be executed using the command line. If you are not familiar with the command line or SSH, please read [[Accessing shell servers over SSH]] first. After connecting to your account using SSH, navigate to the directory containing your new wiki installation. For example, if your wiki is located at <code>www/wiki</code>, execute: cd ~/www/wiki This directory should contain all your wiki files, such as <code>LocalSettings.php</code>. Now, navigate to the <code>maintenance/</code> directory: cd maintenance This directory contains the <code>update.php</code> file. To run this script, execute: php update.php The script will first display a 5 second countdown to execution, just in case you want to abort. After the countdown, you should not interrupt the execution of the script. If everything went well, you should see a lot of text, ending with: Done in x s. Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the backup installation: for example, if your backup is stored in <code>www/wiki_backup</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. aebc36045ec0d1fe746d5d512869390eced8287e 1350 1349 2021-05-01T22:13:13Z Yoa 30 /* Making a backup */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. A table of all recent MediaWiki versions can be found on the [https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life the official table]. In this table, currently supported versions are in '''bold'''. If you arrived at this page after receiving an email from our [[Software Version Checker]]. This email might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can simply choose any supported ('''bold''') version from [https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life the table]. Click on the link of the newer version. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-xxx.tar.gz</code>. Download this file and save it somewhere on your PC. == Making a backup == An important step in the update process is to create a backup of your data on the ULYSSIS server, to prevent data loss if something goes wrong. Additionally, this backup will be used to copy files from your old installation to the new installation. Consequently, '''this step is mandatory'''. The easiest way to create a backup is to '''rename''' the directory containing your <code>LocalSettings.php</code> configuration file (your wiki location) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_backup</code>, or something similar. [[File:Cyberduck rename.png|thumb|center]] == Installing the new files == Now, you will need to extract the zip file you downloaded in step 1. This should result in a directory which looks something like: mediawiki-xxx/ ├── cache/ ├── docs/ ├── ... ├── api.php ├── autoload.php └── ... Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if your wiki was located at <code>www/wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. Next, you should upload this directory to your ULYSSIS account, to the original location of your wiki. If you followed step 2 correctly, the old files should be moved to a backup directory. As a result, after uploading, your ULYSSIS acocunt should contain the new files in something like <code>www/wiki</code>, and the old files in <code>www/wiki_backup</code>. Please refer to [[Accessing your files]] if you don't know how to upload files. Because MediaWiki contains a lot of (small) files, this might take a long time, up to 15 minutes. Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. Although only you know exactly which files these are, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * In case you use a custom logo or favicon, this file also needs to be restored from backup. You can find the locations of these files by checking the <code>$wgLogo</code> and <code>$wgFavicon</code> values in <code>LocalSettings.php</code>. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any modifications made to the old installation files, extensions, or skins. For example, this includes miscellaneous modifications to the configuration of extensions or skins. * Any <code>.htaccess</code> file, if present. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. Unfortunately, this script must be executed using the command line. If you are not familiar with the command line or SSH, please read [[Accessing shell servers over SSH]] first. After connecting to your account using SSH, navigate to the directory containing your new wiki installation. For example, if your wiki is located at <code>www/wiki</code>, execute: cd ~/www/wiki This directory should contain all your wiki files, such as <code>LocalSettings.php</code>. Now, navigate to the <code>maintenance/</code> directory: cd maintenance This directory contains the <code>update.php</code> file. To run this script, execute: php update.php The script will first display a 5 second countdown to execution, just in case you want to abort. After the countdown, you should not interrupt the execution of the script. If everything went well, you should see a lot of text, ending with: Done in x s. Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the backup installation: for example, if your backup is stored in <code>www/wiki_backup</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. 2d98ad2805be13cfdc98fc435f58bfced659743f 1351 1350 2021-05-01T22:13:42Z Yoa 30 /* Making a backup */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. A table of all recent MediaWiki versions can be found on the [https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life the official table]. In this table, currently supported versions are in '''bold'''. If you arrived at this page after receiving an email from our [[Software Version Checker]]. This email might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can simply choose any supported ('''bold''') version from [https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life the table]. Click on the link of the newer version. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-xxx.tar.gz</code>. Download this file and save it somewhere on your PC. == Making a backup == An important step in the update process is to create a backup of your data on the ULYSSIS server, to prevent data loss if something goes wrong. Additionally, this backup will be used to copy files from your old installation to the new installation. Consequently, '''this step is mandatory'''. The easiest way to create a backup is to '''rename''' the directory containing your <code>LocalSettings.php</code> configuration file (your wiki location) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_backup</code>, or something similar. == Installing the new files == Now, you will need to extract the zip file you downloaded in step 1. This should result in a directory which looks something like: mediawiki-xxx/ ├── cache/ ├── docs/ ├── ... ├── api.php ├── autoload.php └── ... Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if your wiki was located at <code>www/wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. Next, you should upload this directory to your ULYSSIS account, to the original location of your wiki. If you followed step 2 correctly, the old files should be moved to a backup directory. As a result, after uploading, your ULYSSIS acocunt should contain the new files in something like <code>www/wiki</code>, and the old files in <code>www/wiki_backup</code>. Please refer to [[Accessing your files]] if you don't know how to upload files. Because MediaWiki contains a lot of (small) files, this might take a long time, up to 15 minutes. Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. Although only you know exactly which files these are, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * In case you use a custom logo or favicon, this file also needs to be restored from backup. You can find the locations of these files by checking the <code>$wgLogo</code> and <code>$wgFavicon</code> values in <code>LocalSettings.php</code>. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any modifications made to the old installation files, extensions, or skins. For example, this includes miscellaneous modifications to the configuration of extensions or skins. * Any <code>.htaccess</code> file, if present. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. Unfortunately, this script must be executed using the command line. If you are not familiar with the command line or SSH, please read [[Accessing shell servers over SSH]] first. After connecting to your account using SSH, navigate to the directory containing your new wiki installation. For example, if your wiki is located at <code>www/wiki</code>, execute: cd ~/www/wiki This directory should contain all your wiki files, such as <code>LocalSettings.php</code>. Now, navigate to the <code>maintenance/</code> directory: cd maintenance This directory contains the <code>update.php</code> file. To run this script, execute: php update.php The script will first display a 5 second countdown to execution, just in case you want to abort. After the countdown, you should not interrupt the execution of the script. If everything went well, you should see a lot of text, ending with: Done in x s. Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the backup installation: for example, if your backup is stored in <code>www/wiki_backup</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. 4b3bddcd5001b302bf067f9dd67aad0545fab316 1355 1351 2021-05-01T22:32:05Z Yoa 30 /* Installing the new files */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. A table of all recent MediaWiki versions can be found on the [https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life the official table]. In this table, currently supported versions are in '''bold'''. If you arrived at this page after receiving an email from our [[Software Version Checker]]. This email might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can simply choose any supported ('''bold''') version from [https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life the table]. Click on the link of the newer version. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-xxx.tar.gz</code>. Download this file and save it somewhere on your PC. == Making a backup == An important step in the update process is to create a backup of your data on the ULYSSIS server, to prevent data loss if something goes wrong. Additionally, this backup will be used to copy files from your old installation to the new installation. Consequently, '''this step is mandatory'''. The easiest way to create a backup is to '''rename''' the directory containing your <code>LocalSettings.php</code> configuration file (your wiki location) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_backup</code>, or something similar. == Installing the new files == Now, you will need to upload the <code>mediawiki-xxx.tar.gz</code> file you downloaded in step 1 to the same path as where your wiki backup directory is located. For example, if your wiki backup directory is located in <code>www/wiki_backup</code>, upload <code>mediawiki-xxx.tar.gz</code> to <code>www/</code>. After uploading, you can extract the file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the file and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-xxx</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * In case you use a custom logo or favicon, this file also needs to be restored from backup. You can find the locations of these files by checking the <code>$wgLogo</code> and <code>$wgFavicon</code> values in <code>LocalSettings.php</code>. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any modifications made to the old installation files, extensions, or skins. For example, this includes miscellaneous modifications to the configuration of extensions or skins. * Any <code>.htaccess</code> file, if present. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. Unfortunately, this script must be executed using the command line. If you are not familiar with the command line or SSH, please read [[Accessing shell servers over SSH]] first. After connecting to your account using SSH, navigate to the directory containing your new wiki installation. For example, if your wiki is located at <code>www/wiki</code>, execute: cd ~/www/wiki This directory should contain all your wiki files, such as <code>LocalSettings.php</code>. Now, navigate to the <code>maintenance/</code> directory: cd maintenance This directory contains the <code>update.php</code> file. To run this script, execute: php update.php The script will first display a 5 second countdown to execution, just in case you want to abort. After the countdown, you should not interrupt the execution of the script. If everything went well, you should see a lot of text, ending with: Done in x s. Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the backup installation: for example, if your backup is stored in <code>www/wiki_backup</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. c948919ddb93d3b45ae963512a6394352efbfccd 1356 1355 2021-05-01T22:34:24Z Yoa 30 /* Finalizing the update */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. A table of all recent MediaWiki versions can be found on the [https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life the official table]. In this table, currently supported versions are in '''bold'''. If you arrived at this page after receiving an email from our [[Software Version Checker]]. This email might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can simply choose any supported ('''bold''') version from [https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life the table]. Click on the link of the newer version. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-xxx.tar.gz</code>. Download this file and save it somewhere on your PC. == Making a backup == An important step in the update process is to create a backup of your data on the ULYSSIS server, to prevent data loss if something goes wrong. Additionally, this backup will be used to copy files from your old installation to the new installation. Consequently, '''this step is mandatory'''. The easiest way to create a backup is to '''rename''' the directory containing your <code>LocalSettings.php</code> configuration file (your wiki location) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_backup</code>, or something similar. == Installing the new files == Now, you will need to upload the <code>mediawiki-xxx.tar.gz</code> file you downloaded in step 1 to the same path as where your wiki backup directory is located. For example, if your wiki backup directory is located in <code>www/wiki_backup</code>, upload <code>mediawiki-xxx.tar.gz</code> to <code>www/</code>. After uploading, you can extract the file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the file and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-xxx</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * In case you use a custom logo or favicon, this file also needs to be restored from backup. You can find the locations of these files by checking the <code>$wgLogo</code> and <code>$wgFavicon</code> values in <code>LocalSettings.php</code>. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any modifications made to the old installation files, extensions, or skins. For example, this includes miscellaneous modifications to the configuration of extensions or skins. * Any <code>.htaccess</code> file, if present. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. This script can be executed using the Cyberduck "Send Command" feature. Unfortunately, this script must be executed using the command line. If you are not familiar with the command line or SSH, please read [[Accessing shell servers over SSH]] first. After connecting to your account using SSH, navigate to the directory containing your new wiki installation. For example, if your wiki is located at <code>www/wiki</code>, execute: cd ~/www/wiki This directory should contain all your wiki files, such as <code>LocalSettings.php</code>. Now, navigate to the <code>maintenance/</code> directory: cd maintenance This directory contains the <code>update.php</code> file. To run this script, execute: php update.php The script will first display a 5 second countdown to execution, just in case you want to abort. After the countdown, you should not interrupt the execution of the script. If everything went well, you should see a lot of text, ending with: Done in x s. Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the backup installation: for example, if your backup is stored in <code>www/wiki_backup</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. f87585ca208b7054bb9df3ae350a609dd3df9b04 1357 1356 2021-05-01T22:35:12Z Yoa 30 /* Installing the new files */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. A table of all recent MediaWiki versions can be found on the [https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life the official table]. In this table, currently supported versions are in '''bold'''. If you arrived at this page after receiving an email from our [[Software Version Checker]]. This email might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can simply choose any supported ('''bold''') version from [https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life the table]. Click on the link of the newer version. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-xxx.tar.gz</code>. Download this file and save it somewhere on your PC. == Making a backup == An important step in the update process is to create a backup of your data on the ULYSSIS server, to prevent data loss if something goes wrong. Additionally, this backup will be used to copy files from your old installation to the new installation. Consequently, '''this step is mandatory'''. The easiest way to create a backup is to '''rename''' the directory containing your <code>LocalSettings.php</code> configuration file (your wiki location) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_backup</code>, or something similar. == Installing the new files == Now, you will need to upload the <code>mediawiki-xxx.tar.gz</code> file you downloaded in step 1 to the same path as where your wiki backup directory is located. For example, if your wiki backup directory is located in <code>www/wiki_backup</code>, upload <code>mediawiki-xxx.tar.gz</code> to <code>www/</code>. After uploading, you can extract the file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the file and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-xxx</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Make sure to refresh after renaming by pressing the "Refresh button in Cyberduck the toolbar. Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * In case you use a custom logo or favicon, this file also needs to be restored from backup. You can find the locations of these files by checking the <code>$wgLogo</code> and <code>$wgFavicon</code> values in <code>LocalSettings.php</code>. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any modifications made to the old installation files, extensions, or skins. For example, this includes miscellaneous modifications to the configuration of extensions or skins. * Any <code>.htaccess</code> file, if present. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. This script can be executed using the Cyberduck "Send Command" feature. Unfortunately, this script must be executed using the command line. If you are not familiar with the command line or SSH, please read [[Accessing shell servers over SSH]] first. After connecting to your account using SSH, navigate to the directory containing your new wiki installation. For example, if your wiki is located at <code>www/wiki</code>, execute: cd ~/www/wiki This directory should contain all your wiki files, such as <code>LocalSettings.php</code>. Now, navigate to the <code>maintenance/</code> directory: cd maintenance This directory contains the <code>update.php</code> file. To run this script, execute: php update.php The script will first display a 5 second countdown to execution, just in case you want to abort. After the countdown, you should not interrupt the execution of the script. If everything went well, you should see a lot of text, ending with: Done in x s. Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the backup installation: for example, if your backup is stored in <code>www/wiki_backup</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. 4452f2b384c4f20def1d94944255360b6d5be581 1358 1357 2021-05-01T22:35:43Z Yoa 30 /* Installing the new files */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. A table of all recent MediaWiki versions can be found on the [https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life the official table]. In this table, currently supported versions are in '''bold'''. If you arrived at this page after receiving an email from our [[Software Version Checker]]. This email might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can simply choose any supported ('''bold''') version from [https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life the table]. Click on the link of the newer version. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-xxx.tar.gz</code>. Download this file and save it somewhere on your PC. == Making a backup == An important step in the update process is to create a backup of your data on the ULYSSIS server, to prevent data loss if something goes wrong. Additionally, this backup will be used to copy files from your old installation to the new installation. Consequently, '''this step is mandatory'''. The easiest way to create a backup is to '''rename''' the directory containing your <code>LocalSettings.php</code> configuration file (your wiki location) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_backup</code>, or something similar. == Installing the new files == Now, you will need to upload the <code>mediawiki-xxx.tar.gz</code> file you downloaded in step 1 to the same path as where your wiki backup directory is located. For example, if your wiki backup directory is located in <code>www/wiki_backup</code>, upload <code>mediawiki-xxx.tar.gz</code> to <code>www/</code>. After uploading, you can extract the file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the file and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-xxx</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Make sure to refresh after renaming by right clicking the directory and pressing "Refresh". Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * In case you use a custom logo or favicon, this file also needs to be restored from backup. You can find the locations of these files by checking the <code>$wgLogo</code> and <code>$wgFavicon</code> values in <code>LocalSettings.php</code>. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any modifications made to the old installation files, extensions, or skins. For example, this includes miscellaneous modifications to the configuration of extensions or skins. * Any <code>.htaccess</code> file, if present. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. This script can be executed using the Cyberduck "Send Command" feature. Unfortunately, this script must be executed using the command line. If you are not familiar with the command line or SSH, please read [[Accessing shell servers over SSH]] first. After connecting to your account using SSH, navigate to the directory containing your new wiki installation. For example, if your wiki is located at <code>www/wiki</code>, execute: cd ~/www/wiki This directory should contain all your wiki files, such as <code>LocalSettings.php</code>. Now, navigate to the <code>maintenance/</code> directory: cd maintenance This directory contains the <code>update.php</code> file. To run this script, execute: php update.php The script will first display a 5 second countdown to execution, just in case you want to abort. After the countdown, you should not interrupt the execution of the script. If everything went well, you should see a lot of text, ending with: Done in x s. Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the backup installation: for example, if your backup is stored in <code>www/wiki_backup</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. 0b87eeca157a283fec0e3f21a1108340ce54648e 1359 1358 2021-05-01T22:36:17Z Yoa 30 /* Making a backup */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. A table of all recent MediaWiki versions can be found on the [https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life the official table]. In this table, currently supported versions are in '''bold'''. If you arrived at this page after receiving an email from our [[Software Version Checker]]. This email might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can simply choose any supported ('''bold''') version from [https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life the table]. Click on the link of the newer version. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-xxx.tar.gz</code>. Download this file and save it somewhere on your PC. == Making a backup == An important step in the update process is to create a backup of your data on the ULYSSIS server, to prevent data loss if something goes wrong. Additionally, this backup will be used to copy files from your old installation to the new installation. Consequently, '''this step is mandatory'''. The easiest way to create a backup is to '''rename''' the directory containing your <code>LocalSettings.php</code> configuration file (your wiki location) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_backup</code>, or something similar. If you used Cyberduck to rename the directory, you should refresh it by right clicking the directory and pressing "Refresh". == Installing the new files == Now, you will need to upload the <code>mediawiki-xxx.tar.gz</code> file you downloaded in step 1 to the same path as where your wiki backup directory is located. For example, if your wiki backup directory is located in <code>www/wiki_backup</code>, upload <code>mediawiki-xxx.tar.gz</code> to <code>www/</code>. After uploading, you can extract the file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the file and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-xxx</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Make sure to refresh after renaming by right clicking the directory and pressing "Refresh". Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * In case you use a custom logo or favicon, this file also needs to be restored from backup. You can find the locations of these files by checking the <code>$wgLogo</code> and <code>$wgFavicon</code> values in <code>LocalSettings.php</code>. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any modifications made to the old installation files, extensions, or skins. For example, this includes miscellaneous modifications to the configuration of extensions or skins. * Any <code>.htaccess</code> file, if present. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. This script can be executed using the Cyberduck "Send Command" feature. Unfortunately, this script must be executed using the command line. If you are not familiar with the command line or SSH, please read [[Accessing shell servers over SSH]] first. After connecting to your account using SSH, navigate to the directory containing your new wiki installation. For example, if your wiki is located at <code>www/wiki</code>, execute: cd ~/www/wiki This directory should contain all your wiki files, such as <code>LocalSettings.php</code>. Now, navigate to the <code>maintenance/</code> directory: cd maintenance This directory contains the <code>update.php</code> file. To run this script, execute: php update.php The script will first display a 5 second countdown to execution, just in case you want to abort. After the countdown, you should not interrupt the execution of the script. If everything went well, you should see a lot of text, ending with: Done in x s. Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the backup installation: for example, if your backup is stored in <code>www/wiki_backup</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. bb15eec063ac5f2db7c1d8022c72ec92e118515e 1363 1359 2021-05-01T22:44:52Z Yoa 30 /* Finalizing the update */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. A table of all recent MediaWiki versions can be found on the [https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life the official table]. In this table, currently supported versions are in '''bold'''. If you arrived at this page after receiving an email from our [[Software Version Checker]]. This email might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can simply choose any supported ('''bold''') version from [https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life the table]. Click on the link of the newer version. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-xxx.tar.gz</code>. Download this file and save it somewhere on your PC. == Making a backup == An important step in the update process is to create a backup of your data on the ULYSSIS server, to prevent data loss if something goes wrong. Additionally, this backup will be used to copy files from your old installation to the new installation. Consequently, '''this step is mandatory'''. The easiest way to create a backup is to '''rename''' the directory containing your <code>LocalSettings.php</code> configuration file (your wiki location) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_backup</code>, or something similar. If you used Cyberduck to rename the directory, you should refresh it by right clicking the directory and pressing "Refresh". == Installing the new files == Now, you will need to upload the <code>mediawiki-xxx.tar.gz</code> file you downloaded in step 1 to the same path as where your wiki backup directory is located. For example, if your wiki backup directory is located in <code>www/wiki_backup</code>, upload <code>mediawiki-xxx.tar.gz</code> to <code>www/</code>. After uploading, you can extract the file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the file and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-xxx</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Make sure to refresh after renaming by right clicking the directory and pressing "Refresh". Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * In case you use a custom logo or favicon, this file also needs to be restored from backup. You can find the locations of these files by checking the <code>$wgLogo</code> and <code>$wgFavicon</code> values in <code>LocalSettings.php</code>. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any modifications made to the old installation files, extensions, or skins. For example, this includes miscellaneous modifications to the configuration of extensions or skins. * Any <code>.htaccess</code> file, if present. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box: php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the backup installation: for example, if your backup is stored in <code>www/wiki_backup</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. 15ddf364af34b59adc0d7d731b26c6f78d146a29 1372 1363 2021-05-06T22:59:10Z Yoa 30 /* Downloading the latest version */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. If you arrived at this page after receiving an email from our [[Software Version Checker]]. This email might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can find your current MediaWiki version by going to the <code>Special:Version#Installed_software</code> page on your wiki. For example, for this wiki, you can find the current version at [[Special:Version#Installed_software]]. A table of all recent MediaWiki versions can be found on the [https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life the official table]. In this table, currently supported versions are in '''bold'''. Click on the link of the version you want to download, either provided by the Software Version Checker, or a newer version compared to your current version. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-xxx.tar.gz</code>. Download this file and save it somewhere on your PC. == Making a backup == An important step in the update process is to create a backup of your data on the ULYSSIS server, to prevent data loss if something goes wrong. Additionally, this backup will be used to copy files from your old installation to the new installation. Consequently, '''this step is mandatory'''. The easiest way to create a backup is to '''rename''' the directory containing your <code>LocalSettings.php</code> configuration file (your wiki location) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_backup</code>, or something similar. If you used Cyberduck to rename the directory, you should refresh it by right clicking the directory and pressing "Refresh". == Installing the new files == Now, you will need to upload the <code>mediawiki-xxx.tar.gz</code> file you downloaded in step 1 to the same path as where your wiki backup directory is located. For example, if your wiki backup directory is located in <code>www/wiki_backup</code>, upload <code>mediawiki-xxx.tar.gz</code> to <code>www/</code>. After uploading, you can extract the file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the file and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-xxx</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Make sure to refresh after renaming by right clicking the directory and pressing "Refresh". Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * In case you use a custom logo or favicon, this file also needs to be restored from backup. You can find the locations of these files by checking the <code>$wgLogo</code> and <code>$wgFavicon</code> values in <code>LocalSettings.php</code>. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any modifications made to the old installation files, extensions, or skins. For example, this includes miscellaneous modifications to the configuration of extensions or skins. * Any <code>.htaccess</code> file, if present. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box: php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the backup installation: for example, if your backup is stored in <code>www/wiki_backup</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. 339cbb1253d57a556c7ddd86822025b1b8be7c07 1373 1372 2021-05-06T22:59:28Z Yoa 30 /* Downloading the latest version */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. If you arrived at this page after receiving an email from our [[Software Version Checker]]. This email might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can find your current MediaWiki version by going to the <code>Special:Version#Installed_software</code> page on your wiki. For example, for this wiki, you can find the current version at [[Special:Version#Installed_software]]. A table of all recent MediaWiki versions can be found on the [https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life the official table]. In this table, currently supported versions are in '''bold'''. Click on the link of the version you want to download, either provided by the Software Version Checker, or a newer version compared to your current version. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-xxx.tar.gz</code>. Download this file and save it somewhere on your PC. == Making a backup == An important step in the update process is to create a backup of your data on the ULYSSIS server, to prevent data loss if something goes wrong. Additionally, this backup will be used to copy files from your old installation to the new installation. Consequently, '''this step is mandatory'''. The easiest way to create a backup is to '''rename''' the directory containing your <code>LocalSettings.php</code> configuration file (your wiki location) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_backup</code>, or something similar. If you used Cyberduck to rename the directory, you should refresh it by right clicking the directory and pressing "Refresh". == Installing the new files == Now, you will need to upload the <code>mediawiki-xxx.tar.gz</code> file you downloaded in step 1 to the same path as where your wiki backup directory is located. For example, if your wiki backup directory is located in <code>www/wiki_backup</code>, upload <code>mediawiki-xxx.tar.gz</code> to <code>www/</code>. After uploading, you can extract the file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the file and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-xxx</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Make sure to refresh after renaming by right clicking the directory and pressing "Refresh". Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * In case you use a custom logo or favicon, this file also needs to be restored from backup. You can find the locations of these files by checking the <code>$wgLogo</code> and <code>$wgFavicon</code> values in <code>LocalSettings.php</code>. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any modifications made to the old installation files, extensions, or skins. For example, this includes miscellaneous modifications to the configuration of extensions or skins. * Any <code>.htaccess</code> file, if present. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box: php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the backup installation: for example, if your backup is stored in <code>www/wiki_backup</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. afcf57d529251eca19f34f07778ab674dcd16d4d 1374 1373 2021-05-06T23:02:37Z Yoa 30 /* Downloading the latest version */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. If you arrived at this page after receiving an email from our [[Software Version Checker]]. This email might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can find your current MediaWiki version by going to the <code>Special:Version#Installed_software</code> page on your wiki. For example, for this wiki, you can find the current version at [[Special:Version#Installed_software]]. A table of all recent MediaWiki versions can be found on the [https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life the official table]. In this table, currently supported versions are in '''bold'''. Click on the link of the version you need to download (if you need to choose a version, make sure to choose a supported, newer, preferably LTS version). This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-xxx.tar.gz</code>. Download this file and save it somewhere on your PC. == Making a backup == An important step in the update process is to create a backup of your data on the ULYSSIS server, to prevent data loss if something goes wrong. Additionally, this backup will be used to copy files from your old installation to the new installation. Consequently, '''this step is mandatory'''. The easiest way to create a backup is to '''rename''' the directory containing your <code>LocalSettings.php</code> configuration file (your wiki location) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_backup</code>, or something similar. If you used Cyberduck to rename the directory, you should refresh it by right clicking the directory and pressing "Refresh". == Installing the new files == Now, you will need to upload the <code>mediawiki-xxx.tar.gz</code> file you downloaded in step 1 to the same path as where your wiki backup directory is located. For example, if your wiki backup directory is located in <code>www/wiki_backup</code>, upload <code>mediawiki-xxx.tar.gz</code> to <code>www/</code>. After uploading, you can extract the file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the file and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-xxx</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Make sure to refresh after renaming by right clicking the directory and pressing "Refresh". Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * In case you use a custom logo or favicon, this file also needs to be restored from backup. You can find the locations of these files by checking the <code>$wgLogo</code> and <code>$wgFavicon</code> values in <code>LocalSettings.php</code>. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any modifications made to the old installation files, extensions, or skins. For example, this includes miscellaneous modifications to the configuration of extensions or skins. * Any <code>.htaccess</code> file, if present. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box: php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the backup installation: for example, if your backup is stored in <code>www/wiki_backup</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. 77e6f8faa62ed228e8ec651120185a385423d67e 1375 1374 2021-05-06T23:02:50Z Yoa 30 /* Downloading the latest version */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. If you arrived at this page after receiving an email from our [[Software Version Checker]]. This email might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can find your current MediaWiki version by going to the <code>Special:Version#Installed_software</code> page on your wiki. For example, for this wiki, you can find the current version at [[Special:Version#Installed_software]]. A table of all recent MediaWiki versions can be found on the [https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life the official table]. In this table, currently supported versions are in '''bold'''. Click on the link of the version you want to download (if you need to choose a version, make sure to choose a supported, newer, preferably LTS version). This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-xxx.tar.gz</code>. Download this file and save it somewhere on your PC. == Making a backup == An important step in the update process is to create a backup of your data on the ULYSSIS server, to prevent data loss if something goes wrong. Additionally, this backup will be used to copy files from your old installation to the new installation. Consequently, '''this step is mandatory'''. The easiest way to create a backup is to '''rename''' the directory containing your <code>LocalSettings.php</code> configuration file (your wiki location) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_backup</code>, or something similar. If you used Cyberduck to rename the directory, you should refresh it by right clicking the directory and pressing "Refresh". == Installing the new files == Now, you will need to upload the <code>mediawiki-xxx.tar.gz</code> file you downloaded in step 1 to the same path as where your wiki backup directory is located. For example, if your wiki backup directory is located in <code>www/wiki_backup</code>, upload <code>mediawiki-xxx.tar.gz</code> to <code>www/</code>. After uploading, you can extract the file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the file and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-xxx</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Make sure to refresh after renaming by right clicking the directory and pressing "Refresh". Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * In case you use a custom logo or favicon, this file also needs to be restored from backup. You can find the locations of these files by checking the <code>$wgLogo</code> and <code>$wgFavicon</code> values in <code>LocalSettings.php</code>. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any modifications made to the old installation files, extensions, or skins. For example, this includes miscellaneous modifications to the configuration of extensions or skins. * Any <code>.htaccess</code> file, if present. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box: php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the backup installation: for example, if your backup is stored in <code>www/wiki_backup</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. 6393ee000f8e11fcc562bc6e0567c0301299d3e6 6 177 1348 2021-05-01T22:10:50Z Yoa 30 wikitext text/x-wiki Cyberduck renaming 7e646c22c1d9a3f3f91bf76b42864d5a91edad0d 6 178 1352 2021-05-01T22:18:06Z Yoa 30 wikitext text/x-wiki Expanding archives using Cyberduck 077907dd20ef9f32b540263acda2edef39efa434 6 179 1353 2021-05-01T22:26:28Z Yoa 30 wikitext text/x-wiki Creating a new browser using Cyberduck 020c9a53738ba7d26f0c5953c7d3bfae3aec50a4 6 180 1354 2021-05-01T22:27:50Z Yoa 30 wikitext text/x-wiki Copying files or directories using drag-and-drop between browsers in Cyberduck 5d41ff7ca7d4b54d490af869e059668f415aef4b 6 181 1360 2021-05-01T22:37:24Z Yoa 30 wikitext text/x-wiki Sending an SSH command to a server using Cyberduck 599e257b8d5f7572f3ea8b408c5f388d621e89b5 6 182 1361 2021-05-01T22:40:02Z Yoa 30 wikitext text/x-wiki MediaWiki update command using Cyberduck c287b124abec96a59c45aaf92dd9a42a2c40f6a2 6 183 1362 2021-05-01T22:42:30Z Yoa 30 wikitext text/x-wiki MediaWiki update command using Cyberduck (output) fab8e0a1188805ec0a0b5675df03fa8e8ecba480 6 184 1364 2021-05-02T15:13:04Z Wtas 42 wikitext text/x-wiki New files and folders 38c5f6bdff4098b664bd9f7529e2b227b86257a8 1368 1364 2021-05-02T21:52:18Z Wtas 42 Wtas uploaded a new version of [[File:New-file-folder.png]] wikitext text/x-wiki New files and folders 38c5f6bdff4098b664bd9f7529e2b227b86257a8 6 185 1366 2021-05-02T21:46:17Z Wtas 42 wikitext text/x-wiki Delete something in Cyberduck 99c0c3b7dd7c989b76a522a7b38b7dcbf93551c6 6 186 1367 2021-05-02T21:48:28Z Wtas 42 wikitext text/x-wiki Delete in cyberduck e5480fdb1b4ddc0c8c01d4916860d95cd5ecfca8 1385 1367 2021-05-14T02:10:24Z Wtas 42 Wtas uploaded a new version of [[File:Delete-cyberduck-WB.png]] wikitext text/x-wiki Delete in cyberduck e5480fdb1b4ddc0c8c01d4916860d95cd5ecfca8 6 187 1369 2021-05-02T22:21:37Z Wtas 42 wikitext text/x-wiki Edit a file in cyberduck 5dae711ed6172bd11cc06052f58a601a31140ef1 1386 1369 2021-05-14T02:13:36Z Wtas 42 Wtas uploaded a new version of [[File:Edit.png]] wikitext text/x-wiki Edit a file in cyberduck 5dae711ed6172bd11cc06052f58a601a31140ef1 0 4 1378 877 2021-05-08T22:56:37Z Bert 8 wikitext text/x-wiki Users can access the ULYSSIS servers through two machines: <code>ssh1.ulyssis.org</code> and <code>ssh2.ulyssis.org</code>. Both of them run Linux. You can run commands on these servers or use them to access the files on your ULYSSIS account. The servers can only be accessed trough SSH, not through FTP or any other protocol. ==Running commands== To run a command on the shell servers, you will need to connect to them using a terminal. Our servers do not support a full graphical interface. ===Linux=== On Linux, you can just open a terminal and connect to the servers by using one of the following commands (with <code>username</code> your username): ssh username@ssh1.ulyssis.org ssh username@ssh2.ulyssis.org Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. ===Windows=== Windows doesn't support native terminals, so you will have to download a program first. A good option is [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty], which is completely free and doesn't require any installation. Just download it and run the .exe file. The parameters: *Host name: ssh1.ulyssis.org or ssh2.ulyssis.org *Protocol: SSH *Port: 22 (should be set automatically) You can save these options for later on. Next, you will be asked to give your password. Doing all this will open a terminal to the remote server which can be used the same way as a Linux terminal. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. More information about Putty can be found at http://the.earth.li/~sgtatham/putty/0.60/htmldoc/. ===Mac=== On Mac, you can just open Terminal. This application can be found in the Utilities folder within your Application folder. If you don't find it there, you can use Spotlight to find it. You can now connect to the servers by using one of the following commands (with <code>username</code> your username): ssh username@ssh1.ulyssis.org ssh username@ssh2.ulyssis.org Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use ctrl+D. ===Useful ideas=== Here are some useful ideas about what you could do with your shell server access: *[[Accessing your files]] *[[Fetch your KU Leuven email into another email address]] *[[ULYSSIS public IRC]] ===Useful commands=== Some useful commands can be found [[Useful Linux Commands|here]]. [[Category:Shell]] e73d93694f62e0cad4668bb7fcb54cc7301b9ef1 6 173 1380 1311 2021-05-14T01:44:07Z Wtas 42 Wtas uploaded a new version of [[File:Open-connection-WB.png]] wikitext text/x-wiki open a connection dialog 5abebaf710d916aa5bc5e1c889725c1b6fe434c9 6 170 1381 1308 2021-05-14T01:45:01Z Wtas 42 Wtas uploaded a new version of [[File:Fingerprint dialog window.png]] wikitext text/x-wiki dialog window asking to trust a fingerpint dbd085bb3a20dff9e3c7407aca5cbc44074ec7fe 6 165 1382 1259 2021-05-14T01:47:59Z Wtas 42 Wtas uploaded a new version of [[File:Cyberduck connection interface.png]] wikitext text/x-wiki Connection interface for Cyberduck 6997bfd247525db1ad8fa68bf272f862a8e8f24e 6 171 1383 1309 2021-05-14T01:52:03Z Wtas 42 Wtas uploaded a new version of [[File:Cyberduck-upload-button.png]] wikitext text/x-wiki upload button for Cyberduck f2adff796d2d0dc27a51c77b98535f456e42da8a 6 175 1384 1313 2021-05-14T02:03:29Z Wtas 42 Wtas uploaded a new version of [[File:Navigating-WB.png]] wikitext text/x-wiki Navigating in Cyberduck 0dbedf98422e398de542e68b9b4805efa175a3c4 1406 1384 2021-07-02T23:17:49Z Wtas 42 Wtas uploaded a new version of [[File:Navigating-WB.png]] wikitext text/x-wiki Navigating in Cyberduck 0dbedf98422e398de542e68b9b4805efa175a3c4 6 172 1388 1310 2021-05-14T14:29:38Z Wtas 42 Wtas uploaded a new version of [[File:Upload-drag-WB.png]] wikitext text/x-wiki picture to explain dragging a file to upload it 07b81319ea1775d6a5dfc481f5d5c518e9596c85 1393 1388 2021-05-16T20:32:29Z Wtas 42 Wtas uploaded a new version of [[File:Upload-drag-WB.png]] wikitext text/x-wiki picture to explain dragging a file to upload it 07b81319ea1775d6a5dfc481f5d5c518e9596c85 0 43 1391 1007 2021-05-15T14:15:11Z Bert 8 wikitext text/x-wiki You may want to receive e-mail from ulyssis on another email provider. It is very easy to set this up. == Change the forwarders for your @ulyssis.org email address == # Go to ucc.ulyssis.org and log in with your username and password. # On the right side, click on '''Mail'''. # Under '''Address forward''' you can change the forward address of your ULYSSIS mail by clicking on '''edit'''. # Choose '''forward''' and enter the email address you want to forward your ULYSSIS mail to and save the changes. # If you forward to Gmail, Hotmail. or use Thunderbird, we recommend looking at [[Using a forwarder as an alias]] so you can send mails under the forwarding address instead of just your own. == Change the forwarders for other domains == # Go to ucc.ulyssis.org and log in with your username and password. # On the right side, click on '''Mail'''. [[File:Forwarder Step1.png|left|alt=|thumb|700px]] 3. Under '''Virtual Domains''', click on the domain you want to change. [[File:Forwarder Step2.png|left|alt=|thumb|700px]] 4. You can change a forwarder by clicking on '''edit''' or on '''Add alias''' and add the forwarders you want. [[File:Forwarder Step3.png|left|alt=|thumb|700px]] 5. Save your changes == Use your mailbox and forwarders at the same time == An alternative way to set the forwarders, that will also allow you to use your mailbox and the webinterface, is to use a .forward file. On each line of this file, you can specify to wich addresses you want to forward the email. If one of the addresses is the same as your @ulyssis address, then the mail will also be placed in your ULYSSIS mailbox. In the following example, your @ulyssis email address is <code>user@ulyssis.org</code>. Example .forward file: user@ulyssis.org example@gmail.com example2@skynet.be This will place the email in your ULYSSIS mailbox so that you can access it from the webinterface or your local mailclient. It will also forward the mail to <code>example@gmail.com</code> and <code>example2@skynet.be</code>. To use this, place a .forward file with the prefered email addresses in your homedir, see [[Accessing your files]], and set your forwarder to 'Inbox' in https://ucc.ulyssis.org/mail [[Category:Mail]] be42c46ecc38fb2a0a80c80a5f518a97cb6c8b69 1400 1391 2021-05-30T21:49:08Z Vincenttc 21 wikitext text/x-wiki You may want to receive e-mail from ULYSSIS on another email provider. It is very easy to set this up. == Change the forwarders for your @ulyssis.org email address == # Go to [https://ucc.ulyssis.org UCC] and log in with your username and password. # On the right side, click on '''Mail'''. # Under '''Address forward''' you can change the forward address of your ULYSSIS mail by clicking on '''edit'''. # Choose '''forward''' and enter the email address you want to forward your ULYSSIS mail to and save the changes. # If you forward to Gmail, Hotmail. or use Thunderbird, we recommend looking at [[Using a forwarder as an alias]] so you can send mails under the forwarding address instead of just your own. == Change the forwarders for other domains == # Go to [https://ucc.ulyssis.org UCC] and log in with your username and password. # On the right side, click on '''Mail'''. [[File:Forwarder Step1.png|left|alt=|thumb|700px]] 3. Under '''Virtual Domains''', click on the domain you want to change. [[File:Forwarder Step2.png|left|alt=|thumb|700px]] 4. You can change a forwarder by clicking on '''edit''' or on '''Add alias''' and add the forwarders you want. [[File:Forwarder Step3.png|left|alt=|thumb|700px]] 5. Save your changes == Use your mailbox and forwarders at the same time == An alternative way to set the forwarders, that will also allow you to use your mailbox and the webinterface, is to use a .forward file. On each line of this file, you can specify to wich addresses you want to forward the email. If one of the addresses is the same as your @ulyssis address, then the mail will also be placed in your ULYSSIS mailbox. In the following example, your @ulyssis email address is <code>user@ulyssis.org</code>. Example .forward file: user@ulyssis.org example@gmail.com example2@skynet.be This will place the email in your ULYSSIS mailbox so that you can access it from the webinterface or your local mailclient. It will also forward the mail to <code>example@gmail.com</code> and <code>example2@skynet.be</code>. To use this, place a .forward file with the prefered email addresses in your homedir, see [[Accessing your files]], and set your forwarder to 'Inbox' in https://ucc.ulyssis.org/mail [[Category:Mail]] fe3aca3b640975ea7d679c3b3a6c654e59b2cdb1 1401 1400 2021-05-30T21:58:20Z Vincenttc 21 /* Use your mailbox and forwarders at the same time */ wikitext text/x-wiki You may want to receive e-mail from ULYSSIS on another email provider. It is very easy to set this up. == Change the forwarders for your @ulyssis.org email address == # Go to [https://ucc.ulyssis.org UCC] and log in with your username and password. # On the right side, click on '''Mail'''. # Under '''Address forward''' you can change the forward address of your ULYSSIS mail by clicking on '''edit'''. # Choose '''forward''' and enter the email address you want to forward your ULYSSIS mail to and save the changes. # If you forward to Gmail, Hotmail. or use Thunderbird, we recommend looking at [[Using a forwarder as an alias]] so you can send mails under the forwarding address instead of just your own. == Change the forwarders for other domains == # Go to [https://ucc.ulyssis.org UCC] and log in with your username and password. # On the right side, click on '''Mail'''. [[File:Forwarder Step1.png|left|alt=|thumb|700px]] 3. Under '''Virtual Domains''', click on the domain you want to change. [[File:Forwarder Step2.png|left|alt=|thumb|700px]] 4. You can change a forwarder by clicking on '''edit''' or on '''Add alias''' and add the forwarders you want. [[File:Forwarder Step3.png|left|alt=|thumb|700px]] 5. Save your changes [[Category:Mail]] 146f4b552a02b8f2ce4b6644b03188b939b66cab 1402 1401 2021-05-30T22:06:57Z Vincenttc 21 /* Change the forwarders for your @ulyssis.org email address */ wikitext text/x-wiki You may want to receive e-mail from ULYSSIS on another email provider. It is very easy to set this up. == Change the forwarders for your @ulyssis.org email address == # Go to [https://ucc.ulyssis.org UCC] and log in with your username and password. # On the right side, click on '''Mail'''. # Under '''Address forward''' you can change the forward address of your ULYSSIS mail by clicking on '''edit'''. # Choose '''forward''' and enter the email address(es) you want to forward your ULYSSIS mail to and save the changes. # If you forward to Gmail, Hotmail. or use Thunderbird, we recommend looking at [[Using a forwarder as an alias]] so you can send mails under the forwarding address instead of just your own. If you want to forward emails received on your @ulyssis.org email address to other addresses as well as have them be delivered in your [[mailbox]], you can add ''username''@ulyssis.org to the forwarders list. This will ensure that the email is delivered to your mailbox as if the destination was set to '''Inbox''' while still forwarding to the other addresses. == Change the forwarders for other domains == # Go to [https://ucc.ulyssis.org UCC] and log in with your username and password. # On the right side, click on '''Mail'''. [[File:Forwarder Step1.png|left|alt=|thumb|700px]] 3. Under '''Virtual Domains''', click on the domain you want to change. [[File:Forwarder Step2.png|left|alt=|thumb|700px]] 4. You can change a forwarder by clicking on '''edit''' or on '''Add alias''' and add the forwarders you want. [[File:Forwarder Step3.png|left|alt=|thumb|700px]] 5. Save your changes [[Category:Mail]] 52d4c5801a4b97089ab5a55d8f7a9124afbd8fbe 1403 1402 2021-05-30T22:10:03Z Vincenttc 21 /* Change the forwarders for your @ulyssis.org email address */ wikitext text/x-wiki You may want to receive e-mail from ULYSSIS on another email provider. It is very easy to set this up. == Change the forwarders for your @ulyssis.org email address == # Go to [https://ucc.ulyssis.org UCC] and log in with your username and password. # On the right side, click on '''Mail'''. # Under '''Address forward''' you can change the forward address of your ULYSSIS mail by clicking on '''edit'''. # Choose '''forward''' and enter the email address(es) you want to forward your ULYSSIS mail to and save the changes. # If you forward to Gmail, Hotmail. or use Thunderbird, we recommend looking at [[Using a forwarder as an alias]] so you can send mails under the forwarding address instead of just your own. If you want to forward emails received on your @ulyssis.org email address to other addresses as well as have them delivered in your [[mailbox]], you can add ''username''@ulyssis.org to the forwarders list. This will ensure that the email is delivered to your mailbox as if the destination was set to '''Inbox''', while emails are still forwarded to the other addresses. == Change the forwarders for other domains == # Go to [https://ucc.ulyssis.org UCC] and log in with your username and password. # On the right side, click on '''Mail'''. [[File:Forwarder Step1.png|left|alt=|thumb|700px]] 3. Under '''Virtual Domains''', click on the domain you want to change. [[File:Forwarder Step2.png|left|alt=|thumb|700px]] 4. You can change a forwarder by clicking on '''edit''' or on '''Add alias''' and add the forwarders you want. [[File:Forwarder Step3.png|left|alt=|thumb|700px]] 5. Save your changes [[Category:Mail]] 47cf0454b6e52ca4e4db293de4933c6f22ce5db9 0 98 1392 1301 2021-05-15T14:20:02Z Bert 8 wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for login through the Central KU Leuven Login (Shibboleth). The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Central KU Leuven Login) enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest/download/MediaWikiShibboleth.zip github]. Unzip the zip file in the <code>extensions/</code> directory in your MediaWiki installation folder. Make sure there is now a <code>MediaWikiShibboleth</code> folder in <code>extensions/</code>. Finally, locate the <code>LocalSettings.php</code> file in your MediaWiki installation folder and add the following lines to it: wfLoadExtension('MediaWikiShibboleth'); $wgGroupPermissions['*']['createaccount'] = false; $wgRevokePermissions['Shibboleth']['editmyprivateinfo'] = true; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 2 lines of the previous paragraph. This really defeats the purpose of the extension though. ==Configuration== MediaWikiShibboleth has some configuration options which allow for restricting who can log in to your wiki. These restrictions are cumulative. For example, it is possible to allow only students enrolled in a specific degree or programme to log in. These options work especially well with restricting the access of the wiki to logged-in users only. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code>LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code>LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code>LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow students enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code>LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. === Translations === It's possible to translate and modify all public MediaWikiShibboleth messages. The translations can be found in the <code>extensions/MediaWikiShibboleth/i18n/</code>. Dutch (<code>nl.json</code>) and English (<code>en.json</code>) translations are already provided. Even the provided translations can be customized, and we strongly advise you to do so, in order to match them with your Wiki situation. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Login without Central KU Leuven login" to expand a login menu. The new log in page looks like this with "Login without Central KU Leuven login" expanded: [[File:Login.png|thumb|none]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png|thumb|none]] [[Category:Security & anti-spam]] [[Category:CMSs]] b78be1f5723609ca9c3cba47491c012989fa7988 0 11 1404 1331 2021-06-17T15:14:45Z Bert 8 wikitext text/x-wiki As described in [[Using your webspace|https://docs.ulyssis.org/Using_your_webspace]], you have your own ULYSSIS domain name that you can use. If you wish, you can also register another domain name. ULYSSIS isn't a domain name registrar, so you'll have to use an external registrar. For example, you can find a list of all registrars for .be at [http://dns.be dns.be]. {{notice|Caution!|Please don't configure your domain to use ns4.ulyssis.student.kuleuven.be, not only will it not work, it may result in unpredictable behaviour.}} If you have registered your own domain and you want to use it with your ULYSSIS account, you need to: # Point your domain name to the following ULYSSIS nameservers: #* ns.ulyssis.student.kuleuven.be #* ns3.ulyssis.student.kuleuven.be #* Optionally: ns2.ulyssis.student.kuleuven.be # Mail us at ulyssis@ulyssis.org, with the following details: #* Your ULYSSIS username #* The domain name you registered #* The directory that you want the domain to point at. This could be your <code>www</code> folder, but any other folder within your home directory is possible. It's also possible to configure a domain to redirect to another domain or website. In that case please mention the specific URL. #* Whether you want to receive e-mail at that domain name via ULYSSIS. Note that we need to request this with ICTS, so this will take a while. Please do keep in mind that, just like any change to an account, this can only be requested by the account holder. You can find more information about DNS at http://en.wikipedia.org/wiki/Domain_Name_System. [[Category:Webserver]] d9912b4e76848f421ec4d47559bcb85ef67c2dc9 6 188 1428 2021-07-06T17:24:51Z Casper 39 wikitext text/x-wiki kuloket agenda screenshot bca98f2effa182132c4c8dcee3480313e809c208 6 189 1429 2021-07-06T17:40:10Z Casper 39 wikitext text/x-wiki kuloket agenda settings 9966accf773488c6fee1b79baa7f652de0beaf4e 0 78 1430 1133 2021-07-06T17:55:35Z Casper 39 wikitext text/x-wiki While relatively unknown, it is possible to add your KULeuven calendar to your personal agenda (e.g. Google Calendar, Outlook, Windows Calendar, etc.). This can be done by following the guide below. = Synchronizing your KULeuven calendar = [[File:Kuloket agenda.png|thumb|358x358px]] Your first step will be to visit KU Loket via Toledo or by using the following [http://kuloket.be link]. Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture. Now you will get an overview of 3 buttons (configure series, configure agenda, reload schedule). Here you will need to select '''configure agenda''', to start configuring the settings of your KULeuven calendar. [[File:Agenda settings kulolet.png|thumb|362x362px]] This should give you a page with multiple options. The only setting we will need to change here, is the switch for '''Show schedule in my agenda'''. This should be switched to '''On'''. The rest of the settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed here further. If you adjusted the setting correctly it would look something like the screenshot here. Now before continuing to the next few steps, we will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. Our following step will be to '''visit your personal student email'''. This can be done again via Toledo or by using the following [https://owa.student.kuleuven.be link]. This should bring you to your personal Mailbox. On the top right hand side of the page, there should be 3 tabs again (Mail, Calendar, People). Here you will need to select '''Calendar''', which should bring you to a page with an overview of the KULeuven calendar (future tasks and courses that are uploaded to Toledo by your professors, should also be shown here now). If the calendar is still completely empty, check if your agenda settings in KU Loket are set correctly according to the screenshot. ## Visit [http://kuloket.be/ KU Loket] ## Go to the '''Agenda''' tab [[File:KUL-Agenda-Step1.PNG|thumb|201x201px]] ## Click '''Agenda sync''' ## Click '''Configure agenda''' (''Agenda instellen'') [[File:KUL-Agenda-Step2.PNG|thumb|190px]] ## Change the switch '''Show schedule in my agenda''' (''Toon uurrooster in mijn agenda'') to '''On'''. [[File:KUL-Agenda-Step3.PNG|thumb|190px]] You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (''Agenda'') [[File:agenda4.png|thumb|190px]] # On the top right (below the menu bar), click the '''Share''' (''Delen'') button. A side-panel appears. # Enter a '''non-KU Leuven email address''' in the '''Share with''' (''Delen met'') textfield. After filling the email address, press the enter key. [[File:agenda5.png|thumb|190px]] # Make sure '''Full details''' (''Volledige informatie'') is selected in the dropdown next to your email address # Click the '''Send''' (''Verzenden'') button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. # Normally your schedule will now be showed in your agenda. If this is not the case, go back to step 1.4 and click '''reload schedule''' (''Uurrooster herladen''). Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> [[Category:Tutorials]] 4a6700d7d5dd6655db9082ca2866775de9f28f38 6 190 1431 2021-07-06T18:01:21Z Casper 39 wikitext text/x-wiki calendar menu share f06191919657806a1f15665af3cd968693ee106a 0 78 1432 1430 2021-07-06T18:01:38Z Casper 39 wikitext text/x-wiki While relatively unknown, it is possible to add your KULeuven calendar to your personal agenda (e.g. Google Calendar, Outlook, Windows Calendar, etc.). This can be done by following the guide below. = Synchronizing your KULeuven calendar = [[File:Kuloket agenda.png|thumb|358x358px]] Your first step will be to visit KU Loket via Toledo or by using the following [http://kuloket.be link]. Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture. Now you will get an overview of 3 buttons (configure series, configure agenda, reload schedule). Here you will need to select '''configure agenda''', to start configuring the settings of your KULeuven calendar. [[File:Agenda settings kulolet.png|thumb|362x362px]] This should give you a page with multiple options. The only setting we will need to change here, is the switch for '''Show schedule in my agenda'''. This should be switched to '''On'''. The rest of the settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed here further. If you adjusted the setting correctly it would look something like the screenshot here. Now before continuing to the next few steps, we will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. Our following step will be to '''visit your personal student email'''. This can be done again via Toledo or by using the following [https://owa.student.kuleuven.be link]. This should bring you to your personal Mailbox. On the top right hand side of the page, there should be 3 tabs again (Mail, Calendar, People). Here you will need to select '''Calendar''', which should bring you to a page with an overview of the KULeuven calendar (future tasks and courses that are uploaded to Toledo by your professors, should also be shown here now). If the calendar is still completely empty, check if your agenda settings in KU Loket are set correctly according to the screenshot. [[File:Menu share calendar.png|thumb|326x326px]] Continuing in the top right hand corner of the page, below the menu bar, there should be 2 buttons (share, print), as show in the screenshot. ## Visit [http://kuloket.be/ KU Loket] ## Go to the '''Agenda''' tab [[File:KUL-Agenda-Step1.PNG|thumb|201x201px]] ## Click '''Agenda sync''' ## Click '''Configure agenda''' (''Agenda instellen'') [[File:KUL-Agenda-Step2.PNG|thumb|190px]] ## Change the switch '''Show schedule in my agenda''' (''Toon uurrooster in mijn agenda'') to '''On'''. [[File:KUL-Agenda-Step3.PNG|thumb|190px]] You will have to wait about 15 minutes before continuing to the next step. # Visit https://owa.student.kuleuven.be and log in with your KU Leuven credentials. # In the top menu bar, click '''Calendar''' (''Agenda'') [[File:agenda4.png|thumb|190px]] # On the top right (below the menu bar), click the '''Share''' (''Delen'') button. A side-panel appears. # Enter a '''non-KU Leuven email address''' in the '''Share with''' (''Delen met'') textfield. After filling the email address, press the enter key. [[File:agenda5.png|thumb|190px]] # Make sure '''Full details''' (''Volledige informatie'') is selected in the dropdown next to your email address # Click the '''Send''' (''Verzenden'') button at the top of the side-panel. # You will receive an email with two weblinks. The first link shows your calendar in your webbrowser, the second link is your iCal feed. # Normally your schedule will now be showed in your agenda. If this is not the case, go back to step 1.4 and click '''reload schedule''' (''Uurrooster herladen''). Some applications will not accept a <code>webcal://</code> URL. If that is the case you can simply modify the URL to start with <code>https://</code> [[Category:Tutorials]] a6535c2c5a3c7539308ce8a8259d096519b80629 1434 1432 2021-07-06T18:54:46Z Casper 39 wikitext text/x-wiki While relatively unknown, it is possible to add your KULeuven calendar to your personal agenda (e.g. Google Calendar, Outlook, Windows Calendar, etc.). This can be done by following the guide below. = Synchronizing your KU Leuven calendar = [[File:Kuloket agenda.png|thumb|387x387px]] Your first step will be to visit KU Loket via Toledo or by using the following [http://kuloket.be link]. Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture. Now you will get an overview of 3 buttons (configure series, configure agenda, reload schedule). Here you will need to select '''configure agenda''', to start configuring the settings of your KU Leuven calendar. [[File:Agenda settings kulolet.png|thumb|389x389px]] This should give you a page with multiple options. The only setting we will need to change here, is the switch for '''Show schedule in my agenda'''. This should be switched to '''On'''. The rest of the settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed here further. If you adjusted the setting correctly it would look something like the screenshot here. Now before continuing to the next few steps, we will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. Our following step will be to '''visit your personal student email'''. This can be done again via Toledo or by using the following [https://owa.student.kuleuven.be link]. This should bring you to your personal Mailbox. On the top right hand side of the page, there should be 3 tabs again (Mail, Calendar, People). Here you will need to select '''Calendar''', which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are uploaded to Toledo by your professors, should also be shown here now). If the calendar is still completely empty, check if your agenda settings in KU Loket are set correctly according to the screenshot. [[File:Menu share calendar.png|thumb|326x326px]] Continuing in the top right hand corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a side-panel with 3 different fields. * ''Share with:'' Here you need to enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'full details' is selected from the dropdown menu (this should be by default). * ''Subject:'' This is the message you will send to the address you entered above, but because it is your own, the content of the message does not really matter. You can leave it as it is. * ''Calendar:'' This defines that you will share your calendar. You can leave it as it is. [[File:Share calendar.png|thumb|335x335px]] If you filled in the information correctly, and made sure the chosen email address is right, and compared the information to the screenshot here, you can press '''Send'''. Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email with two weblinks. The first link (ending on .html) shows your calendar in your webbrowser, the second link (ending on .ics) is your iCal feed. In this case we will need to second link. Importing the iCal link to your chosen personal agenda, can be very dependent from what personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 If your chosen calendar service is not listed here, it does not mean it won't work. Most services support importing iCal. We advice that you search the internet on how to import iCal for your service. [[Category:Tutorials]] 0c07edf84fb3074e5dd7a7ce4ac5fa2ab2abf968 1435 1434 2021-07-06T18:55:16Z Casper 39 wikitext text/x-wiki While relatively unknown, it is possible to add your KULeuven calendar to your personal agenda (e.g. Google Calendar, Outlook, Windows Calendar, etc.). This can be done by following the guide below. = Synchronizing your KU Leuven calendar = [[File:Kuloket agenda.png|thumb|387x387px]] Your first step will be to visit KU Loket via Toledo or by using the following [http://kuloket.be link]. Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture. Now you will get an overview of 3 buttons (configure series, configure agenda, reload schedule). Here you will need to select '''configure agenda''', to start configuring the settings of your KU Leuven calendar. [[File:Agenda settings kulolet.png|thumb|434x434px]] This should give you a page with multiple options. The only setting we will need to change here, is the switch for '''Show schedule in my agenda'''. This should be switched to '''On'''. The rest of the settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed here further. If you adjusted the setting correctly it would look something like the screenshot here. Now before continuing to the next few steps, we will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. Our following step will be to '''visit your personal student email'''. This can be done again via Toledo or by using the following [https://owa.student.kuleuven.be link]. This should bring you to your personal Mailbox. On the top right hand side of the page, there should be 3 tabs again (Mail, Calendar, People). Here you will need to select '''Calendar''', which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are uploaded to Toledo by your professors, should also be shown here now). If the calendar is still completely empty, check if your agenda settings in KU Loket are set correctly according to the screenshot. [[File:Menu share calendar.png|thumb|326x326px]] Continuing in the top right hand corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a side-panel with 3 different fields. * ''Share with:'' Here you need to enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'full details' is selected from the dropdown menu (this should be by default). * ''Subject:'' This is the message you will send to the address you entered above, but because it is your own, the content of the message does not really matter. You can leave it as it is. * ''Calendar:'' This defines that you will share your calendar. You can leave it as it is. [[File:Share calendar.png|thumb|335x335px]] If you filled in the information correctly, and made sure the chosen email address is right, and compared the information to the screenshot here, you can press '''Send'''. Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email with two weblinks. The first link (ending on .html) shows your calendar in your webbrowser, the second link (ending on .ics) is your iCal feed. In this case we will need to second link. Importing the iCal link to your chosen personal agenda, can be very dependent from what personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 If your chosen calendar service is not listed here, it does not mean it won't work. Most services support importing iCal. We advice that you search the internet on how to import iCal for your service. [[Category:Tutorials]] 2ab3f498657621aaa7c10cf0a1353f619d13e9c0 1438 1435 2021-07-06T21:26:28Z Casper 39 wikitext text/x-wiki While relatively unknown, it is possible to add your KULeuven calendar to your personal agenda (e.g. Google Calendar, Outlook, Windows Calendar, etc.). This can be done by following the guide below. = Synchronizing your KU Leuven calendar = [[File:Kuloket2.png|thumb|333x333px]] Your first step will be to visit KU Loket via Toledo or by using the following [http://kuloket.be link]. Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture. Now you will get an overview of 3 buttons (configure series, configure agenda, reload schedule). Here you will need to select '''configure agenda''', to start configuring the settings of your KU Leuven calendar. [[File:Agendasettings2.png|thumb|415x415px]] This should give you a page with multiple options. The only setting we will need to change here, is the switch for '''Show schedule in my agenda'''. This should be switched to '''On'''. The rest of the settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed here further. If you adjusted the setting correctly it would look something like the screenshot here. Now before continuing to the next few steps, we will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. Our following step will be to '''visit your personal student email'''. This can be done again via Toledo or by using the following [https://owa.student.kuleuven.be link]. This should bring you to your personal Mailbox. On the top right hand side of the page, there should be 3 tabs again (Mail, Calendar, People). Here you will need to select '''Calendar''', which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are uploaded to Toledo by your professors, should also be shown here now). If the calendar is still completely empty, check if your agenda settings in KU Loket are set correctly according to the screenshot. [[File:Menu share calendar.png|thumb|326x326px]] Continuing in the top right hand corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a side-panel with 3 different fields. * ''Share with:'' Here you need to enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'full details' is selected from the dropdown menu (this should be by default). * ''Subject:'' This is the message you will send to the address you entered above, but because it is your own, the content of the message does not really matter. You can leave it as it is. * ''Calendar:'' This defines that you will share your calendar. You can leave it as it is. [[File:Share calendar.png|thumb|335x335px]] If you filled in the information correctly, and made sure the chosen email address is right, and compared the information to the screenshot here, you can press '''Send'''. Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email with two weblinks. The first link (ending on .html) shows your calendar in your webbrowser, the second link (ending on .ics) is your iCal feed. In this case we will need to second link. Importing the iCal link to your chosen personal agenda, can be very dependent from what personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 If your chosen calendar service is not listed here, it does not mean it won't work. Most services support importing iCal. We advice that you search the internet on how to import iCal for your service. [[Category:Tutorials]] e4dbbf8bfea7d01ae76162c7511679e946773c71 1442 1438 2021-07-06T21:33:33Z Casper 39 wikitext text/x-wiki While relatively unknown, it is possible to add your KULeuven calendar to your personal agenda (e.g. Google Calendar, Outlook, Windows Calendar, etc.). This can be done by following the guide below. = Synchronizing your KU Leuven calendar = [[File:Kuloket3.png|thumb]] Your first step will be to visit KU Loket via Toledo or by using the following [http://kuloket.be link]. Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture. Now you will get an overview of 3 buttons (configure series, configure agenda, reload schedule). Here you will need to select '''configure agenda''', to start configuring the settings of your KU Leuven calendar. [[File:Agendasettings3.png|thumb|415x415px]] This should give you a page with multiple options. The only setting we will need to change here, is the switch for '''Show schedule in my agenda'''. This should be switched to '''On'''. The rest of the settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed here further. If you adjusted the setting correctly it would look something like the screenshot here. Now before continuing to the next few steps, we will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. Our following step will be to '''visit your personal student email'''. This can be done again via Toledo or by using the following [https://owa.student.kuleuven.be link]. This should bring you to your personal Mailbox. On the top right hand side of the page, there should be 3 tabs again (Mail, Calendar, People). Here you will need to select '''Calendar''', which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are uploaded to Toledo by your professors, should also be shown here now). [[File:Menushare2.png|thumb]] If the calendar is still completely empty, check if your agenda settings in KU Loket are set correctly according to the screenshot. Continuing in the top right hand corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a side-panel with 3 different fields. * ''Share with:'' Here you need to enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'full details' is selected from the dropdown menu (this should be by default). * ''Subject:'' This is the message you will send to the address you entered above, but because it is your own, the content of the message does not really matter. You can leave it as it is. * ''Calendar:'' This defines that you will share your calendar. You can leave it as it is. [[File:Share calendar.png|thumb|335x335px]] If you filled in the information correctly, and made sure the chosen email address is right, and compared the information to the screenshot here, you can press '''Send'''. Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email with two weblinks. The first link (ending on .html) shows your calendar in your webbrowser, the second link (ending on .ics) is your iCal feed. In this case we will need to second link. Importing the iCal link to your chosen personal agenda, can be very dependent from what personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 If your chosen calendar service is not listed here, it does not mean it won't work. Most services support importing iCal. We advice that you search the internet on how to import iCal for your service. [[Category:Tutorials]] 6f5b22921b697eaa91edee398b72444cd28a93be 1443 1442 2021-07-06T21:35:58Z Casper 39 wikitext text/x-wiki While relatively unknown, it is possible to add your KULeuven calendar to your personal agenda (e.g. Google Calendar, Outlook, Windows Calendar, etc.). This can be done by following the guide below. = Synchronizing your KU Leuven calendar = [[File:Kuloket3.png|thumb]] Your first step will be to visit KU Loket via Toledo or by using the following [http://kuloket.be link]. Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture. Now you will get an overview of 3 buttons (configure series, configure agenda, reload schedule). Here you will need to select '''configure agenda''', to start configuring the settings of your KU Leuven calendar. [[File:Agendasettings3.png|thumb|415x415px]] This should give you a page with multiple options. The only setting we will need to change here, is the switch for '''Show schedule in my agenda'''. This should be switched to '''On'''. The rest of the settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed here further. If you adjusted the setting correctly it would look something like the screenshot here. Now before continuing to the next few steps, we will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. The following step will be to '''visit your personal student email'''. This can be done again via Toledo or by using the following [https://owa.student.kuleuven.be link]. This should bring you to your personal Mailbox. On the top right hand side of the page, you should see 3 tabs (Mail, Calendar, People). Here you will need to select '''Calendar''', which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are uploaded to Toledo by your professors, should also be shown here now). [[File:Menushare2.png|thumb]] If the calendar is still completely empty, check if your agenda settings in KU Loket are set correctly according to the screenshot. Continuing in the top right hand corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a side-panel with 3 different fields. * ''Share with:'' Here you need to enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'full details' is selected from the dropdown menu (this should be by default). * ''Subject:'' This is the message you will send to the address you entered above, but because it is your own, the content of the message does not really matter. You can leave it as it is. * ''Calendar:'' This defines that you will share your calendar. You can leave it as it is. [[File:Share calendar.png|thumb|335x335px]] If you filled in the information correctly, and made sure the chosen email address is right, and compared the information to the screenshot here, you can press '''Send'''. Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email with two weblinks. The first link (ending on .html) shows your calendar in your webbrowser, the second link (ending on .ics) is your iCal feed. In this case we will need to second link. Importing the iCal link to your chosen personal agenda, can be very dependent from what personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 If your chosen calendar service is not listed here, it does not mean it won't work. Most services support importing iCal. We advice that you search the internet on how to import iCal for your service. [[Category:Tutorials]] 34f2b29467d3929de6094274bed16e2323dec99d 1444 1443 2021-07-06T21:47:54Z Casper 39 wikitext text/x-wiki This guide will explain how your KU Leuven calendar, which you can see on Toledo, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Outlook, Windows Calendar, etc.), and by following the steps below. = Synchronizing your KU Leuven calendar = [[File:Kuloket3.png|thumb]] Your first step will be to visit KU Loket via Toledo or by using the following [http://kuloket.be link]. Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture. Now you will get an overview of 3 buttons (configure series, configure agenda, reload schedule). Here you will need to select '''configure agenda''', to start configuring the settings of your KU Leuven calendar. [[File:Agendasettings3.png|thumb|415x415px]] This should give you a page with multiple options. The only setting we will need to change here, is the switch for '''Show schedule in my agenda'''. This should be switched to '''On'''. The rest of the settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed here further. If you adjusted the setting correctly it would look something like the screenshot here. Now before continuing to the next few steps, we will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. The following step will be to '''visit your personal student email'''. This can be done again via Toledo or by using the following [https://owa.student.kuleuven.be link]. This should bring you to your personal Mailbox. On the top right hand side of the page, you should see 3 tabs (Mail, Calendar, People). Here you will need to select '''Calendar''', which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are uploaded to Toledo by your professors, should also be shown here now). [[File:Menushare2.png|thumb]] If the calendar is still completely empty, check if your agenda settings in KU Loket are set correctly according to the screenshot. Continuing in the top right hand corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a side-panel with 3 different fields. * ''Share with:'' Here you need to enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'full details' is selected from the dropdown menu (this should be by default). * ''Subject:'' This is the message you will send to the address you entered above, but because it is your own, the content of the message does not really matter. You can leave it as it is. * ''Calendar:'' This defines that you will share your calendar. You can leave it as it is. [[File:Share calendar.png|thumb|335x335px]] If you filled in the information correctly, and made sure the chosen email address is right, and compared the information to the screenshot here, you can press '''Send'''. Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email with two weblinks. The first link (ending on .html) shows your calendar in your webbrowser, the second link (ending on .ics) is your iCal feed. In this case we will need to second link. Importing the iCal link to your chosen personal agenda, can be very dependent from what personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 If your chosen calendar service is not listed here, it does not mean it won't work. Most services support importing iCal. We advice that you search the internet on how to import iCal for your service. [[Category:Tutorials]] 1f8313cea05b79fb6d0e1a1e074869adbff752b9 1445 1444 2021-07-06T21:49:14Z Casper 39 wikitext text/x-wiki This guide will explain how your KU Leuven calendar, which you can see on Toledo, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Outlook, Windows Calendar, etc.), and by following the steps below. = Synchronizing your KU Leuven calendar = [[File:Kuloket3.png|thumb]] Your first step will be to visit KU Loket via Toledo or by using the following [http://kuloket.be link]. Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture. Now you will get an overview of 3 buttons (configure series, configure agenda, reload schedule). Here you will need to select '''configure agenda''', to start configuring the settings of your KU Leuven calendar. [[File:Agendasettings3.png|thumb|415x415px]] This should give you a page with multiple options. The only setting we will need to change here, is the switch for '''Show schedule in my agenda'''. This should be switched to '''On'''. The rest of the settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed here further. If you adjusted the setting correctly it would look something like the screenshot here. Now before continuing to the next few steps, we will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. The following step will be to '''visit your personal student email'''. This can be done again via Toledo or by using the following [https://owa.student.kuleuven.be link]. This should bring you to your personal Mailbox. On the top right hand side of the page, you should see 3 tabs (Mail, Calendar, People). Here you will need to select '''Calendar''', which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are uploaded to Toledo by your professors, should also be shown here now). [[File:Menushare2.png|thumb]] If the calendar is still completely empty, check if your agenda settings in KU Loket are set correctly according to the screenshot. Continuing in the top right hand corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a side-panel with 3 different fields. * ''Share with:'' Here you need to enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'full details' is selected from the dropdown menu (this should be done by default). * ''Subject:'' This is the message you will send to the address you entered above, but because it is your own, the content of the message does not really matter. You can leave it as it is. * ''Calendar:'' This defines that you will share your calendar. You can leave it as it is. [[File:Share calendar.png|thumb|335x335px]] If you filled in the information correctly, and made sure the chosen email address is right, and compared the information to the screenshot here, you can press '''Send'''. Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email with two weblinks. The first link (ending on .html) shows your calendar in your webbrowser, the second link (ending on .ics) is your iCal feed. In this case we will need to second link. Importing the iCal link to your chosen personal agenda, can be very dependent from what personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 If your chosen calendar service is not listed here, it does not mean it won't work. Most services support importing iCal. We advice that you search the internet on how to import iCal for your service. [[Category:Tutorials]] 7f88d7387cce9e2d0bc224c148520dd00f080285 1468 1445 2021-07-24T15:40:12Z Casper 39 wikitext text/x-wiki This guide will explain how your KU Leuven calendar, which you can see on Toledo, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Thunderbird, Outlook, Windows Calendar, etc.), following the steps below. = Synchronizing your KU Leuven calendar = [[File:Kuloket3.png|thumb|359x359px]] Your first step will be to visit KU Loket via Toledo or by visiting [http://kuloket.be kuloket.be] . Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture. Now you will get an overview of 3 buttons (configure series, configure agenda, reload schedule). Here you will need to select '''configure agenda''', to start configuring the settings of your KU Leuven calendar. [[File:Agendasettings3.png|thumb|415x415px]] This should give you a page with multiple options. The only setting we will need to change here, is the switch for '''Show schedule in my agenda'''. This should be switched to '''On'''. The rest of the settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed further here. If you adjusted the setting correctly it would look something like the screenshot on the right. Now before continuing to the next few steps, we will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. The following step will be to '''visit your personal student email'''. This can be done again via Toledo or by visiting [https://owa.student.kuleuven.be owa.student.kuleuven.be] .This should bring you to your personal mailbox. In the top right corner of the page, you should see 3 tabs (Mail, Calendar, People). Here you will need to select '''Calendar''', which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are put on Toledo by your professors, should also be shown here now). [[File:Menushare2.png|thumb|353x353px]] If the calendar is still completely empty, check if your agenda settings in KU Loket are set correctly according to the screenshot and that you are looking at time period where classes are scheduled and not a holiday period. Continuing in the top right corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a side-panel with 3 different fields. *''Share with:'' Here you need to enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'full details' is selected from the dropdown menu (this should be done by default). *''Subject:'' This is the message you will send to the address you entered above, but the content of the message does not really matter. You can leave it as it is. *''Calendar:'' This defines that you will share your calendar. You can leave it as it is. [[File:Share calendar.png|thumb|402x402px]] If you filled in the information correctly, made sure the chosen email address is right, and compared the information to the screenshot on the right, you can press '''Send'''. Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email with two weblinks. The first link (ending on .html) shows your calendar in your webbrowser, the second link (ending on .ics) is your iCal feed. In this case we will need the second link. Importing the iCal link to your chosen personal agenda can vary widely depending on which personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 Almost all calendar services support importing iCal. If your chosen calendar service is not listed here, you can try searching the internet on how to import iCal for your service. [[Category:Tutorials]] 0cf4fa098bc2cc1c6a6ed2bb056fa4767210b861 1469 1468 2021-07-24T15:47:46Z Casper 39 wikitext text/x-wiki This guide will explain how your KU Leuven calendar, which you can see on Toledo, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Thunderbird, Outlook, Windows Calendar, etc.), following the steps below. = Synchronizing your KU Leuven calendar = [[File:Kuloket3.png|thumb|359x359px]] Your first step will be to visit KU Loket via Toledo or by visiting [http://kuloket.be kuloket.be] . Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture. Now you will get an overview of 3 buttons (configure series, configure agenda, reload schedule). Here you will need to select '''configure agenda''', to start configuring the settings of your KU Leuven calendar. [[File:Agendasettings3.png|thumb|476x476px]] This should give you a page with multiple options. The only setting we will need to change here, is the switch for '''Show schedule in my agenda'''. This should be switched to '''On'''. The rest of the settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed further here. If you adjusted the setting correctly it would look something like the screenshot on the right. Now before continuing to the next few steps, we will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. The following step will be to '''visit your personal student email'''. This can be done again via Toledo or by visiting [https://owa.student.kuleuven.be owa.student.kuleuven.be] .This should bring you to your personal mailbox. In the top right corner of the page, you should see 3 tabs (Mail, Calendar, People). Here you will need to select '''Calendar''', which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are put on Toledo by your professors, should also be shown here now). [[File:Menushare2.png|thumb|353x353px]] If the calendar is still completely empty, check if your agenda settings in KU Loket are set correctly according to the screenshot and that you are looking at time period where classes are scheduled and not a holiday period. Continuing in the top right corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a side-panel with 3 different fields. *''Share with:'' Here you need to enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'full details' is selected from the dropdown menu (this should be done by default). *''Subject:'' This is the message you will send to the address you entered above, but the content of the message does not really matter. You can leave it as it is. *''Calendar:'' This defines that you will share your calendar. You can leave it as it is. [[File:Share calendar.png|thumb|402x402px]] If you filled in the information correctly, made sure the chosen email address is right, and compared the information to the screenshot on the right, you can press '''Send'''. Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email with two weblinks. The first link (ending on .html) shows your calendar in your webbrowser, the second link (ending on .ics) is your iCal feed. In this case we will need the second link. Importing the iCal link to your chosen personal agenda can vary widely depending on which personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 Almost all calendar services support importing iCal. If your chosen calendar service is not listed here, you can try searching the internet on how to import iCal for your service. [[Category:Tutorials]] df4527cb94208c53c89e2b9c974dcf0e4b6dc173 1472 1469 2021-08-02T18:50:32Z Casper 39 Casper moved page [[KULoket agenda iCal feed]] to [[Exporting your KU Leuven class schedule and calendar]] wikitext text/x-wiki This guide will explain how your KU Leuven calendar, which you can see on Toledo, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Thunderbird, Outlook, Windows Calendar, etc.), following the steps below. = Synchronizing your KU Leuven calendar = [[File:Kuloket3.png|thumb|359x359px]] Your first step will be to visit KU Loket via Toledo or by visiting [http://kuloket.be kuloket.be] . Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture. Now you will get an overview of 3 buttons (configure series, configure agenda, reload schedule). Here you will need to select '''configure agenda''', to start configuring the settings of your KU Leuven calendar. [[File:Agendasettings3.png|thumb|476x476px]] This should give you a page with multiple options. The only setting we will need to change here, is the switch for '''Show schedule in my agenda'''. This should be switched to '''On'''. The rest of the settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed further here. If you adjusted the setting correctly it would look something like the screenshot on the right. Now before continuing to the next few steps, we will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. The following step will be to '''visit your personal student email'''. This can be done again via Toledo or by visiting [https://owa.student.kuleuven.be owa.student.kuleuven.be] .This should bring you to your personal mailbox. In the top right corner of the page, you should see 3 tabs (Mail, Calendar, People). Here you will need to select '''Calendar''', which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are put on Toledo by your professors, should also be shown here now). [[File:Menushare2.png|thumb|353x353px]] If the calendar is still completely empty, check if your agenda settings in KU Loket are set correctly according to the screenshot and that you are looking at time period where classes are scheduled and not a holiday period. Continuing in the top right corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a side-panel with 3 different fields. *''Share with:'' Here you need to enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'full details' is selected from the dropdown menu (this should be done by default). *''Subject:'' This is the message you will send to the address you entered above, but the content of the message does not really matter. You can leave it as it is. *''Calendar:'' This defines that you will share your calendar. You can leave it as it is. [[File:Share calendar.png|thumb|402x402px]] If you filled in the information correctly, made sure the chosen email address is right, and compared the information to the screenshot on the right, you can press '''Send'''. Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email with two weblinks. The first link (ending on .html) shows your calendar in your webbrowser, the second link (ending on .ics) is your iCal feed. In this case we will need the second link. Importing the iCal link to your chosen personal agenda can vary widely depending on which personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 Almost all calendar services support importing iCal. If your chosen calendar service is not listed here, you can try searching the internet on how to import iCal for your service. [[Category:Tutorials]] df4527cb94208c53c89e2b9c974dcf0e4b6dc173 1475 1472 2021-08-02T19:19:01Z Casper 39 wikitext text/x-wiki This guide will explain how your KU Leuven calendar, which you can see on Toledo, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Thunderbird, Outlook, Windows Calendar, etc.), following the steps below. = Synchronizing your KU Leuven calendar = [[File:Kuloket3.png|thumb|359x359px]] Your first step will be to visit KU Loket via Toledo or by visiting [http://kuloket.be kuloket.be] . Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture. Now you will get an overview of 3 buttons (configure series, configure agenda, reload schedule). Here you will need to select '''configure agenda''', to start configuring the settings of your KU Leuven calendar. [[File:Agendasettings4.png|thumb|370x370px]] This should give you a page with multiple options. The only setting we will need to change here, is the switch for '''Show schedule in my agenda'''. This should be switched to '''On'''. The rest of the settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed further here. If you adjusted the setting correctly it would look something like the screenshot on the right. Now before continuing to the next few steps, we will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. The following step will be to '''visit your personal student email'''. This can be done again via Toledo or by visiting [https://owa.student.kuleuven.be owa.student.kuleuven.be] .This should bring you to your personal mailbox. In the top right corner of the page, you should see 3 tabs (Mail, Calendar, People). Here you will need to select '''Calendar''', which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are put on Toledo by your professors, should also be shown here now). [[File:Menushare2.png|thumb|353x353px]] If the calendar is still completely empty, check if your agenda settings in KU Loket are set correctly according to the screenshot and that you are looking at time period where classes are scheduled and not a holiday period. Continuing in the top right corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a side-panel with 3 different fields. *''Share with:'' Here you need to enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'full details' is selected from the dropdown menu (this should be done by default). *''Subject:'' This is the message you will send to the address you entered above, but the content of the message does not really matter. You can leave it as it is. *''Calendar:'' This defines that you will share your calendar. You can leave it as it is. [[File:Share calendar.png|thumb|402x402px]] If you filled in the information correctly, made sure the chosen email address is right, and compared the information to the screenshot on the right, you can press '''Send'''. Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email with two weblinks. The first link (ending on .html) shows your calendar in your webbrowser, the second link (ending on .ics) is your iCal feed. In this case we will need the second link. Importing the iCal link to your chosen personal agenda can vary widely depending on which personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 Almost all calendar services support importing iCal. If your chosen calendar service is not listed here, you can try searching the internet on how to import iCal for your service. [[Category:Tutorials]] 8ea7e723616105a7575eaac4c1b4e12e1446fa98 1476 1475 2021-08-02T19:19:28Z Casper 39 wikitext text/x-wiki This guide will explain how your KU Leuven calendar, which you can see on Toledo, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Thunderbird, Outlook, Windows Calendar, etc.), following the steps below. = Synchronizing your KU Leuven calendar = [[File:Kuloket3.png|thumb|359x359px]] Your first step will be to visit KU Loket via Toledo or by visiting [http://kuloket.be kuloket.be] . Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture. Now you will get an overview of 3 buttons (configure series, configure agenda, reload schedule). Here you will need to select '''configure agenda''', to start configuring the settings of your KU Leuven calendar. [[File:Agendasettings4.png|thumb|399x399px]] This should give you a page with multiple options. The only setting we will need to change here, is the switch for '''Show schedule in my agenda'''. This should be switched to '''On'''. The rest of the settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed further here. If you adjusted the setting correctly it would look something like the screenshot on the right. Now before continuing to the next few steps, we will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. The following step will be to '''visit your personal student email'''. This can be done again via Toledo or by visiting [https://owa.student.kuleuven.be owa.student.kuleuven.be] .This should bring you to your personal mailbox. In the top right corner of the page, you should see 3 tabs (Mail, Calendar, People). Here you will need to select '''Calendar''', which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are put on Toledo by your professors, should also be shown here now). [[File:Menushare2.png|thumb|353x353px]] If the calendar is still completely empty, check if your agenda settings in KU Loket are set correctly according to the screenshot and that you are looking at time period where classes are scheduled and not a holiday period. Continuing in the top right corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a side-panel with 3 different fields. *''Share with:'' Here you need to enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'full details' is selected from the dropdown menu (this should be done by default). *''Subject:'' This is the message you will send to the address you entered above, but the content of the message does not really matter. You can leave it as it is. *''Calendar:'' This defines that you will share your calendar. You can leave it as it is. [[File:Share calendar.png|thumb|427x427px]] If you filled in the information correctly, made sure the chosen email address is right, and compared the information to the screenshot on the right, you can press '''Send'''. Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email with two weblinks. The first link (ending on .html) shows your calendar in your webbrowser, the second link (ending on .ics) is your iCal feed. In this case we will need the second link. Importing the iCal link to your chosen personal agenda can vary widely depending on which personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 Almost all calendar services support importing iCal. If your chosen calendar service is not listed here, you can try searching the internet on how to import iCal for your service. [[Category:Tutorials]] 11f1f5cb23c6bf646e82c984c162ac913c2f592e 1477 1476 2021-08-02T19:20:53Z Casper 39 wikitext text/x-wiki This guide will explain how your KU Leuven calendar, which you can see on Toledo, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Thunderbird, Outlook, Windows Calendar, etc.), following the steps below. = Synchronizing your KU Leuven calendar = [[File:Kuloket3.png|thumb|359x359px]] Your first step will be to visit KU Loket via Toledo or by visiting [http://kuloket.be kuloket.be] . Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture. Now you will get an overview of 3 buttons (configure series, configure agenda, reload schedule). Here you will need to select '''configure agenda''', to start configuring the settings of your KU Leuven calendar. [[File:Agendasettings4.png|thumb|430x430px]] This should give you a page with multiple options. The only setting we will need to change here, is the switch for '''Show schedule in my agenda'''. This should be switched to '''On'''. The rest of the settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed further here. If you adjusted the setting correctly it would look something like the screenshot on the right. Now before continuing to the next few steps, we will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. The following step will be to '''visit your personal student email'''. This can be done again via Toledo or by visiting [https://owa.student.kuleuven.be owa.student.kuleuven.be] .This should bring you to your personal mailbox. In the top right corner of the page, you should see 3 tabs (Mail, Calendar, People). Here you will need to select '''Calendar''', which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are put on Toledo by your professors, should also be shown here now). [[File:Menushare2.png|thumb|353x353px]] If the calendar is still completely empty, check if your agenda settings in KU Loket are set correctly according to the screenshot and that you are looking at time period where classes are scheduled and not a holiday period. Continuing in the top right corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a side-panel with 3 different fields. *''Share with:'' Here you need to enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'full details' is selected from the dropdown menu (this should be done by default). *''Subject:'' This is the message you will send to the address you entered above, but the content of the message does not really matter. You can leave it as it is. *''Calendar:'' This defines that you will share your calendar. You can leave it as it is. [[File:Share calendar.png|thumb|427x427px]] If you filled in the information correctly, made sure the chosen email address is right, and compared the information to the screenshot on the right, you can press '''Send'''. Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email with two weblinks. The first link (ending on .html) shows your calendar in your webbrowser, the second link (ending on .ics) is your iCal feed. In this case we will need the second link. Importing the iCal link to your chosen personal agenda can vary widely depending on which personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 Almost all calendar services support importing iCal. If your chosen calendar service is not listed here, you can try searching the internet on how to import iCal for your service. [[Category:Tutorials]] 48ff950ea557e1a917e6bcd12e25a8feb60c5558 6 191 1433 2021-07-06T18:33:39Z Casper 39 wikitext text/x-wiki Share calendar fb66e603e0b84c85638d2e4424d0a05451e145e9 6 192 1436 2021-07-06T21:24:01Z Casper 39 wikitext text/x-wiki kuloket 2 0296842340d604da22d7e0a55c1ff52ca66ed5b4 6 193 1437 2021-07-06T21:26:01Z Casper 39 wikitext text/x-wiki Agendasettings2 161cd801fd398d367877ff37cc929b17b5c2ed0a 6 194 1439 2021-07-06T21:31:08Z Casper 39 wikitext text/x-wiki Kuloket3 0b3d6c04c7643ea2e4e27fb1b0f809da6e362264 6 195 1440 2021-07-06T21:31:43Z Casper 39 wikitext text/x-wiki Agendasettings3 5b840686da7ad430ca24e5ce6ba9a9e7afa02cf0 6 196 1441 2021-07-06T21:33:06Z Casper 39 wikitext text/x-wiki Menushare2 4caf0f66552f7ef71a02bb7fa4c4ab9be1a87aba 0 47 1452 1243 2021-07-10T17:30:48Z Bert 8 wikitext text/x-wiki This page will go through a basic setup of MediaWiki. It is based on [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wikipage], and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. This tutorial we'll use a ULYSSIS-account with username "me". == Putting setup-files in place == First we'll have to download the setup file which you can find over at [http://www.mediawiki.org/wiki/Download the official MediaWiki website]. It's an archived file, so you need to extract it first and put the files in a subdirectory of your "document root". The default is just a www directory in your home folder. Putting your files in document_root/wiki/ will make your wiki be located at username.ulyssis.be/wiki/. If you prefer, you can do this all graphically using the manual [[Accessing_your_files]]. If you prefer the command line; <pre> homeuser@home:~$ ssh me@ssh1.ulyssis.org enter super secret password: me@zap:~$ wget https://releases.wikimedia.org/mediawiki/1.35/mediawiki-1.35.1.zip me@zap:~$ unzip mediawiki-1.35.1.zip me@zap:~$ mv mediawiki-1.35.1 www/wiki me@zap:~$ rm -r mediawiki-1.35.1.zip </pre> ==Setting up database== Like the [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki the official MediaWiki installation wiki] tells us, we have three different options to choose from; PostgreSQL, MySQL and SQLite. It's easy to set a PostgreSQL or MySQL database; just go to the UCC. For this tutorial we will continue with a MySQL database (PostgreSQL installation steps are quite similar). Let us visit https://ucc.ulyssis.org/mysql; if this is your first time using MySQL you'll need to create a new account by putting in a super secret password. The wizard will create your MySQL account with the same name as your user-account. We'll also create a new database with an appropriate name by clicking on 'Add database'. In this tutorial we will choose; "wiki", notice that it will be prepended with our username, so we'll end up with a new database named "me_wiki". ==Setup your wiki== If all went well, you can access your website at http://username.ulyssis.be/the_folder_you_used and start the setup wizard. In our example, will surf to http://me.ulyssis.be/wiki. The wizard will guide you through some configuration options. Most of them our pretty straight-forward. When in doubt, you can always click the question mark wich will show you some sensible and recommended default... We'll just discuss the page were the wizard asks you for the database. In our example; <pre> Database host: mysql.ulyssis.org Database name: me_wiki // The name of our database; i.e. the name we chose, prepended by our username. Database table prefix: // We can leave this blank. Database user: me // This is the name of our MySQL-user, which was named after our ULYSSIS-username. Database password: supersecretpassword // Please note that this is not your ULYSSIS-password, but the password you used in UCC when creating the MySQL user! </pre> ==Creating the wiki== After the setup wizard is complete, you can begin the installation procedure. If all went well, you'll be greeted by a page which congratulates you with your new installation. ==Finishing up installation== The setup will offer you a configuration file (containing some settings you specified) that you need to download to your server (more specifically in directory where your MediaWiki-files reside in). You again can do this graphically, or if you prefer a terminal; <pre> homeuser@home:~$ scp path_to_file/LocalSettings.php me@ssh1.ulyssis.org:~/www/wiki enter super secret password: </pre> After this is done, you can finally start using your wiki. Please refer to [http://www.mediawiki.org/wiki/MediaWiki the original MediaWiki documentation] for a more detailed or advanced information. == Extending MediaWiki == By default, every MediaWiki installation looks and works identical. While that is convenient for users, it can be less than ideal if you need specific functionality or wish to adapt your wiki to your style. === Extensions === Extensions add functionality to a wiki, such as more fine-grained authentication, extra layout elements for articles or text filters. An overview of what kinds of extensions are possible can be found on [https://www.mediawiki.org/wiki/Manual:Extensions the official manual]. Some noteworthy extensions can be used to prevent spam or unauthorised access. You can find more information on [[Preventing spam on MediaWiki]] and [[Securing MediaWiki using Centrale KU Leuven Login]]. We've also found that users sometimes have problems with high amounts of disk space usage. To help those users out, we've developed a MediaWiki extension that can automatically reduce file size of new uploads. Specifically it's possible to compress PDFs, convert inefficient image formats such as BMP and TIFF to PNG, loslessly compress PNG, lossy compress JPG, resize images and strip EXIF data. You can find more details on https://github.com/ULYSSIS-KUL/CompressUploads === Skins === Skins are similar to themes, templates or styles within other software. By default MediaWiki uses the well known Vector skin. But other skins are available. Sadly, MediaWiki doesn't maintain a complete list of all available skins and whether they work with recent releases, so it may take a bit of perseverance. General information on Skins is available on the [https://www.mediawiki.org/wiki/Manual:Skins Official Manual]. Besides that there's the [https://www.mediawiki.org/wiki/Manual:Gallery_of_user_styles the user style gallery] and [https://www.mediawiki.org/wiki/Category:All_skins the list of skins]. [[Category:CMSs]] b0449c933ac1eb6973d191356d31ec0c746c1631 6 175 1455 1406 2021-07-16T10:56:53Z Wtas 42 Wtas uploaded a new version of [[File:Navigating-WB.png]] wikitext text/x-wiki Navigating in Cyberduck 0dbedf98422e398de542e68b9b4805efa175a3c4 6 197 1456 2021-07-16T10:58:07Z Wtas 42 wikitext text/x-wiki Show Hidden Files toggle 7799ffb9717b17c79890a2009e4167b426c11b9b 0 37 1458 1341 2021-07-19T23:55:03Z Bert 8 /* Restarting your application */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <code>.cgi</code> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <code>www</code> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <code>hello.cgi</code>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your programming languae, framework or application. Just do a web search for "''keyword'' mod_fcgid", where ''keyword'' is the programming language, framework or application you're planning to use, and you will often find good instructions. We've included some examples below You'll want to treat this starter script as a <code>mod_fcgid</code> script, and usually, you'll want to redirect everything to this script, so you can use an <code>.htaccess</code> file that looks like this: <syntaxhighlight lang="apache">Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</syntaxhighlight> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <code>.htaccess</code> file. {{warning|Warning!|Do not place sensitive files inside the web accessible folder. Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.}} It is adviced to only place the fcgi starter script, <code>.htaccess</code> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [[Managing_Cron_jobs | cronjob]] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than where it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django and Go examples below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <code>touch</code>: <pre>touch starter.fcgi</pre> Replace <code>starter.fcgi</code> with the name of your starter script. === Examples === ==== Python and Django ==== If you want to make a website using Python and [https://www.djangoproject.com/ Django], we recommend that you use a virtual environment. You can use the following steps to get up and running with Django on your ULYSSIS hosting account. <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <code>~/.venv</code>, for example: <pre>python3 -m venv ~/.venv</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <code>.htaccess</code> file in your site's directory, e.g. the <code>www</code> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace <code>user</code> with org if you are an organization, and <code>username</code> with your ULYSSIS username): <syntaxhighlight lang="python">#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </syntaxhighlight> Call this script <code>mysite.fcgi</code>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [https://flask.palletsprojects.com/en/1.1.x/deploying/fastcgi/ Flask documentation for FastCGI] ==== Go ==== To make a website or web application in Go and host it on your ULYSSIS hosting account, you can use the standard library ''fcgi'' package. <ol> <li> [[Accessing shell servers over SSH|Log in to a shell server]]</li> <li> Put an <code>.htaccess</code> file in your site's directory (e.g. the <code>www</code> folder) with a reference to your executable. Here we've chosen <code>mysite.fcgi</code>, but you can adapt this to your liking. <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Write your code, and compile the binary to <code>mysite.fcgi</code>. Below you can find a basic example of how to register two handlers (of which one is the fallback), then start the FastCGI client, and finally have a function (which is called as a goroutine) to check if the binary has been replaced so old processes don't stick around. <syntaxhighlight lang="go">package main import ( "fmt" "net/http" "net/http/fcgi" "os" "path/filepath" "time" ) func uri_interesting(w http.ResponseWriter, r *http.Request) { w.WriteHeader(http.StatusOK) fmt.Fprintln(w, "<h1>Oh, seems like this link isn't that interesting after all</h1>") fmt.Fprintln(w, "<p>Back to the <a href=\"/\">Homepage</a></p>") } func uri_default(w http.ResponseWriter, r *http.Request) { if r.URL.Path != "/" { w.WriteHeader(http.StatusNotFound) fmt.Fprintln(w, "<h1>This page doesn't exist</h1>") fmt.Fprintln(w, "<p>Back to the <a href=\"/\">Homepage</a></p>") } else { w.WriteHeader(http.StatusOK) fmt.Fprintln(w, "<h1>Welcome to this testwebsite!</h1>") fmt.Fprintln(w, "<p>This website is written in Go but doesn't really do much.") fmt.Fprintln(w, "Feel free to visit this <a href=\"/interesting/link\">Interesting link</a> or this <a href=\"/non-existent/link\">non-existent link</a>.</p>") } } func main() { go check_selfreplacement() http.HandleFunc("/interesting/link", uri_interesting) http.HandleFunc("/", uri_default) if err := fcgi.Serve(nil, nil); err != nil { panic(err) } } func check_selfreplacement() { fcgi_location, _ := os.Executable() fcgi_location, _ = filepath.EvalSymlinks(fcgi_location) start_stat, _ := os.Stat(fcgi_location) for { current_stat, _ := os.Stat(fcgi_location) if start_stat.ModTime() != current_stat.ModTime() { os.Exit(0) } time.Sleep(1 * time.Second) } } </syntaxhighlight> If you want to give this example a try, save it as <code>mysite.fcgi.go</code> and then use <code>go build</code> to compile it. </li> <li>Visit your website to verify everything works</li> </ol> [[Category:Webserver]] 5b08fe325792484f9fcb0251e5c2f9310cff70fd 1459 1458 2021-07-19T23:58:16Z Bert 8 /* Go */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <code>.cgi</code> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <code>www</code> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <code>hello.cgi</code>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your programming languae, framework or application. Just do a web search for "''keyword'' mod_fcgid", where ''keyword'' is the programming language, framework or application you're planning to use, and you will often find good instructions. We've included some examples below You'll want to treat this starter script as a <code>mod_fcgid</code> script, and usually, you'll want to redirect everything to this script, so you can use an <code>.htaccess</code> file that looks like this: <syntaxhighlight lang="apache">Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</syntaxhighlight> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <code>.htaccess</code> file. {{warning|Warning!|Do not place sensitive files inside the web accessible folder. Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.}} It is adviced to only place the fcgi starter script, <code>.htaccess</code> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [[Managing_Cron_jobs | cronjob]] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than where it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django and Go examples below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <code>touch</code>: <pre>touch starter.fcgi</pre> Replace <code>starter.fcgi</code> with the name of your starter script. === Examples === ==== Python and Django ==== If you want to make a website using Python and [https://www.djangoproject.com/ Django], we recommend that you use a virtual environment. You can use the following steps to get up and running with Django on your ULYSSIS hosting account. <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <code>~/.venv</code>, for example: <pre>python3 -m venv ~/.venv</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django inside of this virtualenv: <pre>pip install django</pre> </li> <li> Create a new Django project: <pre>django-admin.py startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Install flup for FastCGI: <pre>pip install flup6</pre> </li> <li> Put an <code>.htaccess</code> file in your site's directory, e.g. the <code>www</code> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace <code>user</code> with org if you are an organization, and <code>username</code> with your ULYSSIS username): <syntaxhighlight lang="python">#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </syntaxhighlight> Call this script <code>mysite.fcgi</code>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [https://flask.palletsprojects.com/en/1.1.x/deploying/fastcgi/ Flask documentation for FastCGI] ==== Go ==== To make a website or web application in Go and host it on your ULYSSIS hosting account, you can use the standard library ''fcgi'' package. <ol> <li> [[Accessing shell servers over SSH|Log in to a shell server]]</li> <li> Put an <code>.htaccess</code> file in your site's directory (e.g. the <code>www</code> folder) with a reference to your executable. Here we've chosen <code>mysite.fcgi</code>, but you can adapt this to your liking. <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Write your code, and compile the binary to <code>mysite.fcgi</code>. Below you can find a basic example of how to register two handlers (of which one is the fallback), then start the FastCGI client, and finally have a function (which is called as a goroutine) to check if the binary has been replaced so old processes don't stick around. <syntaxhighlight lang="go">package main import ( "fmt" "net/http" "net/http/fcgi" "os" "path/filepath" "time" ) func uri_interesting(w http.ResponseWriter, r *http.Request) { w.WriteHeader(http.StatusOK) fmt.Fprintln(w, "<h1>Oh, seems like this link isn't that interesting after all</h1>") fmt.Fprintln(w, "<p>Back to the <a href=\"/\">Homepage</a></p>") } func uri_default(w http.ResponseWriter, r *http.Request) { if r.URL.Path != "/" { w.WriteHeader(http.StatusNotFound) fmt.Fprintln(w, "<h1>This page doesn't exist</h1>") fmt.Fprintln(w, "<p>Back to the <a href=\"/\">Homepage</a></p>") } else { w.WriteHeader(http.StatusOK) fmt.Fprintln(w, "<h1>Welcome to this testwebsite!</h1>") fmt.Fprintln(w, "<p>This website is written in Go but doesn't really do much.") fmt.Fprintln(w, "Feel free to visit this <a href=\"/interesting/link\">Interesting link</a> or this <a href=\"/non-existent/link\">non-existent link</a>.</p>") } } func main() { go check_selfreplacement() http.HandleFunc("/interesting/link", uri_interesting) http.HandleFunc("/", uri_default) if err := fcgi.Serve(nil, nil); err != nil { panic(err) } } func check_selfreplacement() { fcgi_location, _ := os.Executable() fcgi_location, _ = filepath.EvalSymlinks(fcgi_location) start_stat, _ := os.Stat(fcgi_location) for { current_stat, _ := os.Stat(fcgi_location) if start_stat.ModTime() != current_stat.ModTime() { os.Exit(0) } time.Sleep(1 * time.Second) } } </syntaxhighlight> If you want to give this example a try, save it as <code>mysite.fcgi.go</code> and then use <code>go build mysite.fcgi.go</code> to compile it. </li> <li>Visit your website to verify everything works</li> </ol> [[Category:Webserver]] 425dc9284161f661a58002215a8cc50307f149c9 0 5 1463 1244 2021-07-20T22:22:30Z Wtas 42 Completely overhauled the page wikitext text/x-wiki This documentation article will explain how to to upload, download, move and delete files on your account using a graphical user interface. If you are a more advanced user, you may want to use the command line to administer your files, in that case [[Accessing shell servers over SSH]] is probably a more relevant documentation page for you. Many different SFTP clients are available depending on your needs and what operating system you run on your computer. For Windows and Mac users, we recommend the graphical SFTP client [https://cyberduck.io/download/ Cyberduck]. If you're using Linux, your file manager usually has a built-in option to connect using the details mentioned in [[#Connecting | Connecting]]. ==Connecting== {{notice|Keep in mind|Our automatic security systems may temporarily prevent you from connecting over SSH/SFTP if you try to connect several times with the wrong username and/or password. This will result in the connection being refused. You can switch between sftp://ssh1.ulyssis.org and sftp://ssh2.ulyssis.org when this happens or wait 10 minutes. More information on our security measures is available on [[ULYSSIS security measures]]}} A Cybderduck-specific explanation can be found at [[#Connecting_2 | Cyberduck: Connecting]]. To access your files using another program you will have to enter the following connection details: * Protocol: SFTP * Server: "ssh1.ulyssis.org" or "ssh2.ulyssis.org" * Port: 22 * Username: your ULYSSIS account username, the one you use for [https://ucc.ulyssis.org ucc.ulyssis.org] * Password: your ULYSSIS account password On our servers, your files are stored in your home folder located at <code>/home/(group)/(username)/</code>, where the group depends upon your account type and the username is your ULYSSIS account username. Any regular user is stored within the <code>user</code> group, and their files are stored within <code>/home/user/(username)</code>. For organizations, <code>org</code> is used, so files are stored within <code>/home/org/(username)</code>. Most (S)FTP clients will by default display your own home folder after you've logged in. ==Using Cyberduck== To get started, download [https://cyberduck.io/download/ Cyberduck] from the official website. You can then install the downloaded file like you would install any other application. Once installed, launch Cyberduck and connect using the steps below. === Connecting === <ul> <li>Click on Open Connection in the top-left corner.</li> <li>Protocol (upper dropdown menu): "SFTP (SSH File Transfer Protocol)"</li> <li>Username: your ULYSSIS account username, the one you use for [https://ucc.ulyssis.org ucc.ulyssis.org]</li> <li>Password: your ULYSSIS account password</li> <li>Server: "ssh1.ulyssis.org" or "ssh2.ulyssis.org" <li>Enable "Save Password" if you don't want to enter your password every time you want to connect using this computer</li> <li>Press connect</li> </ul>[[File:Open-connection-WB.png|alt=|left|frame]] If you get a dialog window about an unknown fingerprint, tick the "Always" box in the bottom left and then click allow. You will now be connected and able to access your files. [[File:Fingerprint dialog window.png|none|alt=|frame]] When you connect to a server using Cyberduck, the remote files will appear: [[File:Cyberduck connection interface.png|none|alt=|frame]] ===Navigating=== You can open a folder by double-clicking it. To go back up one step you can press the "Up" button to the right of the "Current Folder" dropdown. To go back up multiple steps you can click on the "Current Folder" dropdown and select which folder you would like to go back to.[[File:Navigating-WB.png|none|alt=|frame]] ===Viewing hidden files=== To make hidden files, whose filename always start with a '.', visible, click on View -> Show Hidden Files. This is necessary because some files like ".htaccess" and ".user.ini" are hidden by default and they need to be edited sometimes. [[File:Hidden Files.png|none|thumb]] ===Uploading files and folders=== To upload a file or folder, you can use the "Upload" button in the top menu bar and select the file or folder you wish to upload using your file manager. [[File:Cyberduck-upload-button.png|alt=|frame|left]] Or you can drag and drop it from your file manager (Explorer for Windows, Finder for Mac) into the current folder in Cyberduck. [[File:Upload-drag-WB.png|none|alt=|thumb|514x514px]] ===Downloading files and folders=== To download files and folders, you can drag and drop it into your file manager (Explorer for Windows or Finder for Mac), just like uploading but in the other direction. For files specifically it's also possible to simply double-click the file. This will then download it to your Downloads folder. ===Creating and Deleting files and folders=== To create a folder, you right click where you want your folder to be located and then click the "New Folder" option as seen below. You can then type a name for your new folder. To create a file, you right click in the folder where you want your file to be located and then click the "New File" option as seen below. You can then type a name for your new file, making sure to include the necessary extension (eg. file.txt for a text file, file.php for a PHP file, etc.). You can delete a file or folder by selecting it and then either pressing the "Delete" key on your keyboard, or right-clicking and selecting "Delete". [[File:Delete-cyberduck-WB.png|alt=|thumb|384x384px|none]] ===Editing files=== Cyberduck allows you to edit files remotely by selecting a file and then pressing the "Edit" button in the top menu bar, next to the "Upload" button. This opens the file in your text editor (by default Notepad for Windows and TextEdit for Mac). After you're done editing, make sure to save the file using the text editor and then close it. [[File:Edit.png|none|alt=|frame]] [[Category:Files]] [[Category:Shell]] b058e95dcaa35d4785dedc351692c07a8f008ad4 1466 1463 2021-07-21T19:04:33Z Vincenttc 21 wikitext text/x-wiki This documentation article will explain how to to upload, download, move and delete files on your account using a graphical user interface. If you are a more advanced user, you may want to use the command line to administer your files, in that case [[Accessing shell servers over SSH]] is probably a more relevant documentation page for you. Many different SFTP clients are available depending on your needs and what operating system you run on your computer. For Windows and Mac users, we recommend the graphical SFTP client [https://cyberduck.io/download/ Cyberduck]. If you're using Linux, your file manager usually has a built-in option to connect using the details mentioned in [[#Connecting | Connecting]]. ==Connecting== {{notice|Keep in mind|Our automatic security systems may temporarily prevent you from connecting over SSH/SFTP if you try to connect several times with the wrong username and/or password. This will result in the connection being refused. You can switch between sftp://ssh1.ulyssis.org and sftp://ssh2.ulyssis.org when this happens or wait 10 minutes. More information on our security measures is available on [[ULYSSIS security measures]]}} A Cyderduck-specific explanation can be found at [[#Connecting_2 | Cyberduck: Connecting]]. To access your files using another program you will have to enter the following connection details: * Protocol: SFTP * Server: "ssh1.ulyssis.org" or "ssh2.ulyssis.org" * Port: 22 * Username: your ULYSSIS account username, the one you use for [https://ucc.ulyssis.org ucc.ulyssis.org] * Password: your ULYSSIS account password On our servers, your files are stored in your home folder located at <code>/home/(group)/(username)/</code>, where the group depends upon your account type and the username is your ULYSSIS account username. Any regular user is stored within the <code>user</code> group, and their files are stored within <code>/home/user/(username)</code>. For organizations, <code>org</code> is used, so files are stored within <code>/home/org/(username)</code>. Most (S)FTP clients will by default display your own home folder after you've logged in. ==Using Cyberduck== To get started, download [https://cyberduck.io/download/ Cyberduck] from the official website. You can then install the downloaded file like you would install any other application. Once installed, launch Cyberduck and connect using the steps below. === Connecting === <ul> <li>Click on Open Connection in the top-left corner.</li> <li>Protocol (upper dropdown menu): "SFTP (SSH File Transfer Protocol)"</li> <li>Username: your ULYSSIS account username, the one you use for [https://ucc.ulyssis.org ucc.ulyssis.org]</li> <li>Password: your ULYSSIS account password</li> <li>Server: "ssh1.ulyssis.org" or "ssh2.ulyssis.org" <li>Enable "Save Password" if you don't want to enter your password every time you want to connect using this computer</li> <li>Press connect</li> </ul>[[File:Open-connection-WB.png|alt=|left|frame]] If you get a dialog window about an unknown fingerprint, tick the "Always" box in the bottom left and then click allow. You will now be connected and able to access your files. [[File:Fingerprint dialog window.png|none|alt=|frame]] When you connect to a server using Cyberduck, the remote files will appear: [[File:Cyberduck connection interface.png|none|alt=|frame]] ===Navigating=== You can open a folder by double-clicking it. To go back up one step you can press the "Up" button to the right of the "Current Folder" dropdown. To go back up multiple steps you can click on the "Current Folder" dropdown and select which folder you would like to go back to.[[File:Navigating-WB.png|none|alt=|frame]] ===Viewing hidden files=== To make hidden files, whose filename always start with a '.', visible, click on View -> Show Hidden Files. This is necessary because some files like ".htaccess" and ".user.ini" are hidden by default and they need to be edited sometimes. [[File:Hidden Files.png|none|thumb]] ===Uploading files and folders=== To upload a file or folder, you can use the "Upload" button in the top menu bar and select the file or folder you wish to upload using your file manager. [[File:Cyberduck-upload-button.png|alt=|frame|left]] Or you can drag and drop it from your file manager (Explorer for Windows, Finder for Mac) into the current folder in Cyberduck. [[File:Upload-drag-WB.png|none|alt=|thumb|514x514px]] ===Downloading files and folders=== To download files and folders, you can drag and drop it into your file manager (Explorer for Windows or Finder for Mac), just like uploading but in the other direction. For files specifically it's also possible to simply double-click the file. This will then download it to your Downloads folder. ===Creating and Deleting files and folders=== To create a folder, you right click where you want your folder to be located and then click the "New Folder" option as seen below. You can then type a name for your new folder. To create a file, you right click in the folder where you want your file to be located and then click the "New File" option as seen below. You can then type a name for your new file, making sure to include the necessary extension (e.g. file.txt for a text file, file.php for a PHP file, etc.). You can delete a file or folder by selecting it and then either pressing the "Delete" key on your keyboard, or right-clicking and selecting "Delete". [[File:Delete-cyberduck-WB.png|alt=|thumb|384x384px|none]] ===Editing files=== Cyberduck allows you to edit files remotely by selecting a file and then pressing the "Edit" button in the top menu bar, next to the "Upload" button. This opens the file in your text editor (by default Notepad for Windows and TextEdit for Mac). After you're done editing, make sure to save the file using the text editor and then close it. [[File:Edit.png|none|alt=|frame]] [[Category:Files]] [[Category:Shell]] 70109ec34243242ac8cea9e296f2d8ca18e3309d 1467 1466 2021-07-21T19:19:01Z Bert 8 wikitext text/x-wiki This documentation article will explain how to to upload, download, move and delete files on your account using a graphical user interface. If you are a more advanced user, you may want to use the command line to administer your files, in that case [[Accessing shell servers over SSH]] is probably a more relevant documentation page for you. Many different SFTP clients are available depending on your needs and what operating system you run on your computer. For Windows and Mac users, we recommend the graphical SFTP client [https://cyberduck.io/download/ Cyberduck]. If you're using Linux, your file manager usually has a built-in option to connect using the details mentioned in [[#Connecting | Connecting]]. ==Connecting== {{notice|Keep in mind|Our automatic security systems may temporarily prevent you from connecting over SSH/SFTP if you try to connect several times with the wrong username and/or password. This will result in the connection being refused. You can switch between sftp://ssh1.ulyssis.org and sftp://ssh2.ulyssis.org when this happens or wait 10 minutes. More information on our security measures is available on [[ULYSSIS security measures]]}} A Cyberduck-specific explanation can be found at [[#Connecting_2 | Cyberduck: Connecting]]. To access your files using another program you will have to enter the following connection details: * Protocol: SFTP * Server: "ssh1.ulyssis.org" or "ssh2.ulyssis.org" * Port: 22 * Username: your ULYSSIS account username, the one you use for [https://ucc.ulyssis.org ucc.ulyssis.org] * Password: your ULYSSIS account password On our servers, your files are stored in your home folder located at <code>/home/(group)/(username)/</code>, where the group depends upon your account type and the username is your ULYSSIS account username. Any regular user is stored within the <code>user</code> group, and their files are stored within <code>/home/user/(username)</code>. For organizations, <code>org</code> is used, so files are stored within <code>/home/org/(username)</code>. Most (S)FTP clients will by default display your own home folder after you've logged in. ==Using Cyberduck== To get started, download [https://cyberduck.io/download/ Cyberduck] from the official website. You can then install the downloaded file like you would install any other application. Once installed, launch Cyberduck and connect using the steps below. === Connecting === <ul> <li>Click on Open Connection in the top-left corner.</li> <li>Protocol (upper dropdown menu): "SFTP (SSH File Transfer Protocol)"</li> <li>Username: your ULYSSIS account username, the one you use for [https://ucc.ulyssis.org ucc.ulyssis.org]</li> <li>Password: your ULYSSIS account password</li> <li>Server: "ssh1.ulyssis.org" or "ssh2.ulyssis.org" <li>Enable "Save Password" if you don't want to enter your password every time you want to connect using this computer</li> <li>Press connect</li> </ul>[[File:Open-connection-WB.png|alt=|left|frame]] If you get a dialog window about an unknown fingerprint, tick the "Always" box in the bottom left and then click allow. You will now be connected and able to access your files. [[File:Fingerprint dialog window.png|none|alt=|frame]] When you connect to a server using Cyberduck, the remote files will appear: [[File:Cyberduck connection interface.png|none|alt=|frame]] ===Navigating=== You can open a folder by double-clicking it. To go back up one step you can press the "Up" button to the right of the "Current Folder" dropdown. To go back up multiple steps you can click on the "Current Folder" dropdown and select which folder you would like to go back to.[[File:Navigating-WB.png|none|alt=|frame]] ===Viewing hidden files=== To make hidden files, whose filename always start with a '.', visible, click on View -> Show Hidden Files. This is necessary because some files like ".htaccess" and ".user.ini" are hidden by default and they need to be edited sometimes. [[File:Hidden Files.png|none|thumb]] ===Uploading files and folders=== To upload a file or folder, you can use the "Upload" button in the top menu bar and select the file or folder you wish to upload using your file manager. [[File:Cyberduck-upload-button.png|alt=|frame|left]] Or you can drag and drop it from your file manager (Explorer for Windows, Finder for Mac) into the current folder in Cyberduck. [[File:Upload-drag-WB.png|none|alt=|thumb|514x514px]] ===Downloading files and folders=== To download files and folders, you can drag and drop it into your file manager (Explorer for Windows or Finder for Mac), just like uploading but in the other direction. For files specifically it's also possible to simply double-click the file. This will then download it to your Downloads folder. ===Creating and Deleting files and folders=== To create a folder, you right click where you want your folder to be located and then click the "New Folder" option as seen below. You can then type a name for your new folder. To create a file, you right click in the folder where you want your file to be located and then click the "New File" option as seen below. You can then type a name for your new file, making sure to include the necessary extension (e.g. file.txt for a text file, file.php for a PHP file, etc.). You can delete a file or folder by selecting it and then either pressing the "Delete" key on your keyboard, or right-clicking and selecting "Delete". [[File:Delete-cyberduck-WB.png|alt=|thumb|384x384px|none]] ===Editing files=== Cyberduck allows you to edit files remotely by selecting a file and then pressing the "Edit" button in the top menu bar, next to the "Upload" button. This opens the file in your text editor (by default Notepad for Windows and TextEdit for Mac). After you're done editing, make sure to save the file using the text editor and then close it. [[File:Edit.png|none|alt=|frame]] [[Category:Files]] [[Category:Shell]] 93bedfb5e98274c4ee5d4bedcce92215de57b3f9 0 57 1470 1304 2021-08-01T13:14:42Z Casper 39 wikitext text/x-wiki == Restricting spam == By default, Joomla has no option no enable comments, contacts or user registrations. Most of these options are managed through Joomla plugins/extensions. These extensions will allow by default that any user (or bot) can make comments, register an account, etc. To prevent these people or bots attacking your website, a few steps can be taken that are listed below. ==Detecting spam== === R Antispam === R Antispam is an extension for Joomla that works via the Bayesian algorithm to prevent spam on your Joomla website. It can protect you from spam on many different forms. On top of that, the extension is free to download and use. To use R Antispam follow these instructions: * Go to https://extensions.joomla.org/extension/r-antispam/ and press the download button on the right side, to start downloading the extension * Go to the admin panel on your Joomla website * On the top of this page select the tab "Extensions" -> "Manage" -> "Install" * Press the green "Browse for files"-button, and select the .zip file you just downloaded in the first step * Now your plugin should be installed, but to make sure that it is working and active go to the tab "Extensions" -> "Manage" -> "Manage" * This will give you a list of all installed plugins. Now search for the R Antispam plugin and make sure that the status says active (a green V is shown) Now the plugin is working and spam can be prevented. ===Google's reCAPTCHA=== CAPTCHA, originally from a complicated acronym, is a term used for different kinds of challenges to prevent automated scripts from trying to comment, register or login on websites. reCAPTCHA is a project owned by Google that is quite successful at designing these challenges. You probably know reCAPTCHA as the "I'm not a robot" checkbox you often have to press. More details are available on <nowiki>https://google.com/recaptcha</nowiki> To use Google's reCAPTCHA follow these instructions: * Go to google's reCAPTCHA administrator page(https://www.google.com/recaptcha/admin) and register your site * Navigate to the admin panel of your Joomla installation and select the tab "Extensions" -> "Plugins" * Search for 'recaptcha' in the search box and enable the "CAPTCHA - reCAPTCHA"-plugin by clicking on the status icon next to the name * Once complete it is '''critical''' that you configure your reCAPTCHA properly ** Go to reCAPTCHA's configuration page by clicking the plugin's name in the same panel where you enabled it ** Now fill in the required keys you got on google's reCAPTCHA's administrator page before ** When finished entering these keys, press the "Save & Close" button to save your settings From now on, when for example registering an account, Joomla will ask to fill in a reCAPTCHA [[Category:Security & anti-spam]] [[Category:CMSs]] 573a52b1ebea9ba25daf5d3ee9c0777fe2995e2e 1471 1470 2021-08-01T13:16:24Z Casper 39 /* Detecting spam */ wikitext text/x-wiki == Restricting spam == By default, Joomla has no option no enable comments, contacts or user registrations. Most of these options are managed through Joomla plugins/extensions. These extensions will allow by default that any user (or bot) can make comments, register an account, etc. To prevent these people or bots attacking your website, a few steps can be taken that are listed below. It can be the better option to completely restricts comments and any forms of contacts, but of course this is not always possible. ==Detecting spam== As mentioned above, it's better in most cases to simply not allow comments or to restrict them very heavily than having to deal with spam. If you have no other choice, there are some options available to help you out. It's important to keep in mind that both options below rely on external service providers for some aspects of their spam detection. === R Antispam === R Antispam is an extension for Joomla that works via the Bayesian algorithm to prevent spam on your Joomla website. It can protect you from spam on many different forms. On top of that, the extension is free to download and use. To use R Antispam follow these instructions: * Go to https://extensions.joomla.org/extension/r-antispam/ and press the download button on the right side, to start downloading the extension * Go to the admin panel on your Joomla website * On the top of this page select the tab "Extensions" -> "Manage" -> "Install" * Press the green "Browse for files"-button, and select the .zip file you just downloaded in the first step * Now your plugin should be installed, but to make sure that it is working and active go to the tab "Extensions" -> "Manage" -> "Manage" * This will give you a list of all installed plugins. Now search for the R Antispam plugin and make sure that the status says active (a green V is shown) Now the plugin is working and spam can be prevented. ===Google's reCAPTCHA=== CAPTCHA, originally from a complicated acronym, is a term used for different kinds of challenges to prevent automated scripts from trying to comment, register or login on websites. reCAPTCHA is a project owned by Google that is quite successful at designing these challenges. You probably know reCAPTCHA as the "I'm not a robot" checkbox you often have to press. More details are available on <nowiki>https://google.com/recaptcha</nowiki> To use Google's reCAPTCHA follow these instructions: * Go to google's reCAPTCHA administrator page(https://www.google.com/recaptcha/admin) and register your site * Navigate to the admin panel of your Joomla installation and select the tab "Extensions" -> "Plugins" * Search for 'recaptcha' in the search box and enable the "CAPTCHA - reCAPTCHA"-plugin by clicking on the status icon next to the name * Once complete it is '''critical''' that you configure your reCAPTCHA properly ** Go to reCAPTCHA's configuration page by clicking the plugin's name in the same panel where you enabled it ** Now fill in the required keys you got on google's reCAPTCHA's administrator page before ** When finished entering these keys, press the "Save & Close" button to save your settings From now on, when for example registering an account, Joomla will ask to fill in a reCAPTCHA [[Category:Security & anti-spam]] [[Category:CMSs]] 5713b24677170f40db32c291e80b2094e8aa14d3 0 198 1473 2021-08-02T18:50:32Z Casper 39 Casper moved page [[KULoket agenda iCal feed]] to [[Exporting your KU Leuven class schedule and calendar]] wikitext text/x-wiki #REDIRECT [[Exporting your KU Leuven class schedule and calendar]] ddee04fe232c75a42d6d7198c24fc9a0d00e2f49 6 199 1474 2021-08-02T19:18:44Z Casper 39 wikitext text/x-wiki agendasettings4 5d45e2e2576c4a907daa3aa8f0f7de5653a256c1 0 3 1478 1327 2021-08-02T19:22:07Z Casper 39 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Reducing disk usage|Help, my account uses too much disk space]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Using SSHFS]] * [[Making Backups]] * [[Secure file permissions]] * [[Reducing disk usage]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2020]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Sending email from websites]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL/TLS|Getting SSL/TLS (HTTPS security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Claiming a port]] * [[ULYSSIS security measures]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] * [[Spam]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up WordPress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] * [[Updating WordPress]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] * [[Using PHPPgAdmin]] * [[Using Adminer]] * [[Making Backups]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[Exporting your KU Leuven class schedule and calendar]] </div> <div style="clear:both;"></div> </div> __NOTOC__ a34539b3d6edc0470c07bbe974a3e0de0dcd08b3 0 176 1479 1375 2021-08-03T20:25:17Z Yoa 30 Remove refresh instructions wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. If you arrived at this page after receiving an email from our [[Software Version Checker]]. This email might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can find your current MediaWiki version by going to the <code>Special:Version#Installed_software</code> page on your wiki. For example, for this wiki, you can find the current version at [[Special:Version#Installed_software]]. A table of all recent MediaWiki versions can be found on the [https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life the official table]. In this table, currently supported versions are in '''bold'''. Click on the link of the version you want to download (if you need to choose a version, make sure to choose a supported, newer, preferably LTS version). This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-xxx.tar.gz</code>. Download this file and save it somewhere on your PC. == Making a backup == An important step in the update process is to create a backup of your data on the ULYSSIS server, to prevent data loss if something goes wrong. Additionally, this backup will be used to copy files from your old installation to the new installation. Consequently, '''this step is mandatory'''. The easiest way to create a backup is to '''rename''' the directory containing your <code>LocalSettings.php</code> configuration file (your wiki location) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_backup</code>, or something similar. == Installing the new files == Now, you will need to upload the <code>mediawiki-xxx.tar.gz</code> file you downloaded in step 1 to the same path as where your wiki backup directory is located. For example, if your wiki backup directory is located in <code>www/wiki_backup</code>, upload <code>mediawiki-xxx.tar.gz</code> to <code>www/</code>. After uploading, you can extract the file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the file and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-xxx</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * In case you use a custom logo or favicon, this file also needs to be restored from backup. You can find the locations of these files by checking the <code>$wgLogo</code> and <code>$wgFavicon</code> values in <code>LocalSettings.php</code>. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any modifications made to the old installation files, extensions, or skins. For example, this includes miscellaneous modifications to the configuration of extensions or skins. * Any <code>.htaccess</code> file, if present. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box: php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the backup installation: for example, if your backup is stored in <code>www/wiki_backup</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. de46219b4f0b3e46a56a65061973216fbf9e7908 1481 1479 2021-08-03T21:32:09Z Yoa 30 wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. {{info|In this guide, we assume you are familiar with the files on your ULYSSIS account. If you don't know how to access these files, please read [[Accessing your files]] first.}} == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. If you arrived at this page after receiving an email from our [[Software Version Checker]], follow the instructions in the next paragraph. Otherwise, you can skip the next paragraph. The email you received might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can find your current MediaWiki version by going to the <code>Special:Version</code> page on your wiki (simply paste this in the search box) and looking for the "MediaWiki" version under "Installed software". For example, for this wiki, you can find the current version at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed software.png|center|frame]] A table of all recent MediaWiki versions can be found on the [https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life the official table]. In this table, currently supported versions are in '''bold'''. Click on the link of the version you want to download (if you need to choose a version, make sure to choose a supported, newer, preferably LTS version). This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-xxx.tar.gz</code>. Download this file and save it somewhere on your PC. == Renaming the old installation == An important step in the update process is to rename the old installation directory. This way, you can simply copy your data from the old installation directory to the new installation directory during the update. Additionally, you can easily restore your old wiki if something goes wrong. The easiest way to do this, is to '''rename''' your wiki location (the directory containing your <code>LocalSettings.php</code> configuration file) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_old</code>, or something similar. == Installing the new files == Now, you will need to upload the <code>mediawiki-xxx.tar.gz</code> file you downloaded in step 1 next to the old installation directory. For example, if your old installation directory is located in <code>www/wiki_old</code>, upload <code>mediawiki-xxx.tar.gz</code> to <code>www/</code>. After uploading, you can extract the file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the file and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-xxx</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * In case you use a custom logo or favicon, this file also needs to be restored from the old installation. You can find the locations of these files by checking the <code>$wgLogo</code> and <code>$wgFavicon</code> values in <code>LocalSettings.php</code>. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any <code>.htaccess</code> file, if present. '''Make sure you can view hidden files'''; to enable this for Cyberduck, you can look at [[Accessing_your_files#Viewing_hidden_files|Accessing your files]]. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. For example, you might have the ULYSSIS extensions [[Securing MediaWiki using Centrale KU Leuven Login|MediaWikiShibboleth]] or [https://github.com/ULYSSIS-KUL/CompressUploads CompressUploads] installed. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box: php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the old installation: for example, if this is stored in <code>www/wiki_old</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing_your_files#Creating_and_Deleting_files_and_folders|Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. 46de932ee2d1438f1abaace6310d594efc5333ee 1489 1481 2021-08-04T21:18:22Z Yoa 30 /* Downloading the latest version */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. {{info|In this guide, we assume you are familiar with the files on your ULYSSIS account. If you don't know how to access these files, please read [[Accessing your files]] first.}} == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. If you arrived at this page after receiving an email from our [[Software Version Checker]], follow the instructions in the next paragraph. Otherwise, you can skip the next paragraph. The email you received might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can find your current MediaWiki version by going to the <code>Special:Version</code> page on your wiki (simply paste this in the search box) and looking for the "MediaWiki" version under "Installed software". For example, for this wiki, you can find the current version at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed software.png|center|frame]] A table of all recent MediaWiki versions can be found on the [https://en.wikipedia.org/wiki/MediaWiki_version_history the official table]. Currently supported versions are indicated by a green or yellow color in the first column. To determine which version you want to download, follow these steps: * If the ''branch'' of your version (the first two numbers, like 1.xx) is currently supported (green or yellow), you should choose the latest version for this branch. For example, for version 1.35.2, the branch is 1.35. * If this branch is not supported anymore, you should choose the most recent LTS branch. This is indicated by '''(LTS)''' in the second column. * If the most recent LTS branch is older than your current branch, you should download the most recent supported branch (in green). Now, click on the link of the branch you want to download. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-1.xx.y.tar.gz</code>. Download this file and save it somewhere on your PC. == Renaming the old installation == An important step in the update process is to rename the old installation directory. This way, you can simply copy your data from the old installation directory to the new installation directory during the update. Additionally, you can easily restore your old wiki if something goes wrong. The easiest way to do this, is to '''rename''' your wiki location (the directory containing your <code>LocalSettings.php</code> configuration file) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_old</code>, or something similar. == Installing the new files == Now, you will need to upload the <code>mediawiki-xxx.tar.gz</code> file you downloaded in step 1 next to the old installation directory. For example, if your old installation directory is located in <code>www/wiki_old</code>, upload <code>mediawiki-xxx.tar.gz</code> to <code>www/</code>. After uploading, you can extract the file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the file and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-xxx</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * In case you use a custom logo or favicon, this file also needs to be restored from the old installation. You can find the locations of these files by checking the <code>$wgLogo</code> and <code>$wgFavicon</code> values in <code>LocalSettings.php</code>. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any <code>.htaccess</code> file, if present. '''Make sure you can view hidden files'''; to enable this for Cyberduck, you can look at [[Accessing_your_files#Viewing_hidden_files|Accessing your files]]. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. For example, you might have the ULYSSIS extensions [[Securing MediaWiki using Centrale KU Leuven Login|MediaWikiShibboleth]] or [https://github.com/ULYSSIS-KUL/CompressUploads CompressUploads] installed. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box: php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the old installation: for example, if this is stored in <code>www/wiki_old</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing_your_files#Creating_and_Deleting_files_and_folders|Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. e2d8331c2cab0f1a1d8048ad5483b40431f59abe 1490 1489 2021-08-04T21:19:18Z Yoa 30 /* Downloading the latest version */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. {{info|In this guide, we assume you are familiar with the files on your ULYSSIS account. If you don't know how to access these files, please read [[Accessing your files]] first.}} == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. If you arrived at this page after receiving an email from our [[Software Version Checker]], follow the instructions in the next paragraph. Otherwise, you can skip the next paragraph. The email you received might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can find your current MediaWiki version by going to the <code>Special:Version</code> page on your wiki (simply paste this in the search box) and looking for the "MediaWiki" version under "Installed software". For example, for this wiki, you can find the current version at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed software.png|center|frame]] A table of all recent MediaWiki versions can be found on the [https://en.wikipedia.org/wiki/MediaWiki_version_history the official table]. Currently supported versions are indicated by a green or yellow color in the first column. To determine which version you want to download, follow these steps: * If the ''branch'' of your version (the first two numbers, like 1.xx) is currently supported (green or yellow), you should choose the latest version for this branch. For example, for version 1.35.2, the branch is 1.35. * If this branch is not supported anymore, you should choose the most recent LTS branch. This is indicated by '''(LTS)''' in the second column. * If the most recent LTS branch is older than your current branch, you should choose the newest supported branch (green). Now, click on the link of the branch you want to download. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-1.xx.y.tar.gz</code>. Download this file and save it somewhere on your PC. == Renaming the old installation == An important step in the update process is to rename the old installation directory. This way, you can simply copy your data from the old installation directory to the new installation directory during the update. Additionally, you can easily restore your old wiki if something goes wrong. The easiest way to do this, is to '''rename''' your wiki location (the directory containing your <code>LocalSettings.php</code> configuration file) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_old</code>, or something similar. == Installing the new files == Now, you will need to upload the <code>mediawiki-xxx.tar.gz</code> file you downloaded in step 1 next to the old installation directory. For example, if your old installation directory is located in <code>www/wiki_old</code>, upload <code>mediawiki-xxx.tar.gz</code> to <code>www/</code>. After uploading, you can extract the file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the file and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-xxx</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * In case you use a custom logo or favicon, this file also needs to be restored from the old installation. You can find the locations of these files by checking the <code>$wgLogo</code> and <code>$wgFavicon</code> values in <code>LocalSettings.php</code>. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any <code>.htaccess</code> file, if present. '''Make sure you can view hidden files'''; to enable this for Cyberduck, you can look at [[Accessing_your_files#Viewing_hidden_files|Accessing your files]]. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. For example, you might have the ULYSSIS extensions [[Securing MediaWiki using Centrale KU Leuven Login|MediaWikiShibboleth]] or [https://github.com/ULYSSIS-KUL/CompressUploads CompressUploads] installed. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box: php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the old installation: for example, if this is stored in <code>www/wiki_old</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing_your_files#Creating_and_Deleting_files_and_folders|Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. 62c822f22555549b9ad664afb6e32042b72d3c10 1491 1490 2021-08-04T21:19:37Z Yoa 30 /* Downloading the latest version */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. {{info|In this guide, we assume you are familiar with the files on your ULYSSIS account. If you don't know how to access these files, please read [[Accessing your files]] first.}} == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. If you arrived at this page after receiving an email from our [[Software Version Checker]], follow the instructions in the next paragraph. Otherwise, you can skip the next paragraph. The email you received might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can find your current MediaWiki version by going to the <code>Special:Version</code> page on your wiki (simply paste this in the search box) and looking for the "MediaWiki" version under "Installed software". For example, for this wiki, you can find the current version at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed software.png|center|frame]] A table of all recent MediaWiki versions can be found on the [https://en.wikipedia.org/wiki/MediaWiki_version_history the official table]. Currently supported versions are indicated by a green or yellow color in the first column. To determine which version you want to download, follow these steps: * If the ''branch'' of your version (the first two numbers, like 1.xx) is currently supported (green or yellow), you should choose the latest version for this branch. For example, for version 1.35.2, the branch is 1.35. * If this branch is not supported anymore, you should choose the most recent LTS branch. This is indicated by '''(LTS)''' in the second column. * If the most recent LTS branch is older than your current branch, you should choose the newest supported branch (green). Now, click on the link of the branch you want to download. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-xxx.tar.gz</code>. Download this file and save it somewhere on your PC. == Renaming the old installation == An important step in the update process is to rename the old installation directory. This way, you can simply copy your data from the old installation directory to the new installation directory during the update. Additionally, you can easily restore your old wiki if something goes wrong. The easiest way to do this, is to '''rename''' your wiki location (the directory containing your <code>LocalSettings.php</code> configuration file) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_old</code>, or something similar. == Installing the new files == Now, you will need to upload the <code>mediawiki-xxx.tar.gz</code> file you downloaded in step 1 next to the old installation directory. For example, if your old installation directory is located in <code>www/wiki_old</code>, upload <code>mediawiki-xxx.tar.gz</code> to <code>www/</code>. After uploading, you can extract the file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the file and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-xxx</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * In case you use a custom logo or favicon, this file also needs to be restored from the old installation. You can find the locations of these files by checking the <code>$wgLogo</code> and <code>$wgFavicon</code> values in <code>LocalSettings.php</code>. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any <code>.htaccess</code> file, if present. '''Make sure you can view hidden files'''; to enable this for Cyberduck, you can look at [[Accessing_your_files#Viewing_hidden_files|Accessing your files]]. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. For example, you might have the ULYSSIS extensions [[Securing MediaWiki using Centrale KU Leuven Login|MediaWikiShibboleth]] or [https://github.com/ULYSSIS-KUL/CompressUploads CompressUploads] installed. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box: php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the old installation: for example, if this is stored in <code>www/wiki_old</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing_your_files#Creating_and_Deleting_files_and_folders|Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. 82797b3895e3ffac462c27578214bcd730097e2e 1492 1491 2021-08-04T21:20:04Z Yoa 30 /* Downloading the latest version */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. {{info|In this guide, we assume you are familiar with the files on your ULYSSIS account. If you don't know how to access these files, please read [[Accessing your files]] first.}} == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. If you arrived at this page after receiving an email from our [[Software Version Checker]], follow the instructions in the next paragraph. Otherwise, you can skip the next paragraph. The email you received might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can find your current MediaWiki version by going to the <code>Special:Version</code> page on your wiki (simply paste this in the search box) and looking for the "MediaWiki" version under "Installed software". For example, for this wiki, you can find the current version at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed software.png|center|frame]] A table of all recent MediaWiki versions can be found on the [https://en.wikipedia.org/wiki/MediaWiki_version_history the official table]. Currently supported versions are indicated by a green or yellow color in the first column. To determine which version you want to download, follow these steps: * If the ''branch'' of your version ('''the first two numbers''', like <code>1.xx</code>) is currently supported (green or yellow), you should choose the latest version for this branch. For example, for version 1.35.2, the branch is 1.35. * If this branch is not supported anymore, you should choose the most recent LTS branch. This is indicated by '''(LTS)''' in the second column. * If the most recent LTS branch is older than your current branch, you should choose the newest supported branch (green). Now, click on the link of the branch you want to download. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-xxx.tar.gz</code>. Download this file and save it somewhere on your PC. == Renaming the old installation == An important step in the update process is to rename the old installation directory. This way, you can simply copy your data from the old installation directory to the new installation directory during the update. Additionally, you can easily restore your old wiki if something goes wrong. The easiest way to do this, is to '''rename''' your wiki location (the directory containing your <code>LocalSettings.php</code> configuration file) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_old</code>, or something similar. == Installing the new files == Now, you will need to upload the <code>mediawiki-xxx.tar.gz</code> file you downloaded in step 1 next to the old installation directory. For example, if your old installation directory is located in <code>www/wiki_old</code>, upload <code>mediawiki-xxx.tar.gz</code> to <code>www/</code>. After uploading, you can extract the file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the file and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-xxx</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-xxx</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * In case you use a custom logo or favicon, this file also needs to be restored from the old installation. You can find the locations of these files by checking the <code>$wgLogo</code> and <code>$wgFavicon</code> values in <code>LocalSettings.php</code>. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any <code>.htaccess</code> file, if present. '''Make sure you can view hidden files'''; to enable this for Cyberduck, you can look at [[Accessing_your_files#Viewing_hidden_files|Accessing your files]]. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. For example, you might have the ULYSSIS extensions [[Securing MediaWiki using Centrale KU Leuven Login|MediaWikiShibboleth]] or [https://github.com/ULYSSIS-KUL/CompressUploads CompressUploads] installed. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box: php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the old installation: for example, if this is stored in <code>www/wiki_old</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing_your_files#Creating_and_Deleting_files_and_folders|Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. 748642f245d7ae096ad26201b9066787600a394d 1493 1492 2021-08-04T21:20:46Z Yoa 30 wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. {{info|In this guide, we assume you are familiar with the files on your ULYSSIS account. If you don't know how to access these files, please read [[Accessing your files]] first.}} == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. If you arrived at this page after receiving an email from our [[Software Version Checker]], follow the instructions in the next paragraph. Otherwise, you can skip the next paragraph. The email you received might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can find your current MediaWiki version by going to the <code>Special:Version</code> page on your wiki (simply paste this in the search box) and looking for the "MediaWiki" version under "Installed software". For example, for this wiki, you can find the current version at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed software.png|center|frame]] A table of all recent MediaWiki versions can be found on the [https://en.wikipedia.org/wiki/MediaWiki_version_history the official table]. Currently supported versions are indicated by a green or yellow color in the first column. To determine which version you want to download, follow these steps: * If the ''branch'' of your version ('''the first two numbers''', like <code>1.xx</code>) is currently supported (green or yellow), you should choose the latest version for this branch. For example, for version 1.35.2, the branch is 1.35. * If this branch is not supported anymore, you should choose the most recent LTS branch. This is indicated by '''(LTS)''' in the second column. * If the most recent LTS branch is older than your current branch, you should choose the newest supported branch (green). Now, click on the link of the branch you want to download. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-1.xx.y.tar.gz</code>. Download this file and save it somewhere on your PC. == Renaming the old installation == An important step in the update process is to rename the old installation directory. This way, you can simply copy your data from the old installation directory to the new installation directory during the update. Additionally, you can easily restore your old wiki if something goes wrong. The easiest way to do this, is to '''rename''' your wiki location (the directory containing your <code>LocalSettings.php</code> configuration file) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_old</code>, or something similar. == Installing the new files == Now, you will need to upload the <code>mediawiki-1.xx.y.tar.gz</code> file you downloaded in step 1 next to the old installation directory. For example, if your old installation directory is located in <code>www/wiki_old</code>, upload <code>mediawiki-1.xx.y.tar.gz</code> to <code>www/</code>. After uploading, you can extract the file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the file and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-1.xx.y</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-1.xx.y</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * In case you use a custom logo or favicon, this file also needs to be restored from the old installation. You can find the locations of these files by checking the <code>$wgLogo</code> and <code>$wgFavicon</code> values in <code>LocalSettings.php</code>. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any <code>.htaccess</code> file, if present. '''Make sure you can view hidden files'''; to enable this for Cyberduck, you can look at [[Accessing_your_files#Viewing_hidden_files|Accessing your files]]. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. For example, you might have the ULYSSIS extensions [[Securing MediaWiki using Centrale KU Leuven Login|MediaWikiShibboleth]] or [https://github.com/ULYSSIS-KUL/CompressUploads CompressUploads] installed. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box: php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the old installation: for example, if this is stored in <code>www/wiki_old</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing_your_files#Creating_and_Deleting_files_and_folders|Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. 7cd9d636eaec54b81a7345a3361f50758ea5622a 1494 1493 2021-08-04T21:21:22Z Yoa 30 wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. {{info|In this guide, we assume you are familiar with the files on your ULYSSIS account. If you don't know how to access these files, please read [[Accessing your files]] first.}} == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. If you arrived at this page after receiving an email from our [[Software Version Checker]], follow the instructions in the next paragraph. Otherwise, you can skip the next paragraph. The email you received might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can find your current MediaWiki version by going to the <code>Special:Version</code> page on your wiki (simply paste this in the search box) and looking for the "MediaWiki" version under "Installed software". For example, for this wiki, you can find the current version at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed software.png|center|frame]] A table of all recent MediaWiki versions can be found on the [https://en.wikipedia.org/wiki/MediaWiki_version_history the official table]. Currently supported versions are indicated by a green or yellow color in the first column. To determine which version you want to download, follow these steps: * If the ''branch'' of your version ('''the first two numbers''', like <code>1.xx</code>) is currently supported (green or yellow), you should choose the latest version for this branch. For example, for version 1.35.2, the branch is 1.35. * If this branch is not supported anymore, you should choose the most recent LTS branch. This is indicated by '''(LTS)''' in the second column. * If the most recent LTS branch is older than your current branch, you should choose the newest supported branch (green). Now, click on the link of the branch you want to download. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-1.xx.yy.tar.gz</code>. Download this file and save it somewhere on your PC. == Renaming the old installation == An important step in the update process is to rename the old installation directory. This way, you can simply copy your data from the old installation directory to the new installation directory during the update. Additionally, you can easily restore your old wiki if something goes wrong. The easiest way to do this, is to '''rename''' your wiki location (the directory containing your <code>LocalSettings.php</code> configuration file) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_old</code>, or something similar. == Installing the new files == Now, you will need to upload the <code>mediawiki-1.xx.yy.tar.gz</code> file you downloaded in step 1 next to the old installation directory. For example, if your old installation directory is located in <code>www/wiki_old</code>, upload <code>mediawiki-1.xx.yy.tar.gz</code> to <code>www/</code>. After uploading, you can extract the file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the file and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-1.xx.yy</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-1.xx.yy</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * In case you use a custom logo or favicon, this file also needs to be restored from the old installation. You can find the locations of these files by checking the <code>$wgLogo</code> and <code>$wgFavicon</code> values in <code>LocalSettings.php</code>. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any <code>.htaccess</code> file, if present. '''Make sure you can view hidden files'''; to enable this for Cyberduck, you can look at [[Accessing_your_files#Viewing_hidden_files|Accessing your files]]. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. For example, you might have the ULYSSIS extensions [[Securing MediaWiki using Centrale KU Leuven Login|MediaWikiShibboleth]] or [https://github.com/ULYSSIS-KUL/CompressUploads CompressUploads] installed. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box: php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the old installation: for example, if this is stored in <code>www/wiki_old</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing_your_files#Creating_and_Deleting_files_and_folders|Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. 0bbe1e0dee912a7e3eec5ed8562f71bb5f678e86 1495 1494 2021-08-04T21:21:57Z Yoa 30 /* Downloading the latest version */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. {{info|In this guide, we assume you are familiar with the files on your ULYSSIS account. If you don't know how to access these files, please read [[Accessing your files]] first.}} == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. If you arrived at this page after receiving an email from our [[Software Version Checker]], follow the instructions in the next paragraph. Otherwise, you can skip the next paragraph. The email you received might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can find your current MediaWiki version by going to the <code>Special:Version</code> page on your wiki (simply paste this in the search box) and looking for the "MediaWiki" version under "Installed software". For example, for this wiki, you can find the current version at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed software.png|center|frame]] A table of all recent MediaWiki versions can be found on the [https://en.wikipedia.org/wiki/MediaWiki_version_history the official table]. Currently supported versions are indicated by a green or yellow color in the first column. To determine which version you want to download, follow these steps: * If the ''branch'' of your version ('''the first two numbers''', like <code>1.xx</code>) is currently supported (green or yellow), you should choose the latest version for this branch. For example, for version 1.35.3, the branch is 1.35. * If this branch is not supported anymore, you should choose the most recent LTS branch. This is indicated by '''(LTS)''' in the second column. * If the most recent LTS branch is older than your current branch, you should choose the newest supported branch (green). Now, click on the link of the branch you want to download. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-1.xx.yy.tar.gz</code>. Download this file and save it somewhere on your PC. == Renaming the old installation == An important step in the update process is to rename the old installation directory. This way, you can simply copy your data from the old installation directory to the new installation directory during the update. Additionally, you can easily restore your old wiki if something goes wrong. The easiest way to do this, is to '''rename''' your wiki location (the directory containing your <code>LocalSettings.php</code> configuration file) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_old</code>, or something similar. == Installing the new files == Now, you will need to upload the <code>mediawiki-1.xx.yy.tar.gz</code> file you downloaded in step 1 next to the old installation directory. For example, if your old installation directory is located in <code>www/wiki_old</code>, upload <code>mediawiki-1.xx.yy.tar.gz</code> to <code>www/</code>. After uploading, you can extract the file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the file and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-1.xx.yy</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-1.xx.yy</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * In case you use a custom logo or favicon, this file also needs to be restored from the old installation. You can find the locations of these files by checking the <code>$wgLogo</code> and <code>$wgFavicon</code> values in <code>LocalSettings.php</code>. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any <code>.htaccess</code> file, if present. '''Make sure you can view hidden files'''; to enable this for Cyberduck, you can look at [[Accessing_your_files#Viewing_hidden_files|Accessing your files]]. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. For example, you might have the ULYSSIS extensions [[Securing MediaWiki using Centrale KU Leuven Login|MediaWikiShibboleth]] or [https://github.com/ULYSSIS-KUL/CompressUploads CompressUploads] installed. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box: php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the old installation: for example, if this is stored in <code>www/wiki_old</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing_your_files#Creating_and_Deleting_files_and_folders|Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. 2bb7ea8698271b9bb00e9c3c3a33545e4869d731 6 200 1480 2021-08-03T20:31:53Z Yoa 30 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 201 1482 2021-08-04T00:36:22Z Thomasd 40 wikitext text/x-wiki First Cyberduck screenshot for Getting Apache Logs 107adc0111d20dfd7711c45b434606b495e80630 6 202 1483 2021-08-04T00:39:18Z Thomasd 40 wikitext text/x-wiki Second Cyberduck screenshot for Getting Apache Logs 38ea25cbda5d6ce7c74c4a163ae2d519b724d50a 1485 1483 2021-08-04T00:48:46Z Thomasd 40 Thomasd uploaded a new version of [[File:Getting Apache Logs - Cyberduck 2.png]] wikitext text/x-wiki Second Cyberduck screenshot for Getting Apache Logs 38ea25cbda5d6ce7c74c4a163ae2d519b724d50a 6 203 1484 2021-08-04T00:41:02Z Thomasd 40 wikitext text/x-wiki Third Cyberduck screenshot for Getting Apache Logs d3b7e18a772c16be145b99f8074e2dea1c373bc1 0 9 1486 1275 2021-08-04T00:52:03Z Thomasd 40 Filezilla -> Cyberduck, gooi volgorde om wikitext text/x-wiki You can find all your Apache logs (like access.log and error.log) on all of our shell servers in the directory <code>/var/log/apache_user/''username''</code>. For more general information on how to access your files, please visit [[Accessing your files]]. ==Using Cyberduck== You can access the log files using an SFTP client like Cyberduck. Click on "Go" on the top bar and then click "Go to Folder...": [[File:Getting Apache Logs - Cyberduck 1.png]] Then enter <code>/var/log/apache_user/''username''</code> as path name (replace ''username'' with your own username): [[File:Getting Apache Logs - Cyberduck 2.png]] After pressing "Go", you will see a directory for each of your websites, containing their Apache logs. [[File:Getting Apache Logs - Cyberduck 3.png]] ==Using the command line== You can also access your logs by [[Accessing shell servers over SSH|logging in to one of our shell servers over SSH]] and navigating to the correct directory: username@ssh1:~$ cd /var/log/apache_user/username username@ssh1:/var/log/apache_user/username$ ls username.ulyssis.be username@ssh1:/var/log/apache_user/username$ cd username.ulyssis.be username@ssh1:/var/log/apache_user/username/username.ulyssis.be$ ls access-2014-05-07.log error-2014-05-07.log username@ssh1:/var/log/apache_user/username/username.ulyssis.be$ tail error-2014-05-07.log [Wed May 07 01:27:14 2014] [error] [client 10.0.0.1] File does not exist: /home/user/username/www/favicon.ico If you can't find your username inside of <code>/var/log/apache_user</code>, don't worry. If you enter it with <code>cd username</code>, it will automatically appear. [[Category:Webserver]] 1d2b45f3a0c6652ae0522a4ac13bf874b1f57df7 1487 1486 2021-08-04T00:54:16Z Thomasd 40 wikitext text/x-wiki You can find all your Apache logs (like access.log and error.log) on all of our shell servers in the directory <code>/var/log/apache_user/''username''</code>. For more information on how to access your files, please visit [[Accessing your files]]. ==Using Cyberduck== You can access the log files using an SFTP client like Cyberduck. After logging in to one of our shell servers as per [[Accessing your files]], click on "Go" on the top bar and then click "Go to Folder...": [[File:Getting Apache Logs - Cyberduck 1.png]] Then enter <code>/var/log/apache_user/''username''</code> as path name (replace ''username'' with your own username): [[File:Getting Apache Logs - Cyberduck 2.png]] After pressing "Go", you will see a directory for each of your websites, containing their Apache logs. [[File:Getting Apache Logs - Cyberduck 3.png]] ==Using the command line== You can also access your logs by [[Accessing shell servers over SSH|logging in to one of our shell servers over SSH]] and navigating to the correct directory: username@ssh1:~$ cd /var/log/apache_user/username username@ssh1:/var/log/apache_user/username$ ls username.ulyssis.be username@ssh1:/var/log/apache_user/username$ cd username.ulyssis.be username@ssh1:/var/log/apache_user/username/username.ulyssis.be$ ls access-2014-05-07.log error-2014-05-07.log username@ssh1:/var/log/apache_user/username/username.ulyssis.be$ tail error-2014-05-07.log [Wed May 07 01:27:14 2014] [error] [client 10.0.0.1] File does not exist: /home/user/username/www/favicon.ico If you can't find your username inside of <code>/var/log/apache_user</code>, don't worry. If you enter it with <code>cd username</code>, it will automatically appear. [[Category:Webserver]] 3077ee09dd9fc92d9917f6dc305d5f3e1d1d34d1 0 154 1488 1241 2021-08-04T01:03:38Z Thomasd 40 wikitext text/x-wiki __TOC__ This page discusses what happens when you use more disk space than has been allotted to your account (your quota) and how to reduce your disk usage. You may have been pointed here through an automatic email notification you are running over your quota, or through our support. This page is also useful if you want to reduce your disk usage even if you're not using more than your quota. You can check your current disk usage as well as your quota on https://ucc.ulyssis.org/quota. This page first discusses what happens when you use more disk space than is available to your account type (so you therefore go over your quota). This is followed by a detailed manual on how to use the command line tool ''ncdu'' to look for the files and folders that may be causing trouble within your account. Finally, there's a list of examples of common causes for large disk space usage. == What happens when I go over my quota? == If you are using more disk space than the allowed quota for your account type for more than seven consecutive days (the so-called grace period), you will no longer be able to write any additional files or extend existing files. You will probably no longer be able to edit websites on your account or it might even stop working outright. If you haven't configured a forwarder for your <code>''username''@ulyssis.org</code> email address, you will lose emails sent to this address. The grace period of seven days is intended for you to have time to reduce your disk space. You will receive an email every day reminding you that you are using too much disk space. In order to prevent impact on other users in cases where disk usage within an account suddenly and substantially surges, an additional quota slightly higher than your normal quota is imposed, independent of any grace period. == Identifying which files & folders use the most disk space == It is not always easy to immediately identify what is taking up space on your account. Sadly, there are no dependable cross-platform tools to help with this. Instead, we will be using the command line tool ''ncdu'', which runs directly on one of our shell servers. You do not need to be proficient with command line interfaces in order to use this tool, the step-by-step manual below will guide you through the process. However, should you get stuck, do not hesitate to contact us at <code>ulyssis@ulyssis.org</code>. * Connect through SSH to one of the shell servers: https://docs.ulyssis.org/Accessing_shell_servers_over_SSH * Type in <code>ncdu</code> and press enter. You will then see that <code>ncdu</code> is scanning your account. * Once <code>ncdu</code> has finished scanning, it will display which files or folders located directly in your home directory are using the most disk space. When the filename stars with <code>/</code> it is a folder. The results are ordered by size, so it makes most sense to start with the top items. * You can select different files/folders using the '''up and down arrow keys''', navigate the directory structure using either the '''enter and backspace''' keys or the '''left and right''' arrows to move in and out of folders, quit ncdu by pressing '''q''' and delete a file or folder with '''d'''. Be careful to not delete files you still need as you will need to contact us in order to restore them from a backup. * You can check your progress on https://ucc.ulyssis.org/quota. The percentage and values displayed are always current and accurate, there is no delay.[[File:Disk usage ncdu.png|thumb|760x760px]] === Common sources of unnecessary disk usage === * Your ULYSSIS mailbox: Depending on your account settings, your ''@ulyssis.org'' email account may be used as a forwarder or an inbox. When set to ''Inbox'' on https://ucc.ulyssis.org/mail, email will be saved to the ''Maildir'' folder within your account. A substantial amount of email, especially with large attachments, may grow to quite a significant size. You can verify the contents of your mailbox easily by logging in on https://webmail.ulyssis.org using your ULYSSIS account credentials. You can then remove those emails that are no longer useful, and don't forget to empty the trash. To remove the entire mailbox, you can simply remove the Maildir folder from your account (using ncdu, Cyberduck, or another tool). To empty the trash manually, you can remove the ''Maildir/.Trash'' folder. If you no longer wish to use you mailbox, don't forget to change the configuration on https://ucc.ulyssis.org/mail to forward your messages, since you may receive relevant information about your account through this address. * Old websites: if you have older websites on your account that you are no longer using, it might be worth removing them in their entirety. If the deleted website uses a database (this will always be the case if your using WordPress, MediaWiki or another popular CMS), then you should also delete those through our control panel: https://ucc.ulyssis.org (either the MySQL or PostgreSQL sections). If this website had an associated (sub)domain, please send us an email to have it removed. Also keep in mind that old websites may pose a security risk, so it's never good to leave them lying about. * Unused images: in the case of many CMSes (WordPress, Drupal, ...), removing an image from a post will not delete it. For example, in the case of WordPress it will still be available through the Media Library. You can easily find these [https://wordpress.com/support/media/2/#unattached-files unattached files]. In order to reclaim the disk space used by the image, you will have to [https://wordpress.com/support/trash/#permanently-deleting-an-upload delete] it there as well. Similarly, MediaWiki offers a list of ''unused files'' as a special page available in the list of ''Special Pages''. Keep in mind that WordPress or MediaWiki might not always be aware an image or other file is used when it has not been added through its interfaces or through a third party plugin. * Large images: images and especially pictures are often several MBs in size and often have a large resolution. While this is great for editing and printing, such large sizes are not all that useful for inclusion in a webpage. They can make your site load slower and use more disk space without a significant increase in quality. You should therefore consider resizing images before uploading them or installing a plugin, module or extension that reduces their size on upload. However, make sure to watch out for plugins that keep the original image around as this will not reduce but increase your disk usage. For a tutorial on how to resize images, you can take a look at https://wordpress.com/support/media/image-optimization/. This tutorial is geared towards WordPress, but is also applicable in general. If you are using MediaWiki, we have written a plugin that reduces the size of various types of files. You can find more details on [[Setting up MediaWiki#Extensions|Setting up MediaWiki - Extensions]]. * Backups: ULYSSIS makes daily backups of all account data, including databases, and keeps them for at least a month. It is therefore not necessary to make automated backups of your own, for example with plugins such as [https://nl.wordpress.org/plugins/updraftplus/ Updraft] for WordPress. Although it is a good practice to make backups whenever you are making large changes to your site, it is not necessary to keep them after you have verified that your site works correctly. * Anything missing on this list? Feel free to contact us on <code>ulyssis@ulyssis.org</code> with your suggestions. [[Category:Files]] [[Category:Account]] f22158abc15bd78c2cd62fcc278db5407690ef88 0 176 1496 1495 2021-08-04T21:32:12Z Yoa 30 /* Installing the new files */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. {{info|In this guide, we assume you are familiar with the files on your ULYSSIS account. If you don't know how to access these files, please read [[Accessing your files]] first.}} == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. If you arrived at this page after receiving an email from our [[Software Version Checker]], follow the instructions in the next paragraph. Otherwise, you can skip the next paragraph. The email you received might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can find your current MediaWiki version by going to the <code>Special:Version</code> page on your wiki (simply paste this in the search box) and looking for the "MediaWiki" version under "Installed software". For example, for this wiki, you can find the current version at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed software.png|center|frame]] A table of all recent MediaWiki versions can be found on the [https://en.wikipedia.org/wiki/MediaWiki_version_history the official table]. Currently supported versions are indicated by a green or yellow color in the first column. To determine which version you want to download, follow these steps: * If the ''branch'' of your version ('''the first two numbers''', like <code>1.xx</code>) is currently supported (green or yellow), you should choose the latest version for this branch. For example, for version 1.35.3, the branch is 1.35. * If this branch is not supported anymore, you should choose the most recent LTS branch. This is indicated by '''(LTS)''' in the second column. * If the most recent LTS branch is older than your current branch, you should choose the newest supported branch (green). Now, click on the link of the branch you want to download. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-1.xx.yy.tar.gz</code>. Download this file and save it somewhere on your PC. == Renaming the old installation == An important step in the update process is to rename the old installation directory. This way, you can simply copy your data from the old installation directory to the new installation directory during the update. Additionally, you can easily restore your old wiki if something goes wrong. The easiest way to do this, is to '''rename''' your wiki location (the directory containing your <code>LocalSettings.php</code> configuration file) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_old</code>, or something similar. == Installing the new files == Now, you will need to upload the <code>mediawiki-1.xx.yy.tar.gz</code> file you downloaded in step 1 next to the old installation directory. For example, if your old installation directory is located in <code>www/wiki_old</code>, upload <code>mediawiki-1.xx.yy.tar.gz</code> to <code>www/</code>. After uploading, you can extract the file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the file and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-1.xx.yy</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-1.xx.yy</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any <code>.htaccess</code> file, if present. '''Make sure you can view hidden files'''; to enable this for Cyberduck, you can look at [[Accessing_your_files#Viewing_hidden_files|Accessing your files]]. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. For example, you might have the ULYSSIS extensions [[Securing MediaWiki using Centrale KU Leuven Login|MediaWikiShibboleth]] or [https://github.com/ULYSSIS-KUL/CompressUploads CompressUploads] installed. As the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box: php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the old installation: for example, if this is stored in <code>www/wiki_old</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing_your_files#Creating_and_Deleting_files_and_folders|Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. 59372be59948bf44c7c62e57e574dec6ce984f97 1497 1496 2021-08-04T21:33:57Z Yoa 30 /* Updating extensions */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. {{info|In this guide, we assume you are familiar with the files on your ULYSSIS account. If you don't know how to access these files, please read [[Accessing your files]] first.}} == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. If you arrived at this page after receiving an email from our [[Software Version Checker]], follow the instructions in the next paragraph. Otherwise, you can skip the next paragraph. The email you received might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can find your current MediaWiki version by going to the <code>Special:Version</code> page on your wiki (simply paste this in the search box) and looking for the "MediaWiki" version under "Installed software". For example, for this wiki, you can find the current version at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed software.png|center|frame]] A table of all recent MediaWiki versions can be found on the [https://en.wikipedia.org/wiki/MediaWiki_version_history the official table]. Currently supported versions are indicated by a green or yellow color in the first column. To determine which version you want to download, follow these steps: * If the ''branch'' of your version ('''the first two numbers''', like <code>1.xx</code>) is currently supported (green or yellow), you should choose the latest version for this branch. For example, for version 1.35.3, the branch is 1.35. * If this branch is not supported anymore, you should choose the most recent LTS branch. This is indicated by '''(LTS)''' in the second column. * If the most recent LTS branch is older than your current branch, you should choose the newest supported branch (green). Now, click on the link of the branch you want to download. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-1.xx.yy.tar.gz</code>. Download this file and save it somewhere on your PC. == Renaming the old installation == An important step in the update process is to rename the old installation directory. This way, you can simply copy your data from the old installation directory to the new installation directory during the update. Additionally, you can easily restore your old wiki if something goes wrong. The easiest way to do this, is to '''rename''' your wiki location (the directory containing your <code>LocalSettings.php</code> configuration file) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_old</code>, or something similar. == Installing the new files == Now, you will need to upload the <code>mediawiki-1.xx.yy.tar.gz</code> file you downloaded in step 1 next to the old installation directory. For example, if your old installation directory is located in <code>www/wiki_old</code>, upload <code>mediawiki-1.xx.yy.tar.gz</code> to <code>www/</code>. After uploading, you can extract the file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the file and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-1.xx.yy</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-1.xx.yy</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any <code>.htaccess</code> file, if present. '''Make sure you can view hidden files'''; to enable this for Cyberduck, you can look at [[Accessing_your_files#Viewing_hidden_files|Accessing your files]]. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. For example, you might have the ULYSSIS extensions [[Securing MediaWiki using Centrale KU Leuven Login|MediaWikiShibboleth]] or [https://github.com/ULYSSIS-KUL/CompressUploads CompressUploads] installed. As with MediaWiki, you can find the versions of your installed extensions on the <code>Special:Version</code> page, under "Installed extensions". For example, for this wiki, you can the installed extensions at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed extensions.png|center|frame]] Because the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box: php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the old installation: for example, if this is stored in <code>www/wiki_old</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing_your_files#Creating_and_Deleting_files_and_folders|Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. 1231e49a566c0c9539fadf1ea69f9300d1dd178c 1499 1497 2021-08-04T21:47:43Z Yoa 30 /* Updating extensions */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. {{info|In this guide, we assume you are familiar with the files on your ULYSSIS account. If you don't know how to access these files, please read [[Accessing your files]] first.}} == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. If you arrived at this page after receiving an email from our [[Software Version Checker]], follow the instructions in the next paragraph. Otherwise, you can skip the next paragraph. The email you received might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can find your current MediaWiki version by going to the <code>Special:Version</code> page on your wiki (simply paste this in the search box) and looking for the "MediaWiki" version under "Installed software". For example, for this wiki, you can find the current version at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed software.png|center|frame]] A table of all recent MediaWiki versions can be found on the [https://en.wikipedia.org/wiki/MediaWiki_version_history the official table]. Currently supported versions are indicated by a green or yellow color in the first column. To determine which version you want to download, follow these steps: * If the ''branch'' of your version ('''the first two numbers''', like <code>1.xx</code>) is currently supported (green or yellow), you should choose the latest version for this branch. For example, for version 1.35.3, the branch is 1.35. * If this branch is not supported anymore, you should choose the most recent LTS branch. This is indicated by '''(LTS)''' in the second column. * If the most recent LTS branch is older than your current branch, you should choose the newest supported branch (green). Now, click on the link of the branch you want to download. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-1.xx.yy.tar.gz</code>. Download this file and save it somewhere on your PC. == Renaming the old installation == An important step in the update process is to rename the old installation directory. This way, you can simply copy your data from the old installation directory to the new installation directory during the update. Additionally, you can easily restore your old wiki if something goes wrong. The easiest way to do this, is to '''rename''' your wiki location (the directory containing your <code>LocalSettings.php</code> configuration file) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_old</code>, or something similar. == Installing the new files == Now, you will need to upload the <code>mediawiki-1.xx.yy.tar.gz</code> file you downloaded in step 1 next to the old installation directory. For example, if your old installation directory is located in <code>www/wiki_old</code>, upload <code>mediawiki-1.xx.yy.tar.gz</code> to <code>www/</code>. After uploading, you can extract the file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the file and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-1.xx.yy</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-1.xx.yy</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any <code>.htaccess</code> file, if present. '''Make sure you can view hidden files'''; to enable this for Cyberduck, you can look at [[Accessing_your_files#Viewing_hidden_files|Accessing your files]]. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. A list of bundled extensions can be found at https://www.mediawiki.org/wiki/Bundled_extensions_and_skins. For example, you might have the ULYSSIS extensions [[Securing MediaWiki using Centrale KU Leuven Login|MediaWikiShibboleth]] or [https://github.com/ULYSSIS-KUL/CompressUploads CompressUploads] installed. As with MediaWiki, you can find the versions of your installed extensions on the <code>Special:Version</code> page, under "Installed extensions". For example, for this wiki, you can find the installed extensions at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed extensions.png|center|frame]] Because the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box: php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the old installation: for example, if this is stored in <code>www/wiki_old</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing_your_files#Creating_and_Deleting_files_and_folders|Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. 278899157a69566ffbd61a3c8f1ddae9225f2ec8 1500 1499 2021-08-04T21:48:06Z Yoa 30 /* Updating extensions */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. {{info|In this guide, we assume you are familiar with the files on your ULYSSIS account. If you don't know how to access these files, please read [[Accessing your files]] first.}} == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. If you arrived at this page after receiving an email from our [[Software Version Checker]], follow the instructions in the next paragraph. Otherwise, you can skip the next paragraph. The email you received might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can find your current MediaWiki version by going to the <code>Special:Version</code> page on your wiki (simply paste this in the search box) and looking for the "MediaWiki" version under "Installed software". For example, for this wiki, you can find the current version at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed software.png|center|frame]] A table of all recent MediaWiki versions can be found on the [https://en.wikipedia.org/wiki/MediaWiki_version_history the official table]. Currently supported versions are indicated by a green or yellow color in the first column. To determine which version you want to download, follow these steps: * If the ''branch'' of your version ('''the first two numbers''', like <code>1.xx</code>) is currently supported (green or yellow), you should choose the latest version for this branch. For example, for version 1.35.3, the branch is 1.35. * If this branch is not supported anymore, you should choose the most recent LTS branch. This is indicated by '''(LTS)''' in the second column. * If the most recent LTS branch is older than your current branch, you should choose the newest supported branch (green). Now, click on the link of the branch you want to download. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-1.xx.yy.tar.gz</code>. Download this file and save it somewhere on your PC. == Renaming the old installation == An important step in the update process is to rename the old installation directory. This way, you can simply copy your data from the old installation directory to the new installation directory during the update. Additionally, you can easily restore your old wiki if something goes wrong. The easiest way to do this, is to '''rename''' your wiki location (the directory containing your <code>LocalSettings.php</code> configuration file) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_old</code>, or something similar. == Installing the new files == Now, you will need to upload the <code>mediawiki-1.xx.yy.tar.gz</code> file you downloaded in step 1 next to the old installation directory. For example, if your old installation directory is located in <code>www/wiki_old</code>, upload <code>mediawiki-1.xx.yy.tar.gz</code> to <code>www/</code>. After uploading, you can extract the file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the file and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-1.xx.yy</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-1.xx.yy</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any <code>.htaccess</code> file, if present. '''Make sure you can view hidden files'''; to enable this for Cyberduck, you can look at [[Accessing_your_files#Viewing_hidden_files|Accessing your files]]. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. A list of bundled extensions can be found at https://www.mediawiki.org/wiki/Bundled_extensions_and_skins. For example, you might have the ULYSSIS extensions [[Securing MediaWiki using Centrale KU Leuven Login|MediaWikiShibboleth]] or [https://github.com/ULYSSIS-KUL/CompressUploads CompressUploads] installed. As with MediaWiki itself, you can find the versions of your installed extensions on the <code>Special:Version</code> page, under "Installed extensions". For example, for this wiki, you can find the installed extensions at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed extensions.png|center|frame]] Because the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box: php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the old installation: for example, if this is stored in <code>www/wiki_old</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing_your_files#Creating_and_Deleting_files_and_folders|Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. ea2901f888b3825a86353b998fb393c95d2ce01f 1501 1500 2021-08-04T21:48:42Z Yoa 30 /* Updating extensions */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. {{info|In this guide, we assume you are familiar with the files on your ULYSSIS account. If you don't know how to access these files, please read [[Accessing your files]] first.}} == Downloading the latest version == To start updating MediaWiki, you will need to download the version you want to update to. If you arrived at this page after receiving an email from our [[Software Version Checker]], follow the instructions in the next paragraph. Otherwise, you can skip the next paragraph. The email you received might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can find your current MediaWiki version by going to the <code>Special:Version</code> page on your wiki (simply paste this in the search box) and looking for the "MediaWiki" version under "Installed software". For example, for this wiki, you can find the current version at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed software.png|center|frame]] A table of all recent MediaWiki versions can be found on the [https://en.wikipedia.org/wiki/MediaWiki_version_history the official table]. Currently supported versions are indicated by a green or yellow color in the first column. To determine which version you want to download, follow these steps: * If the ''branch'' of your version ('''the first two numbers''', like <code>1.xx</code>) is currently supported (green or yellow), you should choose the latest version for this branch. For example, for version 1.35.3, the branch is 1.35. * If this branch is not supported anymore, you should choose the most recent LTS branch. This is indicated by '''(LTS)''' in the second column. * If the most recent LTS branch is older than your current branch, you should choose the newest supported branch (green). Now, click on the link of the branch you want to download. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-1.xx.yy.tar.gz</code>. Download this file and save it somewhere on your PC. == Renaming the old installation == An important step in the update process is to rename the old installation directory. This way, you can simply copy your data from the old installation directory to the new installation directory during the update. Additionally, you can easily restore your old wiki if something goes wrong. The easiest way to do this, is to '''rename''' your wiki location (the directory containing your <code>LocalSettings.php</code> configuration file) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' this directory to <code>www/wiki_old</code>, or something similar. == Installing the new files == Now, you will need to upload the <code>mediawiki-1.xx.yy.tar.gz</code> file you downloaded in step 1 next to the old installation directory. For example, if your old installation directory is located in <code>www/wiki_old</code>, upload <code>mediawiki-1.xx.yy.tar.gz</code> to <code>www/</code>. After uploading, you can extract the file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the file and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-1.xx.yy</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-1.xx.yy</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any <code>.htaccess</code> file, if present. '''Make sure you can view hidden files'''; to enable this for Cyberduck, you can look at [[Accessing_your_files#Viewing_hidden_files|Accessing your files]]. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. A list of bundled extensions can be found at https://www.mediawiki.org/wiki/Bundled_extensions_and_skins. For example, you might have the ULYSSIS extensions [[Securing MediaWiki using Centrale KU Leuven Login|MediaWikiShibboleth]] or [https://github.com/ULYSSIS-KUL/CompressUploads CompressUploads] installed. As with MediaWiki itself, you can find the versions of your installed extensions on the <code>Special:Version</code> page, under "Installed extensions". Extensions will often link to a website where you can download the latest versions. For example, for this wiki, you can find the installed extensions at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed extensions.png|center|frame]] Because the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box: php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the old installation: for example, if this is stored in <code>www/wiki_old</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing_your_files#Creating_and_Deleting_files_and_folders|Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. b08456026c27704239ea9db362007071e175b75d 1502 1501 2021-08-08T12:17:26Z Yoa 30 wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. {{info|In this guide, we assume you are familiar with the files on your ULYSSIS account. If you don't know how to access these files, please read [[Accessing your files]] first.}} == Downloading the right version == To start updating MediaWiki, you will need to download the archive file of the version you want to update to. If you arrived at this page after receiving an email from our [[Software Version Checker]], follow the instructions in the next paragraph. Otherwise, you can skip the next paragraph. The email you received might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can find your current MediaWiki version by going to the <code>Special:Version</code> page on your wiki (simply paste this in the search box) and looking for the "MediaWiki" version under "Installed software". For example, for this wiki, you can find the current version at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed software.png|center|frame]] A table of all recent MediaWiki versions can be found on the [https://en.wikipedia.org/wiki/MediaWiki_version_history the official table]. Currently supported versions are indicated by a green or yellow color in the first column. To determine which version you want to download, follow these steps: * If the ''branch'' of your version ('''the first two numbers''', like <code>1.xx</code>) is currently supported (green or yellow), you should choose the latest version for this branch. For example, for version 1.35.3, the branch is 1.35. * If this branch is not supported anymore, you should choose the most recent LTS branch. This is indicated by '''(LTS)''' in the second column. '''Make sure this LTS branch is not older than your current branch!''' * If the most recent LTS branch is older than your current branch, you should choose the newest supported branch (green). Now, click on the link of the branch you want to download. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-1.xx.yy.tar.gz</code>. Download this file and save it somewhere on your computer. == Renaming the old installation == An important step in the update process is to rename the old installation directory. This way, you can simply copy your data from the old installation directory to the new installation directory during the update. Additionally, you can easily restore your old wiki if something goes wrong. The easiest way to do this, is to '''rename''' your wiki location (the directory containing your <code>LocalSettings.php</code> configuration file) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' the wiki folder to <code>wiki_old</code>. == Installing the new files == Now, you will need to upload the <code>mediawiki-1.xx.yy.tar.gz</code> file you downloaded in step 1 next to the old installation directory. For example, if your old installation directory is located in <code>www/wiki_old</code>, upload <code>mediawiki-1.xx.yy.tar.gz</code> to <code>www/</code>. After uploading, you can extract the file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the file and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-1.xx.yy</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-1.xx.yy</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The directory containing the uploaded files to the wiki. Most likely, this is <code>images/</code>, unless you set the value <code>$wgUploadDirectory</code> in <code>LocalSettings.php</code> * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any <code>.htaccess</code> file, if present. '''Make sure you can view hidden files'''; to enable this for Cyberduck, you can look at [[Accessing_your_files#Viewing_hidden_files|Accessing your files]]. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. A list of bundled extensions can be found at https://www.mediawiki.org/wiki/Bundled_extensions_and_skins. For example, you might have the ULYSSIS extensions [[Securing MediaWiki using Centrale KU Leuven Login|MediaWikiShibboleth]] or [https://github.com/ULYSSIS-KUL/CompressUploads CompressUploads] installed. As with MediaWiki itself, you can find the versions of your installed extensions on the <code>Special:Version</code> page, under "Installed extensions". Extensions will often link to a website where you can download the latest versions. For example, for this wiki, you can find the installed extensions at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed extensions.png|center|frame]] Because the installation instructions for each extension are different for each extension, this page can't help you with this process. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the files: similar to the MediaWiki zip files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. The MediaWiki developers were kind enough to create a script, called <code>update.php</code>. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box: php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the old installation: for example, if this is stored in <code>www/wiki_old</code>, you can remove it using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing_your_files#Creating_and_Deleting_files_and_folders|Accessing your files]]. However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. 85bf053affa7e447bcb6f5a59dca32be2cc96029 1507 1502 2021-08-08T12:56:49Z Yoa 30 wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. {{info|In this guide, we assume you are familiar with the files on your ULYSSIS account. If you don't know how to access these files, please read [[Accessing your files]] first.}} == Downloading the right version == To start updating MediaWiki, you will need to download the archive file of the version you want to update to. If you arrived at this page after receiving an email from our [[Software Version Checker]], follow the instructions in the next paragraph. Otherwise, you can skip the next paragraph. The email you received might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can find your current MediaWiki version by going to the <code>Special:Version</code> page on your wiki (simply paste this in the search box) and looking for the "MediaWiki" version under "Installed software". For example, for this wiki, you can find the current version at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed software.png|center|frame]] A table of all recent MediaWiki versions can be found on the [https://en.wikipedia.org/wiki/MediaWiki_version_history the official table]. Currently supported versions are indicated by a green or yellow color in the first column. To determine which version you want to download, follow these steps: * If the ''branch'' of your version ('''the first two numbers''', like <code>1.xx</code>) is currently supported (green or yellow), you should choose the latest version for this branch. For example, for version 1.35.3, the branch is 1.35. * If this branch is not supported anymore, you should choose the most recent LTS branch. This is indicated by '''(LTS)''' in the second column. '''Make sure this LTS branch is not older than your current branch!''' * If the most recent LTS branch is older than your current branch, you should choose the newest supported branch (green). Now, click on the link of the branch you want to download. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-1.xx.yy.tar.gz</code>. Download this archive and save it somewhere on your computer. == Renaming the old installation == An important step in the update process is to rename the old installation directory. This way, you can simply copy your data from the old installation directory to the new installation directory during the update. Additionally, you can easily restore your old wiki if something goes wrong. The easiest way to do this, is to '''rename''' your wiki location (the directory containing your <code>LocalSettings.php</code> configuration file) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' the wiki folder to <code>wiki_old</code>. == Installing the new files == Now, you will need to upload the <code>mediawiki-1.xx.yy.tar.gz</code> file you downloaded in step 1 next to the old installation directory. For example, if your old installation directory is located in <code>www/wiki_old</code>, upload <code>mediawiki-1.xx.yy.tar.gz</code> to <code>www/</code>. After uploading, you can extract the archive file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the archive and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-1.xx.yy</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-1.xx.yy</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Finally, you need to copy the configuration files and other files or directories you modified from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The <code>images/</code> directory, containing the uploaded files to the wiki. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any <code>.htaccess</code> file, if present. '''Make sure you can view hidden files'''; to enable this for Cyberduck, you can look at [[Accessing_your_files#Viewing_hidden_files|Accessing your files]]. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. A list of bundled extensions can be found at https://www.mediawiki.org/wiki/Bundled_extensions_and_skins, these extensions will be updated automatically. However, for example, you might have the ULYSSIS extensions [[Securing MediaWiki using Centrale KU Leuven Login|MediaWikiShibboleth]] or [https://github.com/ULYSSIS-KUL/CompressUploads CompressUploads] installed. As with MediaWiki itself, you can find the versions of your installed extensions on the <code>Special:Version</code> page, under "Installed extensions". Extensions will often link to a website where you can download the latest versions. For example, for this wiki, you can find the installed extensions at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed extensions.png|center|frame]] Because the update instructions are different for each extension, you will have to refer to the update instructions of the extension you want to update. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the archive files: similar to the MediaWiki tar.gz archive files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. Your MediaWiki installation contains a script, called <code>update.php</code>, to perform the necessary database upgrades. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box: php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the old installation: you should remove the previously created <code>www/wiki_old</code> directory, using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing_your_files#Creating_and_Deleting_files_and_folders|Accessing your files]]. 7ce577ee53e8ed6994fec6b523bd48f7178b08ca 1508 1507 2021-08-08T13:05:21Z Yoa 30 /* Installing the new files */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. {{info|In this guide, we assume you are familiar with the files on your ULYSSIS account. If you don't know how to access these files, please read [[Accessing your files]] first.}} == Downloading the right version == To start updating MediaWiki, you will need to download the archive file of the version you want to update to. If you arrived at this page after receiving an email from our [[Software Version Checker]], follow the instructions in the next paragraph. Otherwise, you can skip the next paragraph. The email you received might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can find your current MediaWiki version by going to the <code>Special:Version</code> page on your wiki (simply paste this in the search box) and looking for the "MediaWiki" version under "Installed software". For example, for this wiki, you can find the current version at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed software.png|center|frame]] A table of all recent MediaWiki versions can be found on the [https://en.wikipedia.org/wiki/MediaWiki_version_history the official table]. Currently supported versions are indicated by a green or yellow color in the first column. To determine which version you want to download, follow these steps: * If the ''branch'' of your version ('''the first two numbers''', like <code>1.xx</code>) is currently supported (green or yellow), you should choose the latest version for this branch. For example, for version 1.35.3, the branch is 1.35. * If this branch is not supported anymore, you should choose the most recent LTS branch. This is indicated by '''(LTS)''' in the second column. '''Make sure this LTS branch is not older than your current branch!''' * If the most recent LTS branch is older than your current branch, you should choose the newest supported branch (green). Now, click on the link of the branch you want to download. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-1.xx.yy.tar.gz</code>. Download this archive and save it somewhere on your computer. == Renaming the old installation == An important step in the update process is to rename the old installation directory. This way, you can simply copy your data from the old installation directory to the new installation directory during the update. Additionally, you can easily restore your old wiki if something goes wrong. The easiest way to do this, is to '''rename''' your wiki location (the directory containing your <code>LocalSettings.php</code> configuration file) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' the wiki folder to <code>wiki_old</code>. == Installing the new files == Now, you will need to upload the <code>mediawiki-1.xx.yy.tar.gz</code> file you downloaded in step 1 next to the old installation directory. For example, if your old installation directory is located in <code>www/wiki_old</code>, upload <code>mediawiki-1.xx.yy.tar.gz</code> to <code>www/</code>. After uploading, you can extract the archive file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the archive and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-1.xx.yy</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-1.xx.yy</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Finally, you need to copy certain other other files and directories from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The <code>images/</code> directory, containing the uploaded files to the wiki. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any <code>.htaccess</code> file, if present. '''Make sure you can view hidden files'''; to enable this for Cyberduck, you can look at [[Accessing_your_files#Viewing_hidden_files|Accessing your files]]. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. A list of bundled extensions can be found at https://www.mediawiki.org/wiki/Bundled_extensions_and_skins, these extensions will be updated automatically. However, for example, you might have the ULYSSIS extensions [[Securing MediaWiki using Centrale KU Leuven Login|MediaWikiShibboleth]] or [https://github.com/ULYSSIS-KUL/CompressUploads CompressUploads] installed. As with MediaWiki itself, you can find the versions of your installed extensions on the <code>Special:Version</code> page, under "Installed extensions". Extensions will often link to a website where you can download the latest versions. For example, for this wiki, you can find the installed extensions at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed extensions.png|center|frame]] Because the update instructions are different for each extension, you will have to refer to the update instructions of the extension you want to update. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the archive files: similar to the MediaWiki tar.gz archive files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. Your MediaWiki installation contains a script, called <code>update.php</code>, to perform the necessary database upgrades. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box: php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the old installation: you should remove the previously created <code>www/wiki_old</code> directory, using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing_your_files#Creating_and_Deleting_files_and_folders|Accessing your files]]. 4230d7b10e657fc81a9575c906bed11f11fe9842 1509 1508 2021-08-08T13:05:59Z Yoa 30 /* Updating extensions */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. {{info|In this guide, we assume you are familiar with the files on your ULYSSIS account. If you don't know how to access these files, please read [[Accessing your files]] first.}} == Downloading the right version == To start updating MediaWiki, you will need to download the archive file of the version you want to update to. If you arrived at this page after receiving an email from our [[Software Version Checker]], follow the instructions in the next paragraph. Otherwise, you can skip the next paragraph. The email you received might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can find your current MediaWiki version by going to the <code>Special:Version</code> page on your wiki (simply paste this in the search box) and looking for the "MediaWiki" version under "Installed software". For example, for this wiki, you can find the current version at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed software.png|center|frame]] A table of all recent MediaWiki versions can be found on the [https://en.wikipedia.org/wiki/MediaWiki_version_history the official table]. Currently supported versions are indicated by a green or yellow color in the first column. To determine which version you want to download, follow these steps: * If the ''branch'' of your version ('''the first two numbers''', like <code>1.xx</code>) is currently supported (green or yellow), you should choose the latest version for this branch. For example, for version 1.35.3, the branch is 1.35. * If this branch is not supported anymore, you should choose the most recent LTS branch. This is indicated by '''(LTS)''' in the second column. '''Make sure this LTS branch is not older than your current branch!''' * If the most recent LTS branch is older than your current branch, you should choose the newest supported branch (green). Now, click on the link of the branch you want to download. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-1.xx.yy.tar.gz</code>. Download this archive and save it somewhere on your computer. == Renaming the old installation == An important step in the update process is to rename the old installation directory. This way, you can simply copy your data from the old installation directory to the new installation directory during the update. Additionally, you can easily restore your old wiki if something goes wrong. The easiest way to do this, is to '''rename''' your wiki location (the directory containing your <code>LocalSettings.php</code> configuration file) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' the wiki folder to <code>wiki_old</code>. == Installing the new files == Now, you will need to upload the <code>mediawiki-1.xx.yy.tar.gz</code> file you downloaded in step 1 next to the old installation directory. For example, if your old installation directory is located in <code>www/wiki_old</code>, upload <code>mediawiki-1.xx.yy.tar.gz</code> to <code>www/</code>. After uploading, you can extract the archive file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the archive and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-1.xx.yy</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-1.xx.yy</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Finally, you need to copy certain other other files and directories from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The <code>images/</code> directory, containing the uploaded files to the wiki. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any <code>.htaccess</code> file, if present. '''Make sure you can view hidden files'''; to enable this for Cyberduck, you can look at [[Accessing_your_files#Viewing_hidden_files|Accessing your files]]. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. A list of bundled extensions can be found at https://www.mediawiki.org/wiki/Bundled_extensions_and_skins, these extensions will be updated automatically. However, for example, you might have the ULYSSIS extensions [[Securing MediaWiki using Centrale KU Leuven Login|MediaWikiShibboleth]] or [https://github.com/ULYSSIS-KUL/CompressUploads CompressUploads] installed. As with MediaWiki itself, you can find the versions of your installed extensions on the <code>Special:Version</code> page, under "Installed extensions". Extensions will often link to a website where you can download the latest versions. For example, for this wiki, you can find the installed extensions at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed extensions.png|center|frame]] Because the update instructions are different for each extension, you will have to refer to the update instructions of the extension you want to update. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the archive files: similar to the MediaWiki tar.gz archive files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. Your MediaWiki installation contains a script, called <code>update.php</code>, to perform the necessary database upgrades. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box: php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the old installation: you should remove the previously created <code>www/wiki_old</code> directory, using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing_your_files#Creating_and_Deleting_files_and_folders|Accessing your files]]. 2de3e9261812f0187f5fbb18701d5da99014b01c 1510 1509 2021-08-08T13:06:12Z Yoa 30 /* Updating extensions */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. {{info|In this guide, we assume you are familiar with the files on your ULYSSIS account. If you don't know how to access these files, please read [[Accessing your files]] first.}} == Downloading the right version == To start updating MediaWiki, you will need to download the archive file of the version you want to update to. If you arrived at this page after receiving an email from our [[Software Version Checker]], follow the instructions in the next paragraph. Otherwise, you can skip the next paragraph. The email you received might contain a line similar to: - MediaWiki in <path>. Installed version: <version1>. Latest version: <version2>. This line tells you where the MediaWiki installation is located, its current version, and the version you need to download. If you don't have an email from our Software Version Checker, you can find your current MediaWiki version by going to the <code>Special:Version</code> page on your wiki (simply paste this in the search box) and looking for the "MediaWiki" version under "Installed software". For example, for this wiki, you can find the current version at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed software.png|center|frame]] A table of all recent MediaWiki versions can be found on the [https://en.wikipedia.org/wiki/MediaWiki_version_history the official table]. Currently supported versions are indicated by a green or yellow color in the first column. To determine which version you want to download, follow these steps: * If the ''branch'' of your version ('''the first two numbers''', like <code>1.xx</code>) is currently supported (green or yellow), you should choose the latest version for this branch. For example, for version 1.35.3, the branch is 1.35. * If this branch is not supported anymore, you should choose the most recent LTS branch. This is indicated by '''(LTS)''' in the second column. '''Make sure this LTS branch is not older than your current branch!''' * If the most recent LTS branch is older than your current branch, you should choose the newest supported branch (green). Now, click on the link of the branch you want to download. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-1.xx.yy.tar.gz</code>. Download this archive and save it somewhere on your computer. == Renaming the old installation == An important step in the update process is to rename the old installation directory. This way, you can simply copy your data from the old installation directory to the new installation directory during the update. Additionally, you can easily restore your old wiki if something goes wrong. The easiest way to do this, is to '''rename''' your wiki location (the directory containing your <code>LocalSettings.php</code> configuration file) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' the wiki folder to <code>wiki_old</code>. == Installing the new files == Now, you will need to upload the <code>mediawiki-1.xx.yy.tar.gz</code> file you downloaded in step 1 next to the old installation directory. For example, if your old installation directory is located in <code>www/wiki_old</code>, upload <code>mediawiki-1.xx.yy.tar.gz</code> to <code>www/</code>. After uploading, you can extract the archive file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the archive and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-1.xx.yy</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-1.xx.yy</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Finally, you need to copy certain other other files and directories from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The <code>images/</code> directory, containing the uploaded files to the wiki. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any <code>.htaccess</code> file, if present. '''Make sure you can view hidden files'''; to enable this for Cyberduck, you can look at [[Accessing_your_files#Viewing_hidden_files|Accessing your files]]. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. A list of bundled extensions can be found at https://www.mediawiki.org/wiki/Bundled_extensions_and_skins, these extensions will be updated automatically. However, for example, you might have the ULYSSIS extensions [[Securing MediaWiki using Centrale KU Leuven Login|MediaWikiShibboleth]] or [https://github.com/ULYSSIS-KUL/CompressUploads CompressUploads] installed. As with MediaWiki itself, you can find the versions of your installed extensions on the <code>Special:Version</code> page, under "Installed extensions". Extensions will often link to a website where you can download the latest versions. For example, for this wiki, you can find the installed extensions at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed extensions.png|center|frame]] Because the update instructions are different for each extension, you will have to refer to the update instructions of the extension you want to update. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the archive files: similar to the MediaWiki tar.gz archive files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. Your MediaWiki installation contains a script, called <code>update.php</code>, to perform the necessary database upgrades. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box: php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the old installation: you should remove the previously created <code>www/wiki_old</code> directory, using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing_your_files#Creating_and_Deleting_files_and_folders|Accessing your files]]. 4230d7b10e657fc81a9575c906bed11f11fe9842 1511 1510 2021-08-08T20:24:05Z Yoa 30 /* Downloading the right version */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. {{info|In this guide, we assume you are familiar with the files on your ULYSSIS account. If you don't know how to access these files, please read [[Accessing your files]] first.}} == Downloading the right version == To start updating MediaWiki, you will need to download the archive file of the version you want to update to. If you arrived at this page after receiving an email from our [[Software Version Checker]], follow the instructions in the next paragraph. Otherwise, you can skip the next paragraph. === Downloading the right version based on your wiki === You can find your current MediaWiki version by going to the <code>Special:Version</code> page on your wiki (simply paste this in the search box) and looking for the "MediaWiki" version under "Installed software". For example, for this wiki, you can find the current version at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed software.png|center|frame]] A table of all recent MediaWiki versions can be found on the [https://en.wikipedia.org/wiki/MediaWiki_version_history the official table]. Currently supported versions are indicated by a green or yellow color in the first column. To determine which version you want to download, follow these steps: * If the ''branch'' of your version ('''the first two numbers''', like <code>1.xx</code>) is currently supported (green or yellow), you should choose the latest version for this branch. For example, for version 1.35.3, the branch is 1.35. * If this branch is not supported anymore, you should choose the most recent LTS branch. This is indicated by '''(LTS)''' in the second column. '''Make sure this LTS branch is not older than your current branch!''' * If the most recent LTS branch is older than your current branch, you should choose the newest supported branch (green). Now, click on the link of the branch you want to download. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-1.xx.yy.tar.gz</code>. Download this archive and save it somewhere on your computer. === Downloading the right version using the Software Version Checker === The email you received will contain a link to the correct MediaWiki version. This link looks something like: https://releases.wikimedia.org/mediawiki/1.xx/mediawiki-core-1.xx.yy.tar.gz Simply click this link to download the archive and save it somewhere on your computer. == Renaming the old installation == An important step in the update process is to rename the old installation directory. This way, you can simply copy your data from the old installation directory to the new installation directory during the update. Additionally, you can easily restore your old wiki if something goes wrong. The easiest way to do this, is to '''rename''' your wiki location (the directory containing your <code>LocalSettings.php</code> configuration file) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' the wiki folder to <code>wiki_old</code>. == Installing the new files == Now, you will need to upload the <code>mediawiki-1.xx.yy.tar.gz</code> file you downloaded in step 1 next to the old installation directory. For example, if your old installation directory is located in <code>www/wiki_old</code>, upload <code>mediawiki-1.xx.yy.tar.gz</code> to <code>www/</code>. After uploading, you can extract the archive file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the archive and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-1.xx.yy</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-1.xx.yy</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Finally, you need to copy certain other other files and directories from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The <code>images/</code> directory, containing the uploaded files to the wiki. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any <code>.htaccess</code> file, if present. '''Make sure you can view hidden files'''; to enable this for Cyberduck, you can look at [[Accessing_your_files#Viewing_hidden_files|Accessing your files]]. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. A list of bundled extensions can be found at https://www.mediawiki.org/wiki/Bundled_extensions_and_skins, these extensions will be updated automatically. However, for example, you might have the ULYSSIS extensions [[Securing MediaWiki using Centrale KU Leuven Login|MediaWikiShibboleth]] or [https://github.com/ULYSSIS-KUL/CompressUploads CompressUploads] installed. As with MediaWiki itself, you can find the versions of your installed extensions on the <code>Special:Version</code> page, under "Installed extensions". Extensions will often link to a website where you can download the latest versions. For example, for this wiki, you can find the installed extensions at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed extensions.png|center|frame]] Because the update instructions are different for each extension, you will have to refer to the update instructions of the extension you want to update. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the archive files: similar to the MediaWiki tar.gz archive files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. Your MediaWiki installation contains a script, called <code>update.php</code>, to perform the necessary database upgrades. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box: php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the old installation: you should remove the previously created <code>www/wiki_old</code> directory, using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing_your_files#Creating_and_Deleting_files_and_folders|Accessing your files]]. cf7cf4294431ea1cbc6bc63fbbefc577a00a6cc7 1512 1511 2021-08-08T20:26:49Z Yoa 30 /* Downloading the right version */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. {{info|In this guide, we assume you are familiar with the files on your ULYSSIS account. If you don't know how to access these files, please read [[Accessing your files]] first.}} == Downloading the right version == To start updating MediaWiki, you will need to download the archive file of the version you want to update to. If you did not receive an email from our [[Software Version Checker]], follow the instructions in the next subsection. Otherwise, you can skip to the subsection [[#Downloading the right version using the Software Version Checker | Downloading the right version using the Software Version Checker]]. === Downloading the right version based on your wiki === You can find your current MediaWiki version by going to the <code>Special:Version</code> page on your wiki (simply paste this in the search box) and looking for the "MediaWiki" version under "Installed software". For example, for this wiki, you can find the current version at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed software.png|center|frame]] A table of all recent MediaWiki versions can be found on the [https://en.wikipedia.org/wiki/MediaWiki_version_history the official table]. Currently supported versions are indicated by a green or yellow color in the first column. To determine which version you want to download, follow these steps: * If the ''branch'' of your version ('''the first two numbers''', like <code>1.xx</code>) is currently supported (green or yellow), you should choose the latest version for this branch. For example, for version 1.35.3, the branch is 1.35. * If this branch is not supported anymore, you should choose the most recent LTS branch. This is indicated by '''(LTS)''' in the second column. '''Make sure this LTS branch is not older than your current branch!''' * If the most recent LTS branch is older than your current branch, you should choose the newest supported branch (green). Now, click on the link of the branch you want to download. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-1.xx.yy.tar.gz</code>. Download this archive and save it somewhere on your computer. === Downloading the right version using the Software Version Checker === The email you received will contain a link to the correct MediaWiki version. This link looks something like: https://releases.wikimedia.org/mediawiki/1.xx/mediawiki-core-1.xx.yy.tar.gz Simply click this link to download the archive and save it somewhere on your computer. == Renaming the old installation == An important step in the update process is to rename the old installation directory. This way, you can simply copy your data from the old installation directory to the new installation directory during the update. Additionally, you can easily restore your old wiki if something goes wrong. The easiest way to do this, is to '''rename''' your wiki location (the directory containing your <code>LocalSettings.php</code> configuration file) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' the wiki folder to <code>wiki_old</code>. == Installing the new files == Now, you will need to upload the <code>mediawiki-1.xx.yy.tar.gz</code> file you downloaded in step 1 next to the old installation directory. For example, if your old installation directory is located in <code>www/wiki_old</code>, upload <code>mediawiki-1.xx.yy.tar.gz</code> to <code>www/</code>. After uploading, you can extract the archive file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the archive and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-1.xx.yy</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-1.xx.yy</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Finally, you need to copy certain other other files and directories from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The <code>images/</code> directory, containing the uploaded files to the wiki. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any <code>.htaccess</code> file, if present. '''Make sure you can view hidden files'''; to enable this for Cyberduck, you can look at [[Accessing_your_files#Viewing_hidden_files|Accessing your files]]. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. A list of bundled extensions can be found at https://www.mediawiki.org/wiki/Bundled_extensions_and_skins, these extensions will be updated automatically. However, for example, you might have the ULYSSIS extensions [[Securing MediaWiki using Centrale KU Leuven Login|MediaWikiShibboleth]] or [https://github.com/ULYSSIS-KUL/CompressUploads CompressUploads] installed. As with MediaWiki itself, you can find the versions of your installed extensions on the <code>Special:Version</code> page, under "Installed extensions". Extensions will often link to a website where you can download the latest versions. For example, for this wiki, you can find the installed extensions at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed extensions.png|center|frame]] Because the update instructions are different for each extension, you will have to refer to the update instructions of the extension you want to update. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the archive files: similar to the MediaWiki tar.gz archive files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. Your MediaWiki installation contains a script, called <code>update.php</code>, to perform the necessary database upgrades. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box: php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the old installation: you should remove the previously created <code>www/wiki_old</code> directory, using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing_your_files#Creating_and_Deleting_files_and_folders|Accessing your files]]. faebc7bff240511e9eeb59f2b365b0f26ed50d1d 1526 1512 2021-08-13T14:00:38Z Vincenttc 21 wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. {{info|In this guide, we assume you are familiar with the files on your ULYSSIS account. If you don't know how to access these files, please read [[Accessing your files]] first.}} == Downloading the right version == To start updating MediaWiki, you will need to download the archive file of the version you want to update to. If you did not receive an email from our [[Software Version Checker]], follow the instructions in the next subsection. Otherwise, you can skip to the subsection [[#Downloading the right version using the Software Version Checker | Downloading the right version using the Software Version Checker]]. === Downloading the right version based on your wiki === You can find your current MediaWiki version by going to the <code>Special:Version</code> page on your wiki (simply paste this in the search box) and looking for the "MediaWiki" version under "Installed software". For example, for this wiki, you can find the current version at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed software.png|center|frame]] A table of all recent MediaWiki versions can be found on [https://en.wikipedia.org/wiki/MediaWiki_version_history wikipedia]. Currently supported versions are indicated by a green or yellow color in the first column. To determine which version you want to download, follow these steps: * If the ''branch'' of your version ('''the first two numbers''', like <code>1.xx</code>) is currently supported (green or yellow), you should choose the latest version for this branch. For example, for version 1.35.3, the branch is 1.35. * If this branch is not supported anymore, you should choose the most recent LTS branch. This is indicated by '''(LTS)''' in the second column. '''Make sure this LTS branch is not older than your current branch!''' * If the most recent LTS branch is older than your current branch, you should choose the newest supported branch (green). Now, click on the link of the branch you want to download. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-1.xx.yy.tar.gz</code>. Download this archive and save it somewhere on your computer. === Downloading the right version using the Software Version Checker === The email you received will contain a link to the correct MediaWiki version. This link looks something like: https://releases.wikimedia.org/mediawiki/1.xx/mediawiki-core-1.xx.yy.tar.gz Simply click this link to download the archive and save it somewhere on your computer. == Renaming the old installation == An important step in the update process is to rename the old installation directory. This way, you can simply copy your data from the old installation directory to the new installation directory during the update. Additionally, you can easily restore your old wiki if something goes wrong. The easiest way to do this, is to '''rename''' your wiki location (the directory containing your <code>LocalSettings.php</code> configuration file) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' the wiki folder to <code>wiki_old</code>. == Installing the new files == Now, you will need to upload the <code>mediawiki-1.xx.yy.tar.gz</code> file you downloaded in step 1 next to the old installation directory. For example, if your old installation directory is located in <code>www/wiki_old</code>, upload <code>mediawiki-1.xx.yy.tar.gz</code> to <code>www/</code>. After uploading, you can extract the archive file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the archive and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-1.xx.yy</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-1.xx.yy</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Finally, you need to copy certain other other files and directories from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The <code>images/</code> directory, containing the uploaded files to the wiki. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any <code>.htaccess</code> file, if present. '''Make sure you can view hidden files'''; to enable this for Cyberduck, you can look at [[Accessing_your_files#Viewing_hidden_files|Accessing your files]]. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. A list of bundled extensions can be found at https://www.mediawiki.org/wiki/Bundled_extensions_and_skins, these extensions will be updated automatically. However, for example, you might have the ULYSSIS extensions [[Securing MediaWiki using Centrale KU Leuven Login|MediaWikiShibboleth]] or [https://github.com/ULYSSIS-KUL/CompressUploads CompressUploads] installed. As with MediaWiki itself, you can find the versions of your installed extensions on the <code>Special:Version</code> page, under "Installed extensions". Extensions will often link to a website where you can download the latest versions. For example, for this wiki, you can find the installed extensions at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed extensions.png|center|frame]] Because the update instructions are different for each extension, you will have to refer to the update instructions of the extension you want to update. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the archive files: similar to the MediaWiki tar.gz archive files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. Your MediaWiki installation contains a script, called <code>update.php</code>, to perform the necessary database upgrades. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box: php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the old installation: you should remove the previously created <code>www/wiki_old</code> directory, using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing_your_files#Creating_and_Deleting_files_and_folders|Accessing your files]]. 3258ffcd5f96770f04cc270fd9ccfd3a01dccc02 1530 1526 2021-08-17T19:06:35Z Yoa 30 /* Finalizing the update */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. {{info|In this guide, we assume you are familiar with the files on your ULYSSIS account. If you don't know how to access these files, please read [[Accessing your files]] first.}} == Downloading the right version == To start updating MediaWiki, you will need to download the archive file of the version you want to update to. If you did not receive an email from our [[Software Version Checker]], follow the instructions in the next subsection. Otherwise, you can skip to the subsection [[#Downloading the right version using the Software Version Checker | Downloading the right version using the Software Version Checker]]. === Downloading the right version based on your wiki === You can find your current MediaWiki version by going to the <code>Special:Version</code> page on your wiki (simply paste this in the search box) and looking for the "MediaWiki" version under "Installed software". For example, for this wiki, you can find the current version at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed software.png|center|frame]] A table of all recent MediaWiki versions can be found on [https://en.wikipedia.org/wiki/MediaWiki_version_history wikipedia]. Currently supported versions are indicated by a green or yellow color in the first column. To determine which version you want to download, follow these steps: * If the ''branch'' of your version ('''the first two numbers''', like <code>1.xx</code>) is currently supported (green or yellow), you should choose the latest version for this branch. For example, for version 1.35.3, the branch is 1.35. * If this branch is not supported anymore, you should choose the most recent LTS branch. This is indicated by '''(LTS)''' in the second column. '''Make sure this LTS branch is not older than your current branch!''' * If the most recent LTS branch is older than your current branch, you should choose the newest supported branch (green). Now, click on the link of the branch you want to download. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-1.xx.yy.tar.gz</code>. Download this archive and save it somewhere on your computer. === Downloading the right version using the Software Version Checker === The email you received will contain a link to the correct MediaWiki version. This link looks something like: https://releases.wikimedia.org/mediawiki/1.xx/mediawiki-core-1.xx.yy.tar.gz Simply click this link to download the archive and save it somewhere on your computer. == Renaming the old installation == An important step in the update process is to rename the old installation directory. This way, you can simply copy your data from the old installation directory to the new installation directory during the update. Additionally, you can easily restore your old wiki if something goes wrong. The easiest way to do this, is to '''rename''' your wiki location (the directory containing your <code>LocalSettings.php</code> configuration file) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' the wiki folder to <code>wiki_old</code>. == Installing the new files == Now, you will need to upload the <code>mediawiki-1.xx.yy.tar.gz</code> file you downloaded in step 1 next to the old installation directory. For example, if your old installation directory is located in <code>www/wiki_old</code>, upload <code>mediawiki-1.xx.yy.tar.gz</code> to <code>www/</code>. After uploading, you can extract the archive file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the archive and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-1.xx.yy</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-1.xx.yy</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Finally, you need to copy certain other other files and directories from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The <code>images/</code> directory, containing the uploaded files to the wiki. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any <code>.htaccess</code> file, if present. '''Make sure you can view hidden files'''; to enable this for Cyberduck, you can look at [[Accessing_your_files#Viewing_hidden_files|Accessing your files]]. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. A list of bundled extensions can be found at https://www.mediawiki.org/wiki/Bundled_extensions_and_skins, these extensions will be updated automatically. However, for example, you might have the ULYSSIS extensions [[Securing MediaWiki using Centrale KU Leuven Login|MediaWikiShibboleth]] or [https://github.com/ULYSSIS-KUL/CompressUploads CompressUploads] installed. As with MediaWiki itself, you can find the versions of your installed extensions on the <code>Special:Version</code> page, under "Installed extensions". Extensions will often link to a website where you can download the latest versions. For example, for this wiki, you can find the installed extensions at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed extensions.png|center|frame]] Because the update instructions are different for each extension, you will have to refer to the update instructions of the extension you want to update. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the archive files: similar to the MediaWiki tar.gz archive files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. Your MediaWiki installation contains a script, called <code>update.php</code>, to perform the necessary database upgrades. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box (of course, replace <code><wiki installation location></code> with the location of your new installation): php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] However, if you did encounter any errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the old installation: you should remove the previously created <code>www/wiki_old</code> directory, using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing_your_files#Creating_and_Deleting_files_and_folders|Accessing your files]]. c3fd4b69a57cb5b1f875abc478490d4cca2b381f 1531 1530 2021-08-17T19:13:33Z Yoa 30 /* Finalizing the update */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. {{info|In this guide, we assume you are familiar with the files on your ULYSSIS account. If you don't know how to access these files, please read [[Accessing your files]] first.}} == Downloading the right version == To start updating MediaWiki, you will need to download the archive file of the version you want to update to. If you did not receive an email from our [[Software Version Checker]], follow the instructions in the next subsection. Otherwise, you can skip to the subsection [[#Downloading the right version using the Software Version Checker | Downloading the right version using the Software Version Checker]]. === Downloading the right version based on your wiki === You can find your current MediaWiki version by going to the <code>Special:Version</code> page on your wiki (simply paste this in the search box) and looking for the "MediaWiki" version under "Installed software". For example, for this wiki, you can find the current version at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed software.png|center|frame]] A table of all recent MediaWiki versions can be found on [https://en.wikipedia.org/wiki/MediaWiki_version_history wikipedia]. Currently supported versions are indicated by a green or yellow color in the first column. To determine which version you want to download, follow these steps: * If the ''branch'' of your version ('''the first two numbers''', like <code>1.xx</code>) is currently supported (green or yellow), you should choose the latest version for this branch. For example, for version 1.35.3, the branch is 1.35. * If this branch is not supported anymore, you should choose the most recent LTS branch. This is indicated by '''(LTS)''' in the second column. '''Make sure this LTS branch is not older than your current branch!''' * If the most recent LTS branch is older than your current branch, you should choose the newest supported branch (green). Now, click on the link of the branch you want to download. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-1.xx.yy.tar.gz</code>. Download this archive and save it somewhere on your computer. === Downloading the right version using the Software Version Checker === The email you received will contain a link to the correct MediaWiki version. This link looks something like: https://releases.wikimedia.org/mediawiki/1.xx/mediawiki-core-1.xx.yy.tar.gz Simply click this link to download the archive and save it somewhere on your computer. == Renaming the old installation == An important step in the update process is to rename the old installation directory. This way, you can simply copy your data from the old installation directory to the new installation directory during the update. Additionally, you can easily restore your old wiki if something goes wrong. The easiest way to do this, is to '''rename''' your wiki location (the directory containing your <code>LocalSettings.php</code> configuration file) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' the wiki folder to <code>wiki_old</code>. == Installing the new files == Now, you will need to upload the <code>mediawiki-1.xx.yy.tar.gz</code> file you downloaded in step 1 next to the old installation directory. For example, if your old installation directory is located in <code>www/wiki_old</code>, upload <code>mediawiki-1.xx.yy.tar.gz</code> to <code>www/</code>. After uploading, you can extract the archive file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the archive and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-1.xx.yy</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-1.xx.yy</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Finally, you need to copy certain other other files and directories from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by creating a "New Browser". Right click the '''new''' directory, and click "New Browser". [[File:Cyberduck new browser.png|thumb|center]] Then, you can simply place both windows next to each other, and drag-and-drop files or directories to copy them from the '''old''' directory to the '''new''' directory. For example, copying <code>LocalSettings.php</code>: [[File:Cyberduck drag and drop.png|center|750px]] Although the exact files you need to copy are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The <code>images/</code> directory, containing the uploaded files to the wiki. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any <code>.htaccess</code> file, if present. '''Make sure you can view hidden files'''; to enable this for Cyberduck, you can look at [[Accessing_your_files#Viewing_hidden_files|Accessing your files]]. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. A list of bundled extensions can be found at https://www.mediawiki.org/wiki/Bundled_extensions_and_skins, these extensions will be updated automatically. However, for example, you might have the ULYSSIS extensions [[Securing MediaWiki using Centrale KU Leuven Login|MediaWikiShibboleth]] or [https://github.com/ULYSSIS-KUL/CompressUploads CompressUploads] installed. As with MediaWiki itself, you can find the versions of your installed extensions on the <code>Special:Version</code> page, under "Installed extensions". Extensions will often link to a website where you can download the latest versions. For example, for this wiki, you can find the installed extensions at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed extensions.png|center|frame]] Because the update instructions are different for each extension, you will have to refer to the update instructions of the extension you want to update. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the archive files: similar to the MediaWiki tar.gz archive files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. Your MediaWiki installation contains a script, called <code>update.php</code>, to perform the necessary database upgrades. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box (of course, replace <code><wiki installation location></code> with the location of your new installation): php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] If you get the error <code>Could not open input file</code>, you might have misspelled the installation location. Double check the path to make sure everything is correct. If you encounter any other errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the old installation: you should remove the previously created <code>www/wiki_old</code> directory, using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing_your_files#Creating_and_Deleting_files_and_folders|Accessing your files]]. aaa672cb209705cd543f5fada06e888711b1fb80 1537 1531 2021-08-31T23:16:31Z Thomasd 40 wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. {{info|In this guide, we assume you are familiar with the files on your ULYSSIS account. If you don't know how to access these files, please read [[Accessing your files]] first.}} == Downloading the right version == To start updating MediaWiki, you will need to download the archive file of the version you want to update to. If you did not receive an email from our [[Software Version Checker]], follow the instructions in the next subsection. Otherwise, you can skip to the subsection [[#Downloading the right version using the Software Version Checker | Downloading the right version using the Software Version Checker]]. === Downloading the right version based on your wiki === You can find your current MediaWiki version by going to the <code>Special:Version</code> page on your wiki (simply paste this in the search box) and looking for the "MediaWiki" version under "Installed software". For example, for this wiki, you can find the current version at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed software.png|center|frame]] A table of all recent MediaWiki versions can be found on [https://en.wikipedia.org/wiki/MediaWiki_version_history wikipedia]. Currently supported versions are indicated by a green or yellow color in the first column. To determine which version you want to download, follow these steps: * If the ''branch'' of your version ('''the first two numbers''', like <code>1.xx</code>) is currently supported (green or yellow), you should choose the latest version for this branch. For example, for version 1.35.3, the branch is 1.35. * If this branch is not supported anymore, you should choose the most recent LTS branch. This is indicated by '''(LTS)''' in the second column. '''Make sure this LTS branch is not older than your current branch!''' * If the most recent LTS branch is older than your current branch, you should choose the newest supported branch (green). Now, click on the link of the branch you want to download. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-1.xx.yy.tar.gz</code>. Download this archive and save it somewhere on your computer. === Downloading the right version using the Software Version Checker === The email you received will contain a link to the correct MediaWiki version. This link looks something like: https://releases.wikimedia.org/mediawiki/1.xx/mediawiki-core-1.xx.yy.tar.gz Simply click this link to download the archive and save it somewhere on your computer. == Renaming the old installation == An important step in the update process is to rename the old installation directory. This way, you can simply copy your data from the old installation directory to the new installation directory during the update. Additionally, you can easily restore your old wiki if something goes wrong. The easiest way to do this, is to '''rename''' your wiki location (the directory containing your <code>LocalSettings.php</code> configuration file) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' the wiki folder to <code>wiki_old</code>. == Installing the new files == Now, you will need to upload the <code>mediawiki-1.xx.yy.tar.gz</code> file you downloaded in step 1 next to the old installation directory. For example, if your old installation directory is located in <code>www/wiki_old</code>, upload <code>mediawiki-1.xx.yy.tar.gz</code> to <code>www/</code>. After uploading, you can extract the archive file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the archive and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-1.xx.yy</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-1.xx.yy</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Finally, you need to move certain other other files and directories from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by going up a directory (so if your wiki is in <code>www/wiki</code>, go to <code>www</code>), and drag-and-dropping the necessary files and directories. For example, moving <code>LocalSettings.php</code> by drag-and-dropping it from <code>wiki_old</code> into <code>wiki</code>: [[File:Cyberduck wiki move 1.png|thumb|center]] [[File:Cyberduck wiki move 2.png|thumb|center]] Although the exact files you need to move are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The <code>images/</code> directory, containing the uploaded files to the wiki. Because the new wiki directory already contains an (empty) <code>images</code> directory, you need to delete that one first by right-clicking on it and pressing "Delete". Make sure to only delete the <code>images</code> directory in the '''new''' wiki directory. Then you can move the old <code>images</code> directory into the new wiki directory. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any <code>.htaccess</code> file, if present. '''Make sure you can view hidden files'''; to enable this for Cyberduck, you can look at [[Accessing_your_files#Viewing_hidden_files|Accessing your files]]. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. A list of bundled extensions can be found at https://www.mediawiki.org/wiki/Bundled_extensions_and_skins, these extensions will be updated automatically. However, for example, you might have the ULYSSIS extensions [[Securing MediaWiki using Centrale KU Leuven Login|MediaWikiShibboleth]] or [https://github.com/ULYSSIS-KUL/CompressUploads CompressUploads] installed. As with MediaWiki itself, you can find the versions of your installed extensions on the <code>Special:Version</code> page, under "Installed extensions". Extensions will often link to a website where you can download the latest versions. For example, for this wiki, you can find the installed extensions at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed extensions.png|center|frame]] Because the update instructions are different for each extension, you will have to refer to the update instructions of the extension you want to update. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the archive files: similar to the MediaWiki tar.gz archive files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. Your MediaWiki installation contains a script, called <code>update.php</code>, to perform the necessary database upgrades. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box (of course, replace <code><wiki installation location></code> with the location of your new installation): php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] If you get the error <code>Could not open input file</code>, you might have misspelled the installation location. Double check the path to make sure everything is correct. If you encounter any other errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the old installation: you should remove the previously created <code>www/wiki_old</code> directory, using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing_your_files#Creating_and_Deleting_files_and_folders|Accessing your files]]. 6c6d977333ca2cac223a055c5135b5a0ead48788 1538 1537 2021-08-31T23:18:32Z Thomasd 40 /* Installing the new files */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. {{info|In this guide, we assume you are familiar with the files on your ULYSSIS account. If you don't know how to access these files, please read [[Accessing your files]] first.}} == Downloading the right version == To start updating MediaWiki, you will need to download the archive file of the version you want to update to. If you did not receive an email from our [[Software Version Checker]], follow the instructions in the next subsection. Otherwise, you can skip to the subsection [[#Downloading the right version using the Software Version Checker | Downloading the right version using the Software Version Checker]]. === Downloading the right version based on your wiki === You can find your current MediaWiki version by going to the <code>Special:Version</code> page on your wiki (simply paste this in the search box) and looking for the "MediaWiki" version under "Installed software". For example, for this wiki, you can find the current version at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed software.png|center|frame]] A table of all recent MediaWiki versions can be found on [https://en.wikipedia.org/wiki/MediaWiki_version_history wikipedia]. Currently supported versions are indicated by a green or yellow color in the first column. To determine which version you want to download, follow these steps: * If the ''branch'' of your version ('''the first two numbers''', like <code>1.xx</code>) is currently supported (green or yellow), you should choose the latest version for this branch. For example, for version 1.35.3, the branch is 1.35. * If this branch is not supported anymore, you should choose the most recent LTS branch. This is indicated by '''(LTS)''' in the second column. '''Make sure this LTS branch is not older than your current branch!''' * If the most recent LTS branch is older than your current branch, you should choose the newest supported branch (green). Now, click on the link of the branch you want to download. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-1.xx.yy.tar.gz</code>. Download this archive and save it somewhere on your computer. === Downloading the right version using the Software Version Checker === The email you received will contain a link to the correct MediaWiki version. This link looks something like: https://releases.wikimedia.org/mediawiki/1.xx/mediawiki-core-1.xx.yy.tar.gz Simply click this link to download the archive and save it somewhere on your computer. == Renaming the old installation == An important step in the update process is to rename the old installation directory. This way, you can simply copy your data from the old installation directory to the new installation directory during the update. Additionally, you can easily restore your old wiki if something goes wrong. The easiest way to do this, is to '''rename''' your wiki location (the directory containing your <code>LocalSettings.php</code> configuration file) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' the wiki folder to <code>wiki_old</code>. == Installing the new files == Now, you will need to upload the <code>mediawiki-1.xx.yy.tar.gz</code> file you downloaded in step 1 next to the old installation directory. For example, if your old installation directory is located in <code>www/wiki_old</code>, upload <code>mediawiki-1.xx.yy.tar.gz</code> to <code>www/</code>. After uploading, you can extract the archive file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the archive and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-1.xx.yy</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-1.xx.yy</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Finally, you need to move certain other other files and directories from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by going up a directory (so if your wiki is in <code>www/wiki</code>, go to <code>www</code>), and drag-and-dropping the necessary files and directories. For example, moving <code>LocalSettings.php</code> by drag-and-dropping it from <code>wiki_old</code> into <code>wiki</code>: [[File:Cyberduck wiki move 1.png|500px]] [[File:Cyberduck wiki move 2.png|500px]] Although the exact files you need to move are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The <code>images/</code> directory, containing the uploaded files to the wiki. Because the new wiki directory already contains an (empty) <code>images</code> directory, you need to delete that one first by right-clicking on it and pressing "Delete". Make sure to only delete the <code>images</code> directory in the '''new''' wiki directory. Then you can move the old <code>images</code> directory into the new wiki directory. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any <code>.htaccess</code> file, if present. '''Make sure you can view hidden files'''; to enable this for Cyberduck, you can look at [[Accessing_your_files#Viewing_hidden_files|Accessing your files]]. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. A list of bundled extensions can be found at https://www.mediawiki.org/wiki/Bundled_extensions_and_skins, these extensions will be updated automatically. However, for example, you might have the ULYSSIS extensions [[Securing MediaWiki using Centrale KU Leuven Login|MediaWikiShibboleth]] or [https://github.com/ULYSSIS-KUL/CompressUploads CompressUploads] installed. As with MediaWiki itself, you can find the versions of your installed extensions on the <code>Special:Version</code> page, under "Installed extensions". Extensions will often link to a website where you can download the latest versions. For example, for this wiki, you can find the installed extensions at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed extensions.png|center|frame]] Because the update instructions are different for each extension, you will have to refer to the update instructions of the extension you want to update. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the archive files: similar to the MediaWiki tar.gz archive files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. Your MediaWiki installation contains a script, called <code>update.php</code>, to perform the necessary database upgrades. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box (of course, replace <code><wiki installation location></code> with the location of your new installation): php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] If you get the error <code>Could not open input file</code>, you might have misspelled the installation location. Double check the path to make sure everything is correct. If you encounter any other errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the old installation: you should remove the previously created <code>www/wiki_old</code> directory, using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing_your_files#Creating_and_Deleting_files_and_folders|Accessing your files]]. 3e78229a7da748bb726320448c697c6ce0424e79 6 204 1498 2021-08-04T21:47:38Z Yoa 30 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 181 1503 1360 2021-08-08T12:43:30Z Yoa 30 Yoa uploaded a new version of [[File:Cyberduck send command.png]] wikitext text/x-wiki Sending an SSH command to a server using Cyberduck 599e257b8d5f7572f3ea8b408c5f388d621e89b5 6 178 1504 1352 2021-08-08T12:43:36Z Yoa 30 Yoa uploaded a new version of [[File:Cyberduck expand.png]] wikitext text/x-wiki Expanding archives using Cyberduck 077907dd20ef9f32b540263acda2edef39efa434 6 177 1505 1348 2021-08-08T12:43:42Z Yoa 30 Yoa uploaded a new version of [[File:Cyberduck rename.png]] wikitext text/x-wiki Cyberduck renaming 7e646c22c1d9a3f3f91bf76b42864d5a91edad0d 6 179 1506 1353 2021-08-08T12:43:52Z Yoa 30 Yoa uploaded a new version of [[File:Cyberduck new browser.png]] wikitext text/x-wiki Creating a new browser using Cyberduck 020c9a53738ba7d26f0c5953c7d3bfae3aec50a4 0 5 1513 1467 2021-08-09T09:57:01Z Bert 8 wikitext text/x-wiki This documentation article will explain how to upload, download, move and delete files on your account using a graphical user interface. If you are a more advanced user, you may want to use the command line to administer your files, in that case [[Accessing shell servers over SSH]] is probably a more relevant documentation page for you. Many different SFTP clients are available depending on your needs and what operating system you run on your computer. For Windows and Mac users, we recommend the graphical SFTP client [https://cyberduck.io/download/ Cyberduck]. If you're using Linux, your file manager usually has a built-in option to connect using the details mentioned in [[#Connecting | Connecting]]. ==Connecting== {{notice|Keep in mind|Our automatic security systems may temporarily prevent you from connecting over SSH/SFTP if you try to connect several times with the wrong username and/or password. This will result in the connection being refused. You can switch between sftp://ssh1.ulyssis.org and sftp://ssh2.ulyssis.org when this happens or wait 10 minutes. More information on our security measures is available on [[ULYSSIS security measures]]}} A Cyberduck-specific explanation can be found at [[#Connecting_2 | Cyberduck: Connecting]]. To access your files using another program you will have to enter the following connection details: * Protocol: SFTP * Server: "ssh1.ulyssis.org" or "ssh2.ulyssis.org" * Port: 22 * Username: your ULYSSIS account username, the one you use for [https://ucc.ulyssis.org ucc.ulyssis.org] * Password: your ULYSSIS account password On our servers, your files are stored in your home folder located at <code>/home/(group)/(username)/</code>, where the group depends upon your account type and the username is your ULYSSIS account username. Any regular user is stored within the <code>user</code> group, and their files are stored within <code>/home/user/(username)</code>. For organizations, <code>org</code> is used, so files are stored within <code>/home/org/(username)</code>. Most (S)FTP clients will by default display your own home folder after you've logged in. ==Using Cyberduck== To get started, download [https://cyberduck.io/download/ Cyberduck] from the official website. You can then install the downloaded file like you would install any other application. Once installed, launch Cyberduck and connect using the steps below. === Connecting === <ul> <li>Click on Open Connection in the top-left corner.</li> <li>Protocol (upper dropdown menu): "SFTP (SSH File Transfer Protocol)"</li> <li>Username: your ULYSSIS account username, the one you use for [https://ucc.ulyssis.org ucc.ulyssis.org]</li> <li>Password: your ULYSSIS account password</li> <li>Server: "ssh1.ulyssis.org" or "ssh2.ulyssis.org" <li>Enable "Save Password" if you don't want to enter your password every time you want to connect using this computer</li> <li>Press connect</li> </ul>[[File:Open-connection-WB.png|alt=|left|frame]] If you get a dialog window about an unknown fingerprint, tick the "Always" box in the bottom left and then click allow. You will now be connected and able to access your files. [[File:Fingerprint dialog window.png|none|alt=|frame]] When you connect to a server using Cyberduck, the remote files will appear: [[File:Cyberduck connection interface.png|none|alt=|frame]] ===Navigating=== You can open a folder by double-clicking it. To go back up one step you can press the "Up" button to the right of the "Current Folder" dropdown. To go back up multiple steps you can click on the "Current Folder" dropdown and select which folder you would like to go back to.[[File:Navigating-WB.png|none|alt=|frame]] ===Viewing hidden files=== To make hidden files, whose filename always start with a '.', visible, click on View -> Show Hidden Files. This is necessary because some files like ".htaccess" and ".user.ini" are hidden by default and they need to be edited sometimes. [[File:Hidden Files.png|none|thumb]] ===Uploading files and folders=== To upload a file or folder, you can use the "Upload" button in the top menu bar and select the file or folder you wish to upload using your file manager. [[File:Cyberduck-upload-button.png|alt=|frame|left]] Or you can drag and drop it from your file manager (Explorer for Windows, Finder for Mac) into the current folder in Cyberduck. [[File:Upload-drag-WB.png|none|alt=|thumb|514x514px]] ===Downloading files and folders=== To download files and folders, you can drag and drop it into your file manager (Explorer for Windows or Finder for Mac), just like uploading but in the other direction. For files specifically it's also possible to simply double-click the file. This will then download it to your Downloads folder. ===Creating and Deleting files and folders=== To create a folder, you right click where you want your folder to be located and then click the "New Folder" option as seen below. You can then type a name for your new folder. To create a file, you right click in the folder where you want your file to be located and then click the "New File" option as seen below. You can then type a name for your new file, making sure to include the necessary extension (e.g. file.txt for a text file, file.php for a PHP file, etc.). You can delete a file or folder by selecting it and then either pressing the "Delete" key on your keyboard, or right-clicking and selecting "Delete". [[File:Delete-cyberduck-WB.png|alt=|thumb|384x384px|none]] ===Editing files=== Cyberduck allows you to edit files remotely by selecting a file and then pressing the "Edit" button in the top menu bar, next to the "Upload" button. This opens the file in your text editor (by default Notepad for Windows and TextEdit for Mac). After you're done editing, make sure to save the file using the text editor and then close it. [[File:Edit.png|none|alt=|frame]] [[Category:Files]] [[Category:Shell]] bd3c098dcd4a9b6d03888cfd30590285bffa5eec 0 4 1514 1378 2021-08-09T09:58:28Z Bert 8 wikitext text/x-wiki This documentation articles is aimed at more advanced users who want to use the command line to administer files or perform other actions on their ULYSSIS account. If you prefer to upload, download, move and delete files on your account using a graphical user interface, then please refer to [[Accessing your files]]. Users can access the ULYSSIS servers through two machines: <code>ssh1.ulyssis.org</code> and <code>ssh2.ulyssis.org</code>. Both of them run Linux. You can run commands on these servers or use them to access the files on your ULYSSIS account. The servers can only be accessed trough SSH, not through FTP or any other protocol. ==Running commands== To run a command on the shell servers, you will need to connect to them using a terminal. Our servers do not support a full graphical interface. ===Linux=== On Linux, you can just open a terminal and connect to the servers by using one of the following commands (with <code>username</code> your username): ssh username@ssh1.ulyssis.org ssh username@ssh2.ulyssis.org Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. ===Windows=== Windows doesn't support native terminals, so you will have to download a program first. A good option is [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty], which is completely free and doesn't require any installation. Just download it and run the .exe file. The parameters: *Host name: ssh1.ulyssis.org or ssh2.ulyssis.org *Protocol: SSH *Port: 22 (should be set automatically) You can save these options for later on. Next, you will be asked to give your password. Doing all this will open a terminal to the remote server which can be used the same way as a Linux terminal. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. More information about Putty can be found at http://the.earth.li/~sgtatham/putty/0.60/htmldoc/. ===Mac=== On Mac, you can just open Terminal. This application can be found in the Utilities folder within your Application folder. If you don't find it there, you can use Spotlight to find it. You can now connect to the servers by using one of the following commands (with <code>username</code> your username): ssh username@ssh1.ulyssis.org ssh username@ssh2.ulyssis.org Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use ctrl+D. ===Useful ideas=== Here are some useful ideas about what you could do with your shell server access: *[[Accessing your files]] *[[Fetch your KU Leuven email into another email address]] *[[ULYSSIS public IRC]] ===Useful commands=== Some useful commands can be found [[Useful Linux Commands|here]]. [[Category:Shell]] 530847209d30530a28d9c2888a57c7171717deda 1515 1514 2021-08-09T09:59:55Z Bert 8 wikitext text/x-wiki This documentation articles is aimed at more advanced users who want to use the command line to administer files or perform other actions on their ULYSSIS account. If you prefer to upload, download, move and delete files on your account using a graphical user interface, then please refer to [[Accessing your files]]. Users can access the ULYSSIS servers through two machines: <code>ssh1.ulyssis.org</code> and <code>ssh2.ulyssis.org</code>. Both of them run Linux. You can run commands on these servers or use them to access the files on your ULYSSIS account. The servers can only be accessed trough SSH, not through FTP or any other protocol. ==Connecting== To run a command on the shell servers, you will need to connect to them using a terminal. Our servers do not support a full graphical interface. ===Connecting on Linux=== On Linux, you can just open a terminal and connect to the servers by using one of the following commands (with <code>username</code> your username): ssh username@ssh1.ulyssis.org ssh username@ssh2.ulyssis.org Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. ===Connecting on macOS=== On Mac, you can just open Terminal. This application can be found in the Utilities folder within your Application folder. If you don't find it there, you can use Spotlight to find it. You can now connect to the servers by using one of the following commands (with <code>username</code> your username): ssh username@ssh1.ulyssis.org ssh username@ssh2.ulyssis.org Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use ctrl+D. ===Connecting on Windows=== Windows doesn't support native terminals, so you will have to download a program first. A good option is [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty], which is completely free and doesn't require any installation. Just download it and run the .exe file. The parameters: *Host name: ssh1.ulyssis.org or ssh2.ulyssis.org *Protocol: SSH *Port: 22 (should be set automatically) You can save these options for later on. Next, you will be asked to give your password. Doing all this will open a terminal to the remote server which can be used the same way as a Linux terminal. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. More information about Putty can be found at http://the.earth.li/~sgtatham/putty/0.60/htmldoc/. ===Useful ideas=== Here are some useful ideas about what you could do with your shell server access: *[[Accessing your files]] *[[Fetch your KU Leuven email into another email address]] *[[ULYSSIS public IRC]] ===Useful commands=== Some useful commands can be found [[Useful Linux Commands|here]]. [[Category:Shell]] ed3317e54c091577f13a7499617a1fd9d91a3a3a 1516 1515 2021-08-09T12:34:59Z Bert 8 wikitext text/x-wiki This documentation articles is aimed at more advanced users who want to use the command line to administer files or perform other actions on their ULYSSIS account. If you prefer to upload, download, move and delete files on your account using a graphical user interface, then please refer to [[Accessing your files]]. ==Connecting== Users can access ULYSSIS services through two shell servers: <code>ssh1.ulyssis.org</code> and <code>ssh2.ulyssis.org</code>. Both of them run Linux. You can run commands on these servers or use them to access the files on your ULYSSIS account. These servers can only be accessed trough SSH or SFTP (see [[Accessing your files]] for the latter). For SSH access, use the following detials: * Server: "ssh1.ulyssis.org" or "ssh2.ulyssis.org" * Port: 22 * Username: your ULYSSIS account username, the one you use for [https://ucc.ulyssis.org ucc.ulyssis.org] * Password: your ULYSSIS account password ===Connecting on Linux=== On Linux, you can just open a terminal and connect to the servers by using one of the following commands (with <code>username</code> your username): ssh username@ssh1.ulyssis.org ssh username@ssh2.ulyssis.org Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. To copy and paste inside a terminal window, you usually have to use Ctrl+Shift+C and Ctrl+Shift+V, but this may depend on your choice of terminal and its settings. ===Connecting on macOS=== On Mac, you can use Terminal app. This application can be found in the Utilities folder within your Application folder. You can also use Spotlight to find it. You can now connect to the servers by using one of the following commands (with <code>username</code> your username): ssh username@ssh1.ulyssis.org ssh username@ssh2.ulyssis.org Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use ctrl+D. ===Connecting on Windows=== ==== Windows 10 ==== Windows has built-in SSH capabilities since the April 2018 update of Windows 10. Simply search and launch Powershell from your menu. You can now connect to the servers by using one of the following commands (with <code>username</code> your username): ssh username@ssh1.ulyssis.org ssh username@ssh2.ulyssis.org Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use ctrl+D. ==== Older versions of Windows ==== Older versions of Windows don't support native terminals, so you will have to download one first. An option that works on any version of Windows is [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty], which is completely free and doesn't require any installation. Just download it and run the .exe file. The parameters: *Host name: ssh1.ulyssis.org or ssh2.ulyssis.org *Protocol: SSH *Port: 22 (should be set automatically) You can save these options for later on. Next, you will be asked to give your password. Doing all this will open a terminal to the remote server which can be used the same way as a Linux terminal. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. To copy and paste in Putty, you have to right click. More information about Putty can be found at http://the.earth.li/~sgtatham/putty/0.60/htmldoc/. ===Getting started=== Once connected, you can start executing commands to manage your files or perform tasks. You can find a simple overview of basis commands on [[Useful Linux Commands]]. We also have several articles detailing commands for more specific tasks: *[[Managing Cron jobs]] *[[Reducing disk usage]] *[[ULYSSIS public IRC]] *[[Making Backups]] *[[Using (Fast)CGI for non-PHP websites]] *[[Fetch your KU Leuven email into another email address]] ===Using rsync over SSH=== Rsync is a well known utility to transfer and synchronise files across locations. You can use it to synchronise between two local folders, but it also supports synchronisation across an SSH connection. To for example sync the local folder <code>myproject</code> exactly to the <code>www/myproject</code> folder on your ULYSSIS account, you can use the following command: <pre>rsync -rLpvz --delete myproject/ username@ssh1.ulyssis.org:~/www/myproject</pre> Refer to the rsync man page (using <code>man rsync</code>) for more details about the many options of rsync, including the use of -L, -p and --delete in the example above. [[Category:Shell]] e92b67a3cd944c3e6b7f45b43ea1c0c9db575865 1517 1516 2021-08-09T12:35:21Z Bert 8 wikitext text/x-wiki This documentation articles is aimed at more advanced users who want to use the command line to administer files or perform other actions on their ULYSSIS account. If you prefer to upload, download, move and delete files on your account using a graphical user interface, then please refer to [[Accessing your files]]. ==Connecting== Users can access ULYSSIS services through two shell servers: <code>ssh1.ulyssis.org</code> and <code>ssh2.ulyssis.org</code>. Both of them run Linux. You can run commands on these servers or use them to access the files on your ULYSSIS account. These servers can only be accessed trough SSH or SFTP (see [[Accessing your files]] for the latter). For SSH access, use the following detials: * Server: "ssh1.ulyssis.org" or "ssh2.ulyssis.org" * Port: 22 * Username: your ULYSSIS account username, the one you use for [https://ucc.ulyssis.org ucc.ulyssis.org] * Password: your ULYSSIS account password ===Connecting on Linux=== On Linux, you can just open a terminal and connect to the servers by using one of the following commands (with <code>username</code> your username): ssh username@ssh1.ulyssis.org ssh username@ssh2.ulyssis.org Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. To copy and paste inside a terminal window, you usually have to use Ctrl+Shift+C and Ctrl+Shift+V, but this may depend on your choice of terminal and its settings. ===Connecting on macOS=== On Mac, you can use Terminal app. This application can be found in the Utilities folder within your Application folder. You can also use Spotlight to find it. You can now connect to the servers by using one of the following commands (with <code>username</code> your username): ssh username@ssh1.ulyssis.org ssh username@ssh2.ulyssis.org Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use ctrl+D. ===Connecting on Windows=== ==== Windows 10 ==== Windows has built-in SSH capabilities since the April 2018 update of Windows 10. Simply search and launch Powershell from your menu. You can now connect to the servers by using one of the following commands (with <code>username</code> your username): ssh username@ssh1.ulyssis.org ssh username@ssh2.ulyssis.org Enter your password and you're connected. By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use ctrl+D. ==== Older versions of Windows ==== Older versions of Windows don't support native terminals, so you will have to download one first. An option that works on any version of Windows is [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty], which is completely free and doesn't require any installation. Just download it and run the .exe file. The parameters: *Host name: ssh1.ulyssis.org or ssh2.ulyssis.org *Protocol: SSH *Port: 22 (should be set automatically) You can save these options for later on. Next, you will be asked to give your password. Doing all this will open a terminal to the remote server which can be used the same way as a Linux terminal. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. To copy and paste in Putty, you have to right click. More information about Putty can be found at http://the.earth.li/~sgtatham/putty/0.60/htmldoc/. ==Getting started== Once connected, you can start executing commands to manage your files or perform tasks. You can find a simple overview of basis commands on [[Useful Linux Commands]]. We also have several articles detailing commands for more specific tasks: *[[Managing Cron jobs]] *[[Reducing disk usage]] *[[ULYSSIS public IRC]] *[[Making Backups]] *[[Using (Fast)CGI for non-PHP websites]] *[[Fetch your KU Leuven email into another email address]] ==Using rsync over SSH== Rsync is a well known utility to transfer and synchronise files across locations. You can use it to synchronise between two local folders, but it also supports synchronisation across an SSH connection. To for example sync the local folder <code>myproject</code> exactly to the <code>www/myproject</code> folder on your ULYSSIS account, you can use the following command: <pre>rsync -rLpvz --delete myproject/ username@ssh1.ulyssis.org:~/www/myproject</pre> Refer to the rsync man page (using <code>man rsync</code>) for more details about the many options of rsync, including the use of -L, -p and --delete in the example above. [[Category:Shell]] af7eed2145f92a4f45e59501c24e2f318471fef9 1518 1517 2021-08-09T12:37:56Z Bert 8 wikitext text/x-wiki This documentation articles is aimed at more advanced users who want to use the command line to administer files or perform other actions on their ULYSSIS account. If you prefer to upload, download, move and delete files on your account using a graphical user interface, then please refer to [[Accessing your files]]. ==Connecting== Users can access ULYSSIS services through two shell servers: <code>ssh1.ulyssis.org</code> and <code>ssh2.ulyssis.org</code>. Both of them run Linux. You can run commands on these servers or use them to access the files on your ULYSSIS account. These servers can only be accessed trough SSH or SFTP (see [[Accessing your files]] for the latter). For SSH access, use the following detials: * Server: "ssh1.ulyssis.org" or "ssh2.ulyssis.org" * Port: 22 * Username: your ULYSSIS account username, the one you use for [https://ucc.ulyssis.org ucc.ulyssis.org] * Password: your ULYSSIS account password ===Connecting on Linux=== On Linux, you can just open a terminal and connect to the servers by using one of the following commands (with <code>username</code> your username) followed by your password (once prompted): ssh username@ssh1.ulyssis.org ssh username@ssh2.ulyssis.org By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. To copy and paste inside a terminal window, you usually have to use Ctrl+Shift+C and Ctrl+Shift+V, but this may depend on your choice of terminal and its settings. ===Connecting on macOS=== On Mac, you can use Terminal app. This application can be found in the Utilities folder within your Application folder. You can also use Spotlight to find it. You can now connect to the servers by using one of the following commands (with <code>username</code> your username) followed by your password (once prompted): ssh username@ssh1.ulyssis.org ssh username@ssh2.ulyssis.org By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use ctrl+D. ===Connecting on Windows=== ==== Windows 10 ==== Windows has built-in SSH capabilities since the April 2018 update of Windows 10. Simply search and launch Powershell from your menu. You can now connect to the servers by using one of the following commands (with <code>username</code> your username) followed by your password (once prompted): ssh username@ssh1.ulyssis.org ssh username@ssh2.ulyssis.org By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use ctrl+D. ==== Older versions of Windows ==== Older versions of Windows don't support native terminals, so you will have to download one first. An option that works on any version of Windows is [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty], which is completely free and doesn't require any installation. Just download it and run the .exe file. The parameters: *Host name: ssh1.ulyssis.org or ssh2.ulyssis.org *Protocol: SSH *Port: 22 (should be set automatically) You can save these options for later on. Next, you will be asked to give your password. Doing all this will open a terminal to the remote server which can be used the same way as a Linux terminal. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. To copy and paste in Putty, you have to right click. More information about Putty is available on http://the.earth.li/~sgtatham/putty/0.60/htmldoc/. ==Getting started== Once connected, you can start executing commands to manage your files or perform tasks. You can find a simple overview of basis commands on [[Useful Linux Commands]]. We also have several articles detailing commands for more specific tasks: *[[Managing Cron jobs]] *[[Reducing disk usage]] *[[ULYSSIS public IRC]] *[[Making Backups]] *[[Using (Fast)CGI for non-PHP websites]] *[[Fetch your KU Leuven email into another email address]] ==Using rsync over SSH== Rsync is a well known utility to transfer and synchronise files across locations. You can use it to synchronise between two local folders, but it also supports synchronisation across an SSH connection. To for example sync the local folder <code>myproject</code> exactly to the <code>www/myproject</code> folder on your ULYSSIS account, you can use the following command: <pre>rsync -rLpvz --delete myproject/ username@ssh1.ulyssis.org:~/www/myproject</pre> Refer to the rsync man page (using <code>man rsync</code>) for more details about the many options of rsync, including the use of -L, -p and --delete in the example above. [[Category:Shell]] 7a96a3e809f3351d60b0e146ecd7230e873bb591 1533 1518 2021-08-18T21:41:58Z Vincenttc 21 wikitext text/x-wiki This documentation article is aimed at more advanced users who want to use the command line to administer files or perform other actions on their ULYSSIS account. If you prefer to upload, download, move and delete files on your account using a graphical user interface, then please refer to [[Accessing your files]]. ==Connecting== Users can access ULYSSIS services through two shell servers: <code>ssh1.ulyssis.org</code> and <code>ssh2.ulyssis.org</code>. Both of them run Linux (the latest Ubuntu LTS). You can run commands on these servers or use them to access the files on your ULYSSIS account. These servers can only be accessed through SSH or SFTP (see [[Accessing your files]] for the latter). For SSH access, use the following details: * Server: "ssh1.ulyssis.org" or "ssh2.ulyssis.org" * Port: 22 * Username: your ULYSSIS account username, the one you use for [https://ucc.ulyssis.org ucc.ulyssis.org] * Password: your ULYSSIS account password ===Connecting on Linux=== On Linux, you can just open a terminal and connect to the servers by using one of the following commands (with <code>username</code> your ULYSSIS username) followed by your password (once prompted): ssh username@ssh1.ulyssis.org ssh username@ssh2.ulyssis.org By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. To copy and paste inside a terminal window, you usually have to use Ctrl+Shift+C and Ctrl+Shift+V, but this may depend on your choice of terminal and its settings. ===Connecting on macOS=== On Mac, you can use Terminal app. This application can be found in the Utilities folder within your Application folder. You can also use Spotlight to find it. You can now connect to the servers by using one of the following commands (with <code>username</code> your username) followed by your password (once prompted): ssh username@ssh1.ulyssis.org ssh username@ssh2.ulyssis.org By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use ctrl+D. ===Connecting on Windows=== ==== Windows 10 ==== Windows has built-in SSH capabilities since the April 2018 update of Windows 10. Simply search and launch Powershell from your menu. You can now connect to the servers by using one of the following commands (with <code>username</code> your username) followed by your password (once prompted): ssh username@ssh1.ulyssis.org ssh username@ssh2.ulyssis.org By doing this, the terminal will now act as a terminal on the remote server. To disconnect, type <code>logout</code>, <code>exit</code> or use ctrl+D. ==== Older versions of Windows ==== Older versions of Windows don't support native terminals, so you will have to download one first. An option that works on any version of Windows is [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty], which is completely free and doesn't require any installation. Just download it and run the .exe file. The parameters: *Host name: "ssh1.ulyssis.org" or "ssh2.ulyssis.org" *Protocol: SSH *Port: 22 (should be set automatically) You can save these options for later on. Next, you will be asked to give your password. Doing all this will open a terminal to the remote server which can be used the same way as a Linux terminal. To disconnect, type <code>logout</code>, <code>exit</code> or use Ctrl+D. To copy and paste in Putty, you have to right click. More information about Putty is available on https://the.earth.li/~sgtatham/putty/latest/htmldoc/. ==Getting started== Once connected, you can start executing commands to manage your files or perform tasks. You can find a simple overview of basis commands on [[Useful Linux Commands]]. We also have several articles detailing commands for more specific tasks: *[[Managing Cron jobs]] *[[Reducing disk usage]] *[[ULYSSIS public IRC]] *[[Making Backups]] *[[Using (Fast)CGI for non-PHP websites]] *[[Fetch your KU Leuven email into another email address]] ==Using rsync over SSH== Rsync is a well known utility to transfer and synchronise files across locations. You can use it to synchronise between two local folders, but it also supports synchronisation across an SSH connection. To for example sync the local folder <code>myproject</code> exactly to the <code>www/myproject</code> folder on your ULYSSIS account, you can use the following command: <pre>rsync -rLpvz --delete myproject/ username@ssh1.ulyssis.org:~/www/myproject</pre> Refer to the rsync man page (using <code>man rsync</code>) for more details about the many options of rsync, including the use of -L, -p and --delete in the example above. [[Category:Shell]] 0b79f0288992104f6ab74c2215c722726f8e02c6 0 36 1519 1329 2021-08-09T15:09:39Z Bert 8 Redirected page to [[Accessing your files]] wikitext text/x-wiki #REDIRECT [[Accessing your files]] 620126c209e81d1302c47c9d8ed39943c38689c7 0 3 1520 1478 2021-08-09T15:11:44Z Bert 8 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Reducing disk usage|Help, my account uses too much disk space]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Making Backups]] * [[Secure file permissions]] * [[Reducing disk usage]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2020]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Sending email from websites]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL/TLS|Getting SSL/TLS (HTTPS security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Claiming a port]] * [[ULYSSIS security measures]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] * [[Spam]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up WordPress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] * [[Updating WordPress]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] * [[Using PHPPgAdmin]] * [[Using Adminer]] * [[Making Backups]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[Exporting your KU Leuven class schedule and calendar]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 1a6fc2e9013674e77ce90644b3bb91c602db060c 0 7 1521 1157 2021-08-09T15:34:56Z Bert 8 wikitext text/x-wiki ULYSSIS hosts its own IRC network. IRC stands for Internet Relay Chat, [https://en.wikipedia.org/wiki/Internet_Relay_Chat IRC on wikipedia]. It is a chat protocol that mainly focuses on group chat, but also allows for private chat. For any support questions, you are free to contact us via email on ulyssis@ulyssis.org, but if your questions are of a less sensitive nature and could benefit from a back-and-forth, it could be useful to contact us on IRC. Do keep in mind that you may have to wait until someone notices your question, which may take a while. If you don't have a question and just want to hang out in our chat, feel free to join! Keep in mind that our IRC network has been a social space for several generations, so you will find alumni and students from different walks of life there, not just ULYSSIS members and users. ==Web IRC client== If you won't regularly use our IRC or if you just want to check it out, you can use our web IRC client. You can find it at [https://webirc.ulyssis.org/ webirc.ulyssis.org]. Remember to leave your web IRC browser tap open while you wait for a response. ==IRC network details== Below are specific instructions for some clients, but if you are already familiar with IRC, here are the details you need to connect to our server. We highly recommend using SSL. Server: irc.ulyssis.org Port: 6668 (SSL) Channel: #ulyssis If <code>irc.ulyssis.org</code> is down, you can also try the other server in the same network, hosted at <code>irc2.ulyssis.org</code>. Both are connected to each other and you can use them interchangeably. It is advised to add it as a fallback in your IRC client. ==IRC clients== To use IRC, you'll need an IRC client. We advise the terminal based [https://irssi.org/ irssi] or [https://weechat.org/ weechat] for Linux and [https://hexchat.github.io/ hexchat] or [https://www.mirc.com/ mIRC] for Windows, but there are a lot of other free options. You can only receive messages over IRC while you're connected. Therefore, we advise you to run irssi or weechat in either a screen or a tmux session. With a ULYSSIS account, you can run screen or tmux on our shellservers, as they keep running 24/7 you can use them to keep track of your conversations. Screen and tmux are similar programs. Screen has been around for longer and is more tested, while tmux is more modern with new features and being easier to use for beginners. ===Using irssi on our shell servers=== ====Connect to the shellserver==== Use the ssh command in your Linux or OS X terminal, or use PuTTY to connect on windows. Extensive information on how to do so can be found on [[Accessing shell servers over SSH]]. ====Start irssi in a screen==== *When on the shellserver, enter <code>screen -U</code> to start a screen session, or <code>tmux</code> to start a tmux session. *Enter <code>irssi</code> to start irssi *Connect to the IRC server: <code>/server -ssl irc.ulyssis.org 6668</code> *Connect to the public channel: <code>/join #ulyssis</code> ====Screen usage==== *To exit the screen: press Ctrl-A and press D ('detach') to return to the shellserver. *To reconnect: enter <code>screen -r</code> or <code>screen -DR</code> (the latter will create a new screen if it wasn't already made). ====Tmux usage==== *To exit the tmux session: press Ctrl-B and press D ('detach') to return to the shellserver. *To reconnect: enter <code>tmux attach</code> ====Help, I can't reconnect to my session!==== *Check if you are on the right shell server and didn't make a typing error. *If everything is correct, your screen may have been stopped by a crash or a reboot of our shellserver. You can check the [http://status.ulyssis.org status] section of our website for more information about possible downtimes. *Make sure you use the right program (<code>screen</code> if you started a screen session and <code>tmux</code> if you started a tmux session) ==Using ZNC== Alternatively, if you don't like using terminal-based clients, or just want to run your client locally, you can connect with our [https://znc.ulyssis.org/ ZNC server]. However, to use it, you'll need a ULYSSIS account. ZNC connects to our IRC server in your place (fill in the details at the beginning of this article). You can then connect to ZNC with a client of your choice, and it will send you the history you've missed while you were offline. Log in to our ZNC server. In your settings, create a new network. Fill in the basic details (server name, nickname, set <code>BindHost</code> to <code>0.0.0.0</code>). In the server field, fill in <code>irc.ulyssis.org +6668</code>. Add <code>#ulyssis</code> as a channel. You may want to increase the buffer count. Then save at the bottom of the page. In your IRC client, connect to the server <code>znc.ulyssis.org</code> on port 6666 (with SSL) and set <code>username/network:password</code> as password to the server. Replace <code>username</code> with your ULYSSIS username, <code>network</code> with the name of the network in your znc settings, and <code>password</code> with your ULYSSIS password. ==Using Bitlbee== With [https://www.bitlbee.org/main.php/news.r.html Bitlbee], you can connect to other services as if they were an IRC server. It is available at <code>bitlbee.ulyssis.org</code> on ports 7000 and 7001 (SSL). For documentation on how to use Bitlbee, we refer to the manual on its website. This service is only reachable from within the ULYSSIS and KU Leuven networks. [[Category:Shell]] [[Category:ULYSSIS Public Services]] ab30f83cc696e5292ee84a64b96d75066d0c9225 1527 1521 2021-08-14T10:31:32Z Vincenttc 21 wikitext text/x-wiki ULYSSIS hosts its own IRC network. IRC stands for Internet Relay Chat, [https://en.wikipedia.org/wiki/Internet_Relay_Chat IRC on wikipedia]. It is a chat protocol that mainly focuses on group chat, but also allows for private chat. For any support questions, you are free to contact us via email on ulyssis@ulyssis.org, but if your questions are of a less sensitive nature and could benefit from a back-and-forth, it could be useful to contact us on IRC. Do keep in mind that you may have to wait until someone notices your question, which may take a while. If you don't have a question and just want to hang out in our chat, feel free to join! Keep in mind that our IRC network has been a social space for several generations, so you will find alumni and students from different walks of life there, not just ULYSSIS members and users. ==Web IRC client== If you won't regularly use our IRC or if you just want to check it out, you can use our web IRC client. You can find it at [https://webirc.ulyssis.org/ webirc.ulyssis.org]. Remember to leave your web IRC browser tab open while you wait for a response. ==IRC network details== Below are specific instructions for some clients, but if you are already familiar with IRC, here are the details you need to connect to our server. We highly recommend using SSL. Server: irc.ulyssis.org Port: 6668 (SSL) Channel: #ulyssis If <code>irc.ulyssis.org</code> is down, you can also try the other server in the same network, hosted at <code>irc2.ulyssis.org</code>. Both are connected to each other and you can use them interchangeably. It is advised to add it as a fallback in your IRC client. ==IRC clients== To use IRC, you'll need an IRC client. We advise the terminal based [https://irssi.org/ irssi] or [https://weechat.org/ weechat] for Linux and [https://hexchat.github.io/ hexchat] or [https://www.mirc.com/ mIRC] for Windows, but there are a lot of other free options. You can only receive messages over IRC while you're connected. Therefore, we advise you to run irssi or weechat in either a screen or a tmux session. With a ULYSSIS account, you can run screen or tmux on our shellservers, as they keep running 24/7 you can use them to keep track of your conversations. Screen and tmux are similar programs. Screen has been around for longer and is more tested, while tmux is more modern with new features and being easier to use for beginners. ===Using irssi on our shell servers=== ====Connect to the shellserver==== Use the ssh command in your Linux or OS X terminal, or use PuTTY to connect on windows. Extensive information on how to do so can be found on [[Accessing shell servers over SSH]]. ====Start irssi in a screen==== *When on the shellserver, enter <code>screen -U</code> to start a screen session, or <code>tmux</code> to start a tmux session. *Enter <code>irssi</code> to start irssi *Connect to the IRC server: <code>/server -ssl irc.ulyssis.org 6668</code> *Connect to the public channel: <code>/join #ulyssis</code> ====Screen usage==== *To exit the screen: press Ctrl-A and press D ('detach') to return to the shellserver. *To reconnect: enter <code>screen -r</code> or <code>screen -DR</code> (the latter will create a new screen if it wasn't already made). ====Tmux usage==== *To exit the tmux session: press Ctrl-B and press D ('detach') to return to the shellserver. *To reconnect: enter <code>tmux attach</code> ====Help, I can't reconnect to my session!==== *Check if you are on the right shell server and didn't make a typing error. *If everything is correct, your screen may have been stopped by a crash or a reboot of our shellserver. You can check the [http://status.ulyssis.org status] section of our website for more information about possible downtimes. *Make sure you use the right program (<code>screen</code> if you started a screen session and <code>tmux</code> if you started a tmux session) ==Using ZNC== Alternatively, if you don't like using terminal-based clients, or just want to run your client locally, you can connect with our [https://znc.ulyssis.org/ ZNC server]. However, to use it, you'll need a ULYSSIS account. ZNC connects to our IRC server in your place (fill in the details at the beginning of this article). You can then connect to ZNC with a client of your choice, and it will send you the history you've missed while you were offline. Log in to our ZNC server. In your settings, create a new network. Fill in the basic details (server name, nickname, set <code>BindHost</code> to <code>0.0.0.0</code>). In the server field, fill in <code>irc.ulyssis.org +6668</code>. Add <code>#ulyssis</code> as a channel. You may want to increase the buffer count. Then save at the bottom of the page. In your IRC client, connect to the server <code>znc.ulyssis.org</code> on port 6666 (with SSL) and set <code>username/network:password</code> as password to the server. Replace <code>username</code> with your ULYSSIS username, <code>network</code> with the name of the network in your znc settings, and <code>password</code> with your ULYSSIS password. ==Using Bitlbee== With [https://www.bitlbee.org/main.php/news.r.html Bitlbee], you can connect to other services as if they were an IRC server. It is available at <code>bitlbee.ulyssis.org</code> on ports 7000 and 7001 (SSL). For documentation on how to use Bitlbee, we refer to the manual on its website. This service is only reachable from within the ULYSSIS and KU Leuven networks. [[Category:Shell]] [[Category:ULYSSIS Public Services]] b7f636988f3d98574e16286633dc59f72bf9b4b1 0 77 1522 1325 2021-08-09T21:49:37Z Bert 8 /* Adding the KU Leuven SMTP server in Thunderbird */ wikitext text/x-wiki You may want to send e-mail from Thunderbird using your @ulyssis.org-address, or another domain name that you use for your account. Thunderbird allows you to do this, but to configure this properly, you should not use your provider's SMTP server. They will add an extra header stating the original e-mail address the e-mail is sent from. Some e-mail clients show this information, which might be unwanted. The KU Leuven also provides an SMTP server which you can use as a student. It accepts e-mail originating from any e-mail adress, and can therefore be used for this purpose. It should be noted that this is an '''authenticated''' server, so any potential abuse can be tracked back to you. You should '''not''' use this for any malicious purpose. == Adding the KU Leuven SMTP server in Thunderbird == If you already have set up your KU Leuven e-mail in Thunderbird, you can skip this step and proceed to [[#Configure an identity for your e-mail account|Configure an identity for your e-mail account]] below. Go to your '''Account Settings''' (Edit > Account Settings or Tools > Account Settings, depending on your operating system). At the bottom of the left sidebar, you will find an entry named '''Outgoing Server (SMTP)'''. Click this to access your SMTP settings. In your SMTP settings, you should see a list of existing SMTP servers. We want to add a new entry, so click the '''Add...''' button. In the screen that pops up, fill in the settings of the KU Leuven SMTP server, using the example screenshot below based on the [https://admin.kuleuven.be/icts/english/services/email/imap-configuratie-en official ICTS documentation]. Replace the displayed user name with your own KULid (m/r/s/u number). You will have to fill in the corresponding password on first use. [[File:Thunderbird-SMTPS.png]] == Configure an identity for your e-mail account == Back in the '''Account Settings''' screen, click on your e-mail address (not on any of its children). In the screen that opens, there will be a button '''Manage Identities...''' at the bottom. Click it. In the new screen, there will be one existing identity already: the default identity corresponding with your normal e-mail address. We want to add a new identity, so click the '''Add...''' button. In the screen that pops up, fill the name and e-mail address you wish to use. At the bottom, make sure you choose the SMTP server of your student account. This is shown in the image below. [[File:Thunderbird-Identity.png]] == Sending your first e-mail == When you compose a new e-mail, you can change the sender in the "From" field to the identity you just configured. If everything was installed correctly, Thunderbird will show you a pop-up to enter your KU Leuven password when you try to send the e-mail. In this pop-up, you can choose to save this password for later use. [[Category:Mail]] fd3d824c065edeec5ab1decb0f5378b3fb8baf2b 1523 1522 2021-08-09T22:05:12Z Bert 8 /* Configure an identity for your e-mail account */ wikitext text/x-wiki You may want to send e-mail from Thunderbird using your @ulyssis.org-address, or another domain name that you use for your account. Thunderbird allows you to do this, but to configure this properly, you should not use your provider's SMTP server. They will add an extra header stating the original e-mail address the e-mail is sent from. Some e-mail clients show this information, which might be unwanted. The KU Leuven also provides an SMTP server which you can use as a student. It accepts e-mail originating from any e-mail adress, and can therefore be used for this purpose. It should be noted that this is an '''authenticated''' server, so any potential abuse can be tracked back to you. You should '''not''' use this for any malicious purpose. == Adding the KU Leuven SMTP server in Thunderbird == If you already have set up your KU Leuven e-mail in Thunderbird, you can skip this step and proceed to [[#Configure an identity for your e-mail account|Configure an identity for your e-mail account]] below. Go to your '''Account Settings''' (Edit > Account Settings or Tools > Account Settings, depending on your operating system). At the bottom of the left sidebar, you will find an entry named '''Outgoing Server (SMTP)'''. Click this to access your SMTP settings. In your SMTP settings, you should see a list of existing SMTP servers. We want to add a new entry, so click the '''Add...''' button. In the screen that pops up, fill in the settings of the KU Leuven SMTP server, using the example screenshot below based on the [https://admin.kuleuven.be/icts/english/services/email/imap-configuratie-en official ICTS documentation]. Replace the displayed user name with your own KULid (m/r/s/u number). You will have to fill in the corresponding password on first use. [[File:Thunderbird-SMTPS.png]] == Configure an identity for your e-mail account == Back in the '''Account Settings''' screen, click on your e-mail address (not on any of its children). In the screen that opens, there will be a button '''Manage Identities...''' at the bottom. Click it. In the new screen, there will be one existing identity already: the default identity corresponding with your normal e-mail address. We want to add a new identity, so click the '''Add...''' button. In the screen that pops up, fill in the name and e-mail address you wish to use. At the bottom, make sure you choose the SMTP server of your KULid. This is shown in the image below. [[File:Thunderbird-Identity.png]] == Sending your first e-mail == When you compose a new e-mail, you can change the sender in the "From" field to the identity you just configured. If everything was installed correctly, Thunderbird will show you a pop-up to enter your KU Leuven password when you try to send the e-mail. In this pop-up, you can choose to save this password for later use. [[Category:Mail]] f7056a002605b9790c5636e12cad08547805a538 1524 1523 2021-08-09T22:12:40Z Bert 8 /* Configure an identity for your e-mail account */ wikitext text/x-wiki You may want to send e-mail from Thunderbird using your @ulyssis.org-address, or another domain name that you use for your account. Thunderbird allows you to do this, but to configure this properly, you should not use your provider's SMTP server. They will add an extra header stating the original e-mail address the e-mail is sent from. Some e-mail clients show this information, which might be unwanted. The KU Leuven also provides an SMTP server which you can use as a student. It accepts e-mail originating from any e-mail adress, and can therefore be used for this purpose. It should be noted that this is an '''authenticated''' server, so any potential abuse can be tracked back to you. You should '''not''' use this for any malicious purpose. == Adding the KU Leuven SMTP server in Thunderbird == If you already have set up your KU Leuven e-mail in Thunderbird, you can skip this step and proceed to [[#Configure an identity for your e-mail account|Configure an identity for your e-mail account]] below. Go to your '''Account Settings''' (Edit > Account Settings or Tools > Account Settings, depending on your operating system). At the bottom of the left sidebar, you will find an entry named '''Outgoing Server (SMTP)'''. Click this to access your SMTP settings. In your SMTP settings, you should see a list of existing SMTP servers. We want to add a new entry, so click the '''Add...''' button. In the screen that pops up, fill in the settings of the KU Leuven SMTP server, using the example screenshot below based on the [https://admin.kuleuven.be/icts/english/services/email/imap-configuratie-en official ICTS documentation]. Replace the displayed user name with your own KULid (m/r/s/u number). You will have to fill in the corresponding password on first use. [[File:Thunderbird-SMTPS.png]] == Configure an identity for your e-mail account == Back in the '''Account Settings''' screen, click on your e-mail address (not on any of its children). In the screen that opens, there will be a button '''Manage Identities...''' at the bottom. Click it. In the new screen, there will be one existing identity already: the default identity corresponding with your normal e-mail address. We want to add a new identity, so click the '''Add...''' button. In the screen that pops up, fill in the name and e-mail address you wish to use. At the bottom, make sure you choose the SMTP server of your KULid. This is shown in the image below. [[File:Thunderbird-Identity.png]] If you're adding an identity for a group alias, you may also want to automatically send a copy of any replies or emails you're sending to the alias itself to make sure all others are aware of it. To do that, enable the BCC checkbox under the '''Copies & Folders''' tab. It should automatically contain the alias. == Sending your first e-mail == When you compose a new e-mail, you can change the sender in the "From" field to the identity you just configured. If everything was installed correctly, Thunderbird will show you a pop-up to enter your KU Leuven password when you try to send the e-mail. In this pop-up, you can choose to save this password for later use. [[Category:Mail]] 413125bd6c2eab1d3759b3fcf8e2a1975798bbf6 0 20 1525 1123 2021-08-12T00:33:29Z Bert 8 wikitext text/x-wiki ==How to install WordPress for your account== First you need to download WordPress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your webroot directory on our servers. Mostly this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install WordPress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there.<br> '''Warning:''' Postgresql databases are not supported by WordPress, only use MySQL databases. Now we are ready to install WordPress, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. The setup will ask you for your database configuration: *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Table Prefix:''' only change this if you have multiple installations of WordPress in your database<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]] In the next step you need to fill in your own preferences. Finally you will be prompted to log into your WordPress website. Now the installation is finished. {{info|We advise all WordPress users to enable automatic updates for their plugins, themes and WordPres itself. You can find detailed instructions on [[Updating WordPress]].}} To help you design your website, there are a few guides from WordPress that can help you: *https://wordpress.org/support/article/first-steps-with-wordpress-b/ *https://wordpress.org/support/article/using-themes/#get-new-themes *https://wordpress.org/support/article/managing-plugins/ ==Setting up multiple instances of WordPress== If you want to have multiple instances of a WordPress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular WordPress installation, i.e. the steps in the section above. You can also use WordPress' [https://wordpress.org/support/article/create-a-network/ multisite] option. If you need more help with this, you can find it [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 09288dca446aac04272fa631a7576d5f0ca4dc20 0 9 1528 1487 2021-08-15T20:37:54Z Thomasd 40 wikitext text/x-wiki You can find all your Apache logs (like <code>access.log</code> and <code>error.log</code>) on all of our shell servers in the directory <code>/var/log/apache_user/''username''</code>. For more information on how to access your files, please visit [[Accessing your files]]. ==Using Cyberduck (graphical interface)== You can access the log files using an SFTP client like Cyberduck. After logging in to one of our shell servers as per [[Accessing your files]], click on "Go" on the top bar and then click "Go to Folder...": [[File:Getting Apache Logs - Cyberduck 1.png]] Then enter <code>/var/log/apache_user/''username''</code> as path name (replace ''username'' with your own username): [[File:Getting Apache Logs - Cyberduck 2.png]] After pressing "Go", you will see a directory for each of your websites, containing their Apache logs. [[File:Getting Apache Logs - Cyberduck 3.png]] After a few days, logs will be compressed into a `bz2` file. ==Using the command line== You can also access your logs by [[Accessing shell servers over SSH|logging in to one of our shell servers over SSH]] and navigating to the correct directory: username@ssh1:~$ cd /var/log/apache_user/username username@ssh1:/var/log/apache_user/username$ ls username.ulyssis.be username@ssh1:/var/log/apache_user/username$ cd username.ulyssis.be username@ssh1:/var/log/apache_user/username/username.ulyssis.be$ ls access-2014-05-07.log error-2014-05-07.log username@ssh1:/var/log/apache_user/username/username.ulyssis.be$ tail error-2014-05-07.log [Wed May 07 01:27:14 2014] [error] [client 10.0.0.1] File does not exist: /home/user/username/www/favicon.ico If you can't find your username inside of <code>/var/log/apache_user</code>, don't worry. If you enter it with <code>cd username</code>, it will automatically appear. [[Category:Webserver]] cdfc853184cf1b7ead5f2dfabab693f825aa2c64 1529 1528 2021-08-15T20:38:13Z Thomasd 40 /* Using Cyberduck (graphical interface) */ wikitext text/x-wiki You can find all your Apache logs (like <code>access.log</code> and <code>error.log</code>) on all of our shell servers in the directory <code>/var/log/apache_user/''username''</code>. For more information on how to access your files, please visit [[Accessing your files]]. ==Using Cyberduck (graphical interface)== You can access the log files using an SFTP client like Cyberduck. After logging in to one of our shell servers as per [[Accessing your files]], click on "Go" on the top bar and then click "Go to Folder...": [[File:Getting Apache Logs - Cyberduck 1.png]] Then enter <code>/var/log/apache_user/''username''</code> as path name (replace ''username'' with your own username): [[File:Getting Apache Logs - Cyberduck 2.png]] After pressing "Go", you will see a directory for each of your websites, containing their Apache logs. [[File:Getting Apache Logs - Cyberduck 3.png]] After a few days, logs will be compressed into a <code>bz2</code> file. ==Using the command line== You can also access your logs by [[Accessing shell servers over SSH|logging in to one of our shell servers over SSH]] and navigating to the correct directory: username@ssh1:~$ cd /var/log/apache_user/username username@ssh1:/var/log/apache_user/username$ ls username.ulyssis.be username@ssh1:/var/log/apache_user/username$ cd username.ulyssis.be username@ssh1:/var/log/apache_user/username/username.ulyssis.be$ ls access-2014-05-07.log error-2014-05-07.log username@ssh1:/var/log/apache_user/username/username.ulyssis.be$ tail error-2014-05-07.log [Wed May 07 01:27:14 2014] [error] [client 10.0.0.1] File does not exist: /home/user/username/www/favicon.ico If you can't find your username inside of <code>/var/log/apache_user</code>, don't worry. If you enter it with <code>cd username</code>, it will automatically appear. [[Category:Webserver]] f8d1b7302969c18aa21c02f47bcc588f12d0b8ca 0 11 1532 1404 2021-08-17T23:48:03Z Bert 8 wikitext text/x-wiki While your ULYSSIS account comes with a subdomain of ulyssis.be and studentenweb.org based on your username, it can be useful and practical to use a personalised domain like a .be, .com or .org for a specific organisation, person or event. To register such a domain, you will have to purchase it from an external registrar, as ULYSSIS doesn't currently offer these kinds of services. You are free to chose any registrar (or reseller) that offers the kind of domain you are looking for. Some registrars are more or less expensive depending on what level of service they offer. You can use lists like the one made available by [https://www.dnsbelgium.be/nl/domeinnaam-registreren/vind-registrar#tld=be DNS Belgium] and [https://www.icann.org/en/accredited-registrars ICANN] if you are unsure where to start. {{notice|Caution!|Please don't configure your domain to use ns4.ulyssis.student.kuleuven.be, not only will it not work, it may result in unpredictable behaviour.}} After you have registered your own domain and you want to use it with your ULYSSIS account, you need to: # Point your domain name to the following ULYSSIS nameservers: #* ns.ulyssis.student.kuleuven.be #* ns2.ulyssis.student.kuleuven.be #* ns3.ulyssis.student.kuleuven.be # Mail us at ulyssis@ulyssis.org, with the following details: #* Your ULYSSIS username #* The domain name you registered #* The directory that you want the domain to point at. This could be your <code>www</code> folder, but any other folder within your home directory is possible. It's also possible to configure a domain to redirect to another domain or website. In that case please mention the specific URL. #* Whether you want to receive e-mail at that domain name via ULYSSIS. Note that we need to request this with ICTS, so this will take a while. Please do keep in mind that, just like any change to an account, this can only be requested by the account holder. You can find more information about DNS at http://en.wikipedia.org/wiki/Domain_Name_System. [[Category:Webserver]] 8393224f5d07b4faf0881fb0d0e54faccbc3a46d 0 29 1534 1280 2021-08-30T19:29:52Z Simon 36 wikitext text/x-wiki To register an account, follow these steps: [[File:UCC Request New Account.png|thumb|right]] * Go to https://ucc.ulyssis.org/accounts and log in using your Central KU Leuven Account. * Select the kind of account you wish to register: ** Most people will want to register a '''regular account''' for '''personal use'''. ** If you are a recognised '''faculty union''' (kring), assembly or '''faculty consultative bodies''' (facultair overlegorgaan) you are entitled to this free account. We verify this using the list of recognised faculty unions (kringen) from LOKO on http://loko.be/verenigingen/ and list of recognised faculty consultative bodies from the Studentenraad KU Leuven on https://www.sturakuleuven.be/onze-werking/facultaire-overlegorganen/ . Recognised organisations are not entitled to a free account (see below). ** If you are a '''recognised organisation''' by LOKO or the KU Leuven itself you are entitled to an organisation account, which has a reduced price. We verify this using the list of associations (vrije verenigingen) recognised by [http://loko.be/verenigingen/ LOKO] and the list of recognised [https://www.kuleuven.be/cultuur/doehetzelf/ensembles music] and [https://www.kuleuven.be/cultuur/doehetzelf/podium.htm performing arts] ensembles by KU Leuven. * After picking your account type you have to choose which options you want, as well as a username and a language. * Accept the ULYSSIS terms of use and confirm your order. * An email will be sent to your KU Leuven email address to confirm your order alongside a request for payment. * As soon as we have received and processed your payment, your account will be activated and you will receive instructions to set a password. [[Category:Account]] f70448c385fd91f82d91ba5e771c618ccd00205e 6 205 1535 2021-08-31T23:10:04Z Thomasd 40 wikitext text/x-wiki First step in moving files/directories between wiki installations in Cyberduck e24a83983c0d74d78ecc12ec0129bd65e896cab0 6 206 1536 2021-08-31T23:11:02Z Thomasd 40 wikitext text/x-wiki Second step in moving files/directories between wiki installations in Cyberduck b34d9539f32d0614071f1ad1c2b7602f4ab237c2 0 57 1539 1471 2021-09-02T11:05:23Z Casper 39 /* Restricting spam */ wikitext text/x-wiki == Restricting spam == By default, Joomla has no option no enable comments, contacts or user registrations. Most of these options are managed through Joomla plugins/extensions. But these extensions will often allow by default that any user (or bot) can make comments, register an account, etc. To prevent these people or bots attacking your website, a few steps can be taken which are listed below. It can be the better option to completely not use comments or any other forms of contact, but of course this is not always possible. ==Detecting spam== As mentioned above, it's better in most cases to simply not allow comments or to restrict them very heavily than having to deal with spam. If you have no other choice, there are some options available to help you out. It's important to keep in mind that both options below rely on external service providers for some aspects of their spam detection. === R Antispam === R Antispam is an extension for Joomla that works via the Bayesian algorithm to prevent spam on your Joomla website. It can protect you from spam on many different forms. On top of that, the extension is free to download and use. To use R Antispam follow these instructions: * Go to https://extensions.joomla.org/extension/r-antispam/ and press the download button on the right side, to start downloading the extension * Go to the admin panel on your Joomla website * On the top of this page select the tab "Extensions" -> "Manage" -> "Install" * Press the green "Browse for files"-button, and select the .zip file you just downloaded in the first step * Now your plugin should be installed, but to make sure that it is working and active go to the tab "Extensions" -> "Manage" -> "Manage" * This will give you a list of all installed plugins. Now search for the R Antispam plugin and make sure that the status says active (a green V is shown) Now the plugin is working and spam can be prevented. ===Google's reCAPTCHA=== CAPTCHA, originally from a complicated acronym, is a term used for different kinds of challenges to prevent automated scripts from trying to comment, register or login on websites. reCAPTCHA is a project owned by Google that is quite successful at designing these challenges. You probably know reCAPTCHA as the "I'm not a robot" checkbox you often have to press. More details are available on <nowiki>https://google.com/recaptcha</nowiki> To use Google's reCAPTCHA follow these instructions: * Go to google's reCAPTCHA administrator page(https://www.google.com/recaptcha/admin) and register your site * Navigate to the admin panel of your Joomla installation and select the tab "Extensions" -> "Plugins" * Search for 'recaptcha' in the search box and enable the "CAPTCHA - reCAPTCHA"-plugin by clicking on the status icon next to the name * Once complete it is '''critical''' that you configure your reCAPTCHA properly ** Go to reCAPTCHA's configuration page by clicking the plugin's name in the same panel where you enabled it ** Now fill in the required keys you got on google's reCAPTCHA's administrator page before ** When finished entering these keys, press the "Save & Close" button to save your settings From now on, when for example registering an account, Joomla will ask to fill in a reCAPTCHA [[Category:Security & anti-spam]] [[Category:CMSs]] 766cc16d4880e5efcb70367c2e50f239a4e9fc10 0 50 1540 734 2021-09-02T11:28:25Z Casper 39 /* How to install Drupal for your account */ wikitext text/x-wiki ==How to install Drupal for your account== First you need to download Drupal from their website, https://www.drupal.org/download. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named 'drupal-x.x.x', where the x is the downloaded version of Drupal. Next, you have to move the '''contents''' of the drupal-x.x.x directory to your webroot directory on our servers. Most often this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Drupal on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. *'''Database name:''' If you haven't created a MySQL or PostgreSQL database/user on UCC, then you'll have to create it here. The default database is: "username_username". *'''Database username:''' The name you used during the creation of your database account. *'''Database password:''' The password you used during the creation of your database account. *'''Database host:''' This is <code>mysql.ulyssis.org</code>. You will need to click on ''Advanced options'' to set this option. After that you can proceed in the wizard where you can fill in some last few details. By then the wizard will do the rest except for asking some basic questions about the site and, congratulations, you have installed Drupal. ==Setting up multiple instances of Drupal== If you want to have multiple instances of a Drupal site there are two options. The multiple instances can either share drupal code or be fully seperate. For fully seperate installs you can simply create a (sub)folder to store another copy of the drupal code in. You can then access it either from your default domain or have us attach another domain to it for you, more info about that on [[Adding domain names]] If you wish for multiple websites to share the same codebase it is easiest to use multiple domains. More information about how to set this up in your drupal is available in the drupal documentation: https://www.drupal.org/documentation/install/multi-site. As soon as you have made your preperations you can contact us about hooking up the domain name, more info about that on [[Adding domain names]] [[Category:CMSs]] d393fae7ef10b4faa7b4555830ea2b0df6033de9 1542 1540 2021-09-02T12:06:58Z Casper 39 /* How to install Drupal for your account */ wikitext text/x-wiki ==How to install Drupal for your account== First you need to download Drupal from their website, https://www.drupal.org/download. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named 'drupal-x.x.x', where the x is the downloaded version of Drupal. Next, you have to move the '''contents''' of the drupal-x.x.x directory to your webroot directory on our servers. Most often this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Drupal on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. You can also use PostgreSQL as an alternative to MySQL, but fot the esase Now we are ready to install Drupal, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. '''Warning:''' It is possible that during the wizard, under the section of "Requirements review", you will get a warning that the Apache version cannot be determined. This has no consequences in the installation so you can go click "continue anyway" at the bottom of this page. [[File:Drupaldbconfig.png|thumb|477x477px]] The setup will ask you for your MySQL database configuration (when using PostgreSQL instead, select the option on top of the page): * '''Database Name/Databasenaam:''' the name of the MySQL database * '''Database Username/Gebruikersnaam:''' your username * '''Database Password/Wachtwoord:''' your MySQL database password * '''Host/Hostnaam:''' <code>mysql.ulyssis.org (you will need to open 'advanced options' to set this)</code> * '''Port number:''' 3306 (default) * '''Table name prefix:''' only change this if you have multiple installations of WordPress in your database So it should look something like this the screenshot to the right. After that you can proceed in the wizard where you can fill in some last few details. By then the wizard will do the rest except for asking some basic questions about the site and, congratulations, you have installed Drupal. ==Setting up multiple instances of Drupal== If you want to have multiple instances of a Drupal site there are two options. The multiple instances can either share drupal code or be fully seperate. For fully seperate installs you can simply create a (sub)folder to store another copy of the drupal code in. You can then access it either from your default domain or have us attach another domain to it for you, more info about that on [[Adding domain names]] If you wish for multiple websites to share the same codebase it is easiest to use multiple domains. More information about how to set this up in your drupal is available in the drupal documentation: https://www.drupal.org/documentation/install/multi-site. As soon as you have made your preperations you can contact us about hooking up the domain name, more info about that on [[Adding domain names]] [[Category:CMSs]] 5f2bb86c0690849da715fb975873e39995e574c0 1544 1542 2021-09-02T12:11:57Z Casper 39 wikitext text/x-wiki ==How to install Drupal for your account== First you need to download Drupal from their website, https://www.drupal.org/download. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named 'drupal-x.x.x', where the x is the downloaded version of Drupal. Next, you have to move the '''contents''' of the drupal-x.x.x directory to your webroot directory on our servers. Most often this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Drupal on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. You can also use PostgreSQL as an alternative to MySQL, but fot the esase Now we are ready to install Drupal, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. [[File:Screenshot 2021-09-02 at 14-01-14 Requirements review Drupal.png|thumb|343x343px]] '''Warning:''' It is possible that during the wizard, under the section of "Requirements review", you will get a warning that the Apache version cannot be determined. This has no consequences in the installation so you can go click "continue anyway" at the bottom of this page. [[File:Drupaldbconfig.png|thumb|477x477px]] The setup will ask you for your MySQL database configuration (when using PostgreSQL instead, select the option on top of the page): * '''Database Name/Databasenaam:''' the name of the MySQL database * '''Database Username/Gebruikersnaam:''' your username * '''Database Password/Wachtwoord:''' your MySQL database password * '''Host/Hostnaam:''' <code>mysql.ulyssis.org (you will need to open 'advanced options' to set this)</code> * '''Port number:''' 3306 (default) * '''Table name prefix:''' only change this if you have multiple installations of WordPress in your database So it should look something like this the screenshot to the right. In the next steps Drupal will install the website and you will need to fill in your own preferences. Finally you will be prompted to with your own Drupal website. Now the installation is finished. ==Setting up multiple instances of Drupal== If you want to have multiple instances of a Drupal site there are two options. The multiple instances can either share drupal code or be fully seperate. For fully seperate installs you can simply create a (sub)folder to store another copy of the drupal code in. You can then access it either from your default domain or have us attach another domain to it for you, more info about that on [[Adding domain names]] If you wish for multiple websites to share the same codebase it is easiest to use multiple domains. More information about how to set this up in your drupal is available in the drupal documentation: https://www.drupal.org/documentation/install/multi-site. As soon as you have made your preperations you can contact us about hooking up the domain name, more info about that on [[Adding domain names]] [[Category:CMSs]] f4af1fbdcb0abd1bc841333449368ab3951e0477 1545 1544 2021-09-02T12:12:22Z Casper 39 /* How to install Drupal for your account */ wikitext text/x-wiki ==How to install Drupal for your account== First you need to download Drupal from their website, https://www.drupal.org/download. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named 'drupal-x.x.x', where the x is the downloaded version of Drupal. Next, you have to move the '''contents''' of the drupal-x.x.x directory to your webroot directory on our servers. Most often this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Drupal on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. You can also use PostgreSQL as an alternative to MySQL, but fot the esase Now we are ready to install Drupal, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. [[File:Screenshot 2021-09-02 at 14-01-14 Requirements review Drupal.png|thumb|343x343px]] '''Warning:''' It is possible that during the wizard, under the section of "Requirements review", you will get a warning that the Apache version cannot be determined. This has no consequences in the installation so you can go click "continue anyway" at the bottom of this page. The setup will ask you for your MySQL database configuration (when using PostgreSQL instead, select the option on top of the page):[[File:Drupaldbconfig.png|thumb|477x477px]] * '''Database Name/Databasenaam:''' the name of the MySQL database * '''Database Username/Gebruikersnaam:''' your username * '''Database Password/Wachtwoord:''' your MySQL database password * '''Host/Hostnaam:''' <code>mysql.ulyssis.org (you will need to open 'advanced options' to set this)</code> * '''Port number:''' 3306 (default) * '''Table name prefix:''' only change this if you have multiple installations of WordPress in your database So it should look something like this the screenshot to the right. In the next steps Drupal will install the website and you will need to fill in your own preferences. Finally you will be prompted to with your own Drupal website. Now the installation is finished. ==Setting up multiple instances of Drupal== If you want to have multiple instances of a Drupal site there are two options. The multiple instances can either share drupal code or be fully seperate. For fully seperate installs you can simply create a (sub)folder to store another copy of the drupal code in. You can then access it either from your default domain or have us attach another domain to it for you, more info about that on [[Adding domain names]] If you wish for multiple websites to share the same codebase it is easiest to use multiple domains. More information about how to set this up in your drupal is available in the drupal documentation: https://www.drupal.org/documentation/install/multi-site. As soon as you have made your preperations you can contact us about hooking up the domain name, more info about that on [[Adding domain names]] [[Category:CMSs]] 8d77106c61b88aa36532c440d92d2f9c0b6e5cfc 6 207 1541 2021-09-02T12:04:45Z Casper 39 wikitext text/x-wiki drupaldbconfig c74d45eb00d3a3b594318c5635be693fc9a7cfad 6 208 1543 2021-09-02T12:07:31Z Casper 39 wikitext text/x-wiki drupalrv e0f95842e5616a759f095ee671dbd2deceaa2caa 0 50 1546 1545 2021-09-02T12:12:55Z Casper 39 /* How to install Drupal for your account */ wikitext text/x-wiki ==How to install Drupal for your account== First you need to download Drupal from their website, https://www.drupal.org/download. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named 'drupal-x.x.x', where the x is the downloaded version of Drupal. Next, you have to move the '''contents''' of the drupal-x.x.x directory to your webroot directory on our servers. Most often this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Drupal on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. You can also use PostgreSQL as an alternative to MySQL, but fot the esase[[File:Screenshot 2021-09-02 at 14-01-14 Requirements review Drupal.png|thumb|343x343px]]Now we are ready to install Drupal, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. '''Warning:''' It is possible that during the wizard, under the section of "Requirements review", you will get a warning that the Apache version cannot be determined. This has no consequences in the installation so you can go click "continue anyway" at the bottom of this page. The setup will ask you for your MySQL database configuration (when using PostgreSQL instead, select the option on top of the page):[[File:Drupaldbconfig.png|thumb|477x477px]] * '''Database Name/Databasenaam:''' the name of the MySQL database * '''Database Username/Gebruikersnaam:''' your username * '''Database Password/Wachtwoord:''' your MySQL database password * '''Host/Hostnaam:''' <code>mysql.ulyssis.org (you will need to open 'advanced options' to set this)</code> * '''Port number:''' 3306 (default) * '''Table name prefix:''' only change this if you have multiple installations of WordPress in your database So it should look something like this the screenshot to the right. In the next steps Drupal will install the website and you will need to fill in your own preferences. Finally you will be prompted to with your own Drupal website. Now the installation is finished. ==Setting up multiple instances of Drupal== If you want to have multiple instances of a Drupal site there are two options. The multiple instances can either share drupal code or be fully seperate. For fully seperate installs you can simply create a (sub)folder to store another copy of the drupal code in. You can then access it either from your default domain or have us attach another domain to it for you, more info about that on [[Adding domain names]] If you wish for multiple websites to share the same codebase it is easiest to use multiple domains. More information about how to set this up in your drupal is available in the drupal documentation: https://www.drupal.org/documentation/install/multi-site. As soon as you have made your preperations you can contact us about hooking up the domain name, more info about that on [[Adding domain names]] [[Category:CMSs]] 3354b313b51103457d3906afdcf42b508fc41a16 1547 1546 2021-09-02T12:13:10Z Casper 39 /* How to install Drupal for your account */ wikitext text/x-wiki ==How to install Drupal for your account== First you need to download Drupal from their website, https://www.drupal.org/download. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named 'drupal-x.x.x', where the x is the downloaded version of Drupal. Next, you have to move the '''contents''' of the drupal-x.x.x directory to your webroot directory on our servers. Most often this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Drupal on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. You can also use PostgreSQL as an alternative to MySQL, but fot the esase Now we are ready to install Drupal, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. '''Warning:''' It is possible that during the wizard, under the section of "Requirements review", you will get a warning that the Apache version cannot be determined. This has no consequences in the installation so you can go click "continue anyway" at the bottom of this page.[[File:Screenshot 2021-09-02 at 14-01-14 Requirements review Drupal.png|thumb|343x343px]]The setup will ask you for your MySQL database configuration (when using PostgreSQL instead, select the option on top of the page):[[File:Drupaldbconfig.png|thumb|477x477px]] * '''Database Name/Databasenaam:''' the name of the MySQL database * '''Database Username/Gebruikersnaam:''' your username * '''Database Password/Wachtwoord:''' your MySQL database password * '''Host/Hostnaam:''' <code>mysql.ulyssis.org (you will need to open 'advanced options' to set this)</code> * '''Port number:''' 3306 (default) * '''Table name prefix:''' only change this if you have multiple installations of WordPress in your database So it should look something like this the screenshot to the right. In the next steps Drupal will install the website and you will need to fill in your own preferences. Finally you will be prompted to with your own Drupal website. Now the installation is finished. ==Setting up multiple instances of Drupal== If you want to have multiple instances of a Drupal site there are two options. The multiple instances can either share drupal code or be fully seperate. For fully seperate installs you can simply create a (sub)folder to store another copy of the drupal code in. You can then access it either from your default domain or have us attach another domain to it for you, more info about that on [[Adding domain names]] If you wish for multiple websites to share the same codebase it is easiest to use multiple domains. More information about how to set this up in your drupal is available in the drupal documentation: https://www.drupal.org/documentation/install/multi-site. As soon as you have made your preperations you can contact us about hooking up the domain name, more info about that on [[Adding domain names]] [[Category:CMSs]] 18501f3c55ac0f4d8f42799f4c12de0ccecd2882 1548 1547 2021-09-02T12:13:21Z Casper 39 wikitext text/x-wiki ==How to install Drupal for your account== First you need to download Drupal from their website, https://www.drupal.org/download. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named 'drupal-x.x.x', where the x is the downloaded version of Drupal. Next, you have to move the '''contents''' of the drupal-x.x.x directory to your webroot directory on our servers. Most often this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Drupal on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. You can also use PostgreSQL as an alternative to MySQL, but fot the esase Now we are ready to install Drupal, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard.[[File:Screenshot 2021-09-02 at 14-01-14 Requirements review Drupal.png|thumb|343x343px]]'''Warning:''' It is possible that during the wizard, under the section of "Requirements review", you will get a warning that the Apache version cannot be determined. This has no consequences in the installation so you can go click "continue anyway" at the bottom of this page. The setup will ask you for your MySQL database configuration (when using PostgreSQL instead, select the option on top of the page):[[File:Drupaldbconfig.png|thumb|477x477px]] * '''Database Name/Databasenaam:''' the name of the MySQL database * '''Database Username/Gebruikersnaam:''' your username * '''Database Password/Wachtwoord:''' your MySQL database password * '''Host/Hostnaam:''' <code>mysql.ulyssis.org (you will need to open 'advanced options' to set this)</code> * '''Port number:''' 3306 (default) * '''Table name prefix:''' only change this if you have multiple installations of WordPress in your database So it should look something like this the screenshot to the right. In the next steps Drupal will install the website and you will need to fill in your own preferences. Finally you will be prompted to with your own Drupal website. Now the installation is finished. ==Setting up multiple instances of Drupal== If you want to have multiple instances of a Drupal site there are two options. The multiple instances can either share drupal code or be fully seperate. For fully seperate installs you can simply create a (sub)folder to store another copy of the drupal code in. You can then access it either from your default domain or have us attach another domain to it for you, more info about that on [[Adding domain names]] If you wish for multiple websites to share the same codebase it is easiest to use multiple domains. More information about how to set this up in your drupal is available in the drupal documentation: https://www.drupal.org/documentation/install/multi-site. As soon as you have made your preperations you can contact us about hooking up the domain name, more info about that on [[Adding domain names]] [[Category:CMSs]] 2857f14bc6b54e5a8983d015ac7b47aed76f84e5 1549 1548 2021-09-02T12:13:50Z Casper 39 wikitext text/x-wiki ==How to install Drupal for your account== First you need to download Drupal from their website, https://www.drupal.org/download. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named 'drupal-x.x.x', where the x is the downloaded version of Drupal. Next, you have to move the '''contents''' of the drupal-x.x.x directory to your webroot directory on our servers. Most often this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Drupal on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. You can also use PostgreSQL as an alternative to MySQL, but fot the esase Now we are ready to install Drupal, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard.[[File:Screenshot 2021-09-02 at 14-01-14 Requirements review Drupal.png|thumb|343x343px]]'''Warning:''' It is possible that during the wizard, under the section of "Requirements review", you will get a warning that the Apache version cannot be determined. This has no consequences in the installation so you can go click "continue anyway" at the bottom of this page. The setup will ask you for your MySQL database configuration (when using PostgreSQL instead, select the option on top of the page): *[[File:Drupaldbconfig.png|thumb|477x477px]]'''Database Name/Databasenaam:''' the name of the MySQL database * '''Database Username/Gebruikersnaam:''' your username * '''Database Password/Wachtwoord:''' your MySQL database password * '''Host/Hostnaam:''' <code>mysql.ulyssis.org (you will need to open 'advanced options' to set this)</code> * '''Port number:''' 3306 (default) * '''Table name prefix:''' only change this if you have multiple installations of WordPress in your database So it should look something like this the screenshot to the right. In the next steps Drupal will install the website and you will need to fill in your own preferences. Finally you will be prompted to with your own Drupal website. Now the installation is finished. ==Setting up multiple instances of Drupal== If you want to have multiple instances of a Drupal site there are two options. The multiple instances can either share drupal code or be fully seperate. For fully seperate installs you can simply create a (sub)folder to store another copy of the drupal code in. You can then access it either from your default domain or have us attach another domain to it for you, more info about that on [[Adding domain names]] If you wish for multiple websites to share the same codebase it is easiest to use multiple domains. More information about how to set this up in your drupal is available in the drupal documentation: https://www.drupal.org/documentation/install/multi-site. As soon as you have made your preperations you can contact us about hooking up the domain name, more info about that on [[Adding domain names]] [[Category:CMSs]] 24f006c18a4bf1d1c4e914d26aa0bce6a4b8e3ed 1550 1549 2021-09-02T12:14:48Z Casper 39 /* How to install Drupal for your account */ wikitext text/x-wiki ==How to install Drupal for your account== First you need to download Drupal from their website, https://www.drupal.org/download. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named 'drupal-x.x.x', where the x is the downloaded version of Drupal. Next, you have to move the '''contents''' of the drupal-x.x.x directory to your webroot directory on our servers. Most often this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Drupal on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. You can also use PostgreSQL as an alternative to MySQL, but fot the esase Now we are ready to install Drupal, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard.[[File:Screenshot 2021-09-02 at 14-01-14 Requirements review Drupal.png|thumb|343x343px]]'''Warning:''' It is possible that during the wizard, under the section of "Requirements review", you will get a warning that the Apache version cannot be determined. This has no consequences in the installation so you can go click "continue anyway" at the bottom of this page. The setup will ask you for your MySQL database configuration (when using PostgreSQL instead, select the option on top of the page): *[[File:Drupaldbconfig.png|thumb|477x477px]]'''Database Name/Databasenaam:''' the name of the MySQL database * '''Database Username/Gebruikersnaam:''' your username * '''Database Password/Wachtwoord:''' your MySQL database password * '''Host/Hostnaam:''' <code>mysql.ulyssis.org (you will need to open 'advanced options' to set this)</code> * '''Port number:''' 3306 (default) * '''Table name prefix:''' only change this if you have multiple installations of WordPress in your database So it should look something like this the screenshot to the right. In the next steps Drupal will install the website and you will need to fill in your own preferences. Finally you will be prompted to with your own Drupal website. Now the installation is finished. <br><br> ==Setting up multiple instances of Drupal== If you want to have multiple instances of a Drupal site there are two options. The multiple instances can either share drupal code or be fully seperate. For fully seperate installs you can simply create a (sub)folder to store another copy of the drupal code in. You can then access it either from your default domain or have us attach another domain to it for you, more info about that on [[Adding domain names]] If you wish for multiple websites to share the same codebase it is easiest to use multiple domains. More information about how to set this up in your drupal is available in the drupal documentation: https://www.drupal.org/documentation/install/multi-site. As soon as you have made your preperations you can contact us about hooking up the domain name, more info about that on [[Adding domain names]] [[Category:CMSs]] 591b66285ed77fc73e5a6ffa836d51762e554551 1551 1550 2021-09-02T12:19:18Z Casper 39 /* Setting up multiple instances of Drupal */ wikitext text/x-wiki ==How to install Drupal for your account== First you need to download Drupal from their website, https://www.drupal.org/download. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named 'drupal-x.x.x', where the x is the downloaded version of Drupal. Next, you have to move the '''contents''' of the drupal-x.x.x directory to your webroot directory on our servers. Most often this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Drupal on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. You can also use PostgreSQL as an alternative to MySQL, but fot the esase Now we are ready to install Drupal, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard.[[File:Screenshot 2021-09-02 at 14-01-14 Requirements review Drupal.png|thumb|343x343px]]'''Warning:''' It is possible that during the wizard, under the section of "Requirements review", you will get a warning that the Apache version cannot be determined. This has no consequences in the installation so you can go click "continue anyway" at the bottom of this page. The setup will ask you for your MySQL database configuration (when using PostgreSQL instead, select the option on top of the page): *[[File:Drupaldbconfig.png|thumb|477x477px]]'''Database Name/Databasenaam:''' the name of the MySQL database * '''Database Username/Gebruikersnaam:''' your username * '''Database Password/Wachtwoord:''' your MySQL database password * '''Host/Hostnaam:''' <code>mysql.ulyssis.org (you will need to open 'advanced options' to set this)</code> * '''Port number:''' 3306 (default) * '''Table name prefix:''' only change this if you have multiple installations of WordPress in your database So it should look something like this the screenshot to the right. In the next steps Drupal will install the website and you will need to fill in your own preferences. Finally you will be prompted to with your own Drupal website. Now the installation is finished. <br><br> ==Setting up multiple instances of Drupal== If you want to have multiple instances of a Drupal site there are two options. The multiple instances can either share Drupal code or be fully separate. For a fully separate installation, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular WordPress installation, i.e. the steps in the section above. If you wish for multiple websites to share the same code base it is easiest to use multiple domains. More information about how to set this up in your Drupal is available in the Drupal documentation: https://www.drupal.org/documentation/install/multi-site. As soon as you have made your preparations you can contact us about setting up the domain name, more info about that on [[Adding domain names]]. [[Category:CMSs]] 835da49947a15fd02c09b4443605e0da3701a145 1552 1551 2021-09-02T12:38:12Z Casper 39 /* How to install Drupal for your account */ wikitext text/x-wiki ==How to install Drupal for your account== First you need to download Drupal from their website, https://www.drupal.org/download. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named 'drupal-x.x.x', where the x is the downloaded version of Drupal. Next, you have to move the '''contents''' of the drupal-x.x.x directory to your webroot directory on our servers. Most often this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Drupal on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. You can also use PostgreSQL as an alternative to MySQL, but fot the esase Now we are ready to install Drupal, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard.[[File:Screenshot 2021-09-02 at 14-01-14 Requirements review Drupal.png|thumb|343x343px]]'''Warning:''' It is possible that during the wizard, under the section of "Requirements review", you will get a warning that the Apache version cannot be determined. This has no consequences in the installation so you can go click "continue anyway" at the bottom of this page. The setup will ask you for your MySQL database configuration (when using PostgreSQL instead, select the option on top of the page): *[[File:Drupaldbconfig.png|thumb|477x477px]]'''Database Name/Databasenaam:''' the name of the MySQL database * '''Database Username/Gebruikersnaam:''' your username * '''Database Password/Wachtwoord:''' your MySQL database password * '''Host/Hostnaam:''' <code>mysql.ulyssis.org (you will need to open 'advanced options' to set this)</code> * '''Port number:''' 3306 (default) * '''Table name prefix:''' only enter this if you have multiple installations of Drupal in your database So it should look something like this the screenshot to the right. In the next steps Drupal will install the website and you will need to fill in your own preferences. Finally you will be prompted to with your own Drupal website. Now the installation is finished. <br><br> ==Setting up multiple instances of Drupal== If you want to have multiple instances of a Drupal site there are two options. The multiple instances can either share Drupal code or be fully separate. For a fully separate installation, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Drupal installation, i.e. the steps in the section above. If you wish for multiple websites to share the same code base it is easiest to use multiple domains. More information about how to set this up in your Drupal is available in the Drupal documentation: https://www.drupal.org/documentation/install/multi-site. As soon as you have made your preparations you can contact us about setting up the domain name, more info about that on [[Adding domain names]]. [[Category:CMSs]] 71f600647c48801f018268ecadfca7b4b999615a 1553 1552 2021-09-03T08:46:38Z Casper 39 /* How to install Drupal for your account */ wikitext text/x-wiki ==How to install Drupal for your account== First you need to download Drupal from their website, https://www.drupal.org/download. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named 'drupal-x.x.x', where the x is the downloaded version of Drupal. Next, you have to move the '''contents''' of the drupal-x.x.x directory to your webroot directory on our servers. Most often this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Drupal on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. You can also use PostgreSQL as an alternative to MySQL, but for the ease of this guide, only MySQL will be shown here. Now we are ready to install Drupal, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard.[[File:Screenshot 2021-09-02 at 14-01-14 Requirements review Drupal.png|thumb|343x343px]]'''Warning:''' It is possible that during the wizard, under the section of "Requirements review", you will get a warning that the Apache version cannot be determined. This has no consequences in the installation so you can go click "continue anyway" at the bottom of this page. The setup will ask you for your MySQL database configuration (when using PostgreSQL instead, select the option on top of the page): *[[File:Drupaldbconfig.png|thumb|477x477px]]'''Database Name/Databasenaam:''' the name of the MySQL database * '''Database Username/Gebruikersnaam:''' your username * '''Database Password/Wachtwoord:''' your MySQL database password * '''Host/Hostnaam:''' <code>mysql.ulyssis.org (you will need to open 'advanced options' to set this)</code> * '''Port number:''' 3306 (default) * '''Table name prefix:''' only enter this if you have multiple installations of Drupal in your database So it should look something like this the screenshot to the right. In the next steps Drupal will install the website and you will need to fill in your own preferences. Finally you will be prompted to with your own Drupal website. Now the installation is finished. <br><br> ==Setting up multiple instances of Drupal== If you want to have multiple instances of a Drupal site there are two options. The multiple instances can either share Drupal code or be fully separate. For a fully separate installation, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Drupal installation, i.e. the steps in the section above. If you wish for multiple websites to share the same code base it is easiest to use multiple domains. More information about how to set this up in your Drupal is available in the Drupal documentation: https://www.drupal.org/documentation/install/multi-site. As soon as you have made your preparations you can contact us about setting up the domain name, more info about that on [[Adding domain names]]. [[Category:CMSs]] d5e4a95b63c21029bc3315451e479c521150c161 1571 1553 2021-09-16T17:12:00Z Casper 39 wikitext text/x-wiki This page will go through a basic setup of Drupal, and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. ==Putting setup-files in place== First you need to download Drupal from their website, https://www.drupal.org/download. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named 'drupal-x.x.x', where the x is the downloaded version of Drupal. Next, you have to move the '''contents''' of the drupal-x.x.x directory to your webroot directory on our servers. Most often this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. == Setting up a database == Besides files, we also need a database to install Drupal on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. You can also use PostgreSQL as an alternative to MySQL, but for the ease of this guide, only MySQL will be shown here. == Installing Drupal == Now we are ready to install Drupal, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard.[[File:Screenshot 2021-09-02 at 14-01-14 Requirements review Drupal.png|thumb|343x343px]]'''Warning:''' It is possible that during the wizard, under the section of "Requirements review", you will get a warning that the Apache version cannot be determined. This has no consequences in the installation so you can go click "continue anyway" at the bottom of this page. The setup will ask you for your MySQL database configuration (when using PostgreSQL instead, select the option on top of the page): *[[File:Drupaldbconfig.png|thumb|477x477px]]'''Database Name/Databasenaam:''' the name of the MySQL database * '''Database Username/Gebruikersnaam:''' your username * '''Database Password/Wachtwoord:''' your MySQL database password * '''Host/Hostnaam:''' <code>mysql.ulyssis.org (you will need to open 'advanced options' to set this)</code> * '''Port number:''' 3306 (default) * '''Table name prefix:''' only enter this if you have multiple installations of Drupal in your database So it should look something like this the screenshot to the right. In the next steps Drupal will install the website and you will need to fill in your own preferences. Finally you will be prompted to with your own Drupal website. Now the installation is finished. <br><br> ==Setting up multiple instances of Drupal== If you want to have multiple instances of a Drupal site there are two options. The multiple instances can either share Drupal code or be fully separate. For a fully separate installation, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Drupal installation, i.e. the steps in the section above. If you wish for multiple websites to share the same code base it is easiest to use multiple domains. More information about how to set this up in your Drupal is available in the Drupal documentation: https://www.drupal.org/documentation/install/multi-site. As soon as you have made your preparations you can contact us about setting up the domain name, more info about that on [[Adding domain names]]. [[Category:CMSs]] 5ac95096c9225c1c5a477ed0958f588a63d2fb6f 1578 1571 2021-10-10T18:37:09Z Casper 39 /* Setting up a database */ wikitext text/x-wiki This page will go through a basic setup of Drupal, and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. ==Putting setup files in place== First you need to download Drupal from their website, https://www.drupal.org/download. After you've received the zip file, you will need to upload it to the server in the www directory. This can be done easily by using Cyberduck and following the steps on [[Accessing your files]]. After uploading, you can extract the archive file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the archive and click "Expand Archive". [[File:Cyberduck expand.png|left|thumb|502x502px]] This will give you a directory named 'drupal-x.x.x', where the x is the downloaded version of Drupal. If you followed all steps correctly, you should have the drupal directory inside your www directory on the server. == Setting up a database == Besides files, we also need a database to install Drupal on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instructions on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. You can also use PostgreSQL ([[Using PostgreSQL]]) as an alternative to MySQL, but for the ease of this guide, only MySQL will be shown here. == Installing Drupal == Now we are ready to install Drupal, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard.[[File:Screenshot 2021-09-02 at 14-01-14 Requirements review Drupal.png|thumb|343x343px]]'''Warning:''' It is possible that during the wizard, under the section of "Requirements review", you will get a warning that the Apache version cannot be determined. This has no consequences in the installation so you can go click "continue anyway" at the bottom of this page. The setup will ask you for your MySQL database configuration (when using PostgreSQL instead, select the option on top of the page): *[[File:Drupaldbconfig.png|thumb|477x477px]]'''Database Name/Databasenaam:''' the name of the MySQL database * '''Database Username/Gebruikersnaam:''' your username * '''Database Password/Wachtwoord:''' your MySQL database password * '''Host/Hostnaam:''' <code>mysql.ulyssis.org (you will need to open 'advanced options' to set this)</code> * '''Port number:''' 3306 (default) * '''Table name prefix:''' only enter this if you have multiple installations of Drupal in your database So it should look something like this the screenshot to the right. In the next steps Drupal will install the website and you will need to fill in your own preferences. Finally you will be prompted to with your own Drupal website. Now the installation is finished. <br><br> ==Setting up multiple instances of Drupal== If you want to have multiple instances of a Drupal site there are two options. The multiple instances can either share Drupal code or be fully separate. For a fully separate installation, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Drupal installation, i.e. the steps in the section above. If you wish for multiple websites to share the same code base it is easiest to use multiple domains. More information about how to set this up in your Drupal is available in the Drupal documentation: https://www.drupal.org/documentation/install/multi-site. As soon as you have made your preparations you can contact us about setting up the domain name, more info about that on [[Adding domain names]]. [[Category:CMSs]] ca0a94235edda0800a85a1259e179acc166438af 1579 1578 2021-10-10T18:51:41Z Casper 39 /* Putting setup files in place */ wikitext text/x-wiki This page will go through a basic setup of Drupal, and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. ==Putting setup files in place== First you need to download Drupal from their website, https://www.drupal.org/download. After you've received the zip file, you will need to upload it to the server in the www directory. This can be done easily by using Cyberduck and following the steps on [[Accessing your files]]. After uploading, you can extract the archive file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the archive and click "Expand Archive". [[File:Cyberduck expand.png|left|thumb|502x502px]] This will give you a directory named 'drupal-x.x.x', where the x is the downloaded version of Drupal. If you followed all steps correctly, you should have the drupal directory inside your www directory on the server. The next step will be to move all the contents from the 'drupal-x.x.x' folder to the www directory. The easiest way to do this using Cyberduck is by going into your drupal folder, and drag-and-dropping all files and directories in your www folder. == Setting up a database == Besides files, we also need a database to install Drupal on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instructions on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. You can also use PostgreSQL ([[Using PostgreSQL]]) as an alternative to MySQL, but for the ease of this guide, only MySQL will be shown here. == Installing Drupal == Now we are ready to install Drupal, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard.[[File:Screenshot 2021-09-02 at 14-01-14 Requirements review Drupal.png|thumb|343x343px]]'''Warning:''' It is possible that during the wizard, under the section of "Requirements review", you will get a warning that the Apache version cannot be determined. This has no consequences in the installation so you can go click "continue anyway" at the bottom of this page. The setup will ask you for your MySQL database configuration (when using PostgreSQL instead, select the option on top of the page): *[[File:Drupaldbconfig.png|thumb|477x477px]]'''Database Name/Databasenaam:''' the name of the MySQL database * '''Database Username/Gebruikersnaam:''' your username * '''Database Password/Wachtwoord:''' your MySQL database password * '''Host/Hostnaam:''' <code>mysql.ulyssis.org (you will need to open 'advanced options' to set this)</code> * '''Port number:''' 3306 (default) * '''Table name prefix:''' only enter this if you have multiple installations of Drupal in your database So it should look something like this the screenshot to the right. In the next steps Drupal will install the website and you will need to fill in your own preferences. Finally you will be prompted to with your own Drupal website. Now the installation is finished. <br><br> ==Setting up multiple instances of Drupal== If you want to have multiple instances of a Drupal site there are two options. The multiple instances can either share Drupal code or be fully separate. For a fully separate installation, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Drupal installation, i.e. the steps in the section above. If you wish for multiple websites to share the same code base it is easiest to use multiple domains. More information about how to set this up in your Drupal is available in the Drupal documentation: https://www.drupal.org/documentation/install/multi-site. As soon as you have made your preparations you can contact us about setting up the domain name, more info about that on [[Adding domain names]]. [[Category:CMSs]] a1652bf8ea28c89b0a1fd53f2fb70b4f6b0902a7 1581 1579 2021-10-16T08:25:45Z Casper 39 /* Installing Drupal */ wikitext text/x-wiki This page will go through a basic setup of Drupal, and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. ==Putting setup files in place== First you need to download Drupal from their website, https://www.drupal.org/download. After you've received the zip file, you will need to upload it to the server in the www directory. This can be done easily by using Cyberduck and following the steps on [[Accessing your files]]. After uploading, you can extract the archive file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the archive and click "Expand Archive". [[File:Cyberduck expand.png|left|thumb|502x502px]] This will give you a directory named 'drupal-x.x.x', where the x is the downloaded version of Drupal. If you followed all steps correctly, you should have the drupal directory inside your www directory on the server. The next step will be to move all the contents from the 'drupal-x.x.x' folder to the www directory. The easiest way to do this using Cyberduck is by going into your drupal folder, and drag-and-dropping all files and directories in your www folder. == Setting up a database == Besides files, we also need a database to install Drupal on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instructions on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. You can also use PostgreSQL ([[Using PostgreSQL]]) as an alternative to MySQL, but for the ease of this guide, only MySQL will be shown here. == Installing Drupal == Now we are ready to install Drupal, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. The setup will ask you for your MySQL database configuration (when using PostgreSQL instead, select the option on top of the page): *[[File:Drupaldbconfig.png|thumb|477x477px]]'''Database Name/Databasenaam:''' the name of the MySQL database * '''Database Username/Gebruikersnaam:''' your username * '''Database Password/Wachtwoord:''' your MySQL database password * '''Host/Hostnaam:''' <code>mysql.ulyssis.org (you will need to open 'advanced options' to set this)</code> * '''Port number:''' 3306 (default) * '''Table name prefix:''' only enter this if you have multiple installations of Drupal in your database So it should look something like this the screenshot to the right. In the next steps Drupal will install the website and you will need to fill in your own preferences. Finally you will be prompted to with your own Drupal website. Now the installation is finished. ==Setting up multiple instances of Drupal== If you want to have multiple instances of a Drupal site there are two options. The multiple instances can either share Drupal code or be fully separate. For a fully separate installation, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Drupal installation, i.e. the steps in the section above. If you wish for multiple websites to share the same code base it is easiest to use multiple domains. More information about how to set this up in your Drupal is available in the Drupal documentation: https://www.drupal.org/documentation/install/multi-site. As soon as you have made your preparations you can contact us about setting up the domain name, more info about that on [[Adding domain names]]. [[Category:CMSs]] 888d14d27ed72256523a6c626b144a58e5671a5d 1582 1581 2021-10-16T08:26:06Z Casper 39 /* Installing Drupal */ wikitext text/x-wiki This page will go through a basic setup of Drupal, and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. ==Putting setup files in place== First you need to download Drupal from their website, https://www.drupal.org/download. After you've received the zip file, you will need to upload it to the server in the www directory. This can be done easily by using Cyberduck and following the steps on [[Accessing your files]]. After uploading, you can extract the archive file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the archive and click "Expand Archive". [[File:Cyberduck expand.png|left|thumb|502x502px]] This will give you a directory named 'drupal-x.x.x', where the x is the downloaded version of Drupal. If you followed all steps correctly, you should have the drupal directory inside your www directory on the server. The next step will be to move all the contents from the 'drupal-x.x.x' folder to the www directory. The easiest way to do this using Cyberduck is by going into your drupal folder, and drag-and-dropping all files and directories in your www folder. == Setting up a database == Besides files, we also need a database to install Drupal on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instructions on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. You can also use PostgreSQL ([[Using PostgreSQL]]) as an alternative to MySQL, but for the ease of this guide, only MySQL will be shown here. == Installing Drupal == Now we are ready to install Drupal, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. The setup will ask you for your MySQL database configuration (when using PostgreSQL instead, select the option on top of the page):[[File:Drupaldbconfig.png|thumb|477x477px]] *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Database Username/Gebruikersnaam:''' your username *'''Database Password/Wachtwoord:''' your MySQL database password *'''Host/Hostnaam:''' <code>mysql.ulyssis.org (you will need to open 'advanced options' to set this)</code> *'''Port number:''' 3306 (default) *'''Table name prefix:''' only enter this if you have multiple installations of Drupal in your database So it should look something like this the screenshot to the right. In the next steps Drupal will install the website and you will need to fill in your own preferences. Finally you will be prompted to with your own Drupal website. Now the installation is finished. ==Setting up multiple instances of Drupal== If you want to have multiple instances of a Drupal site there are two options. The multiple instances can either share Drupal code or be fully separate. For a fully separate installation, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Drupal installation, i.e. the steps in the section above. If you wish for multiple websites to share the same code base it is easiest to use multiple domains. More information about how to set this up in your Drupal is available in the Drupal documentation: https://www.drupal.org/documentation/install/multi-site. As soon as you have made your preparations you can contact us about setting up the domain name, more info about that on [[Adding domain names]]. [[Category:CMSs]] 8fc8aef3b72adecc2ff4d7401e812ae8e1c25b84 1583 1582 2021-10-16T08:26:22Z Casper 39 /* Installing Drupal */ wikitext text/x-wiki This page will go through a basic setup of Drupal, and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. ==Putting setup files in place== First you need to download Drupal from their website, https://www.drupal.org/download. After you've received the zip file, you will need to upload it to the server in the www directory. This can be done easily by using Cyberduck and following the steps on [[Accessing your files]]. After uploading, you can extract the archive file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the archive and click "Expand Archive". [[File:Cyberduck expand.png|left|thumb|502x502px]] This will give you a directory named 'drupal-x.x.x', where the x is the downloaded version of Drupal. If you followed all steps correctly, you should have the drupal directory inside your www directory on the server. The next step will be to move all the contents from the 'drupal-x.x.x' folder to the www directory. The easiest way to do this using Cyberduck is by going into your drupal folder, and drag-and-dropping all files and directories in your www folder. == Setting up a database == Besides files, we also need a database to install Drupal on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instructions on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. You can also use PostgreSQL ([[Using PostgreSQL]]) as an alternative to MySQL, but for the ease of this guide, only MySQL will be shown here. == Installing Drupal == Now we are ready to install Drupal, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard.[[File:Drupaldbconfig.png|thumb|477x477px]] The setup will ask you for your MySQL database configuration (when using PostgreSQL instead, select the option on top of the page): *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Database Username/Gebruikersnaam:''' your username *'''Database Password/Wachtwoord:''' your MySQL database password *'''Host/Hostnaam:''' <code>mysql.ulyssis.org (you will need to open 'advanced options' to set this)</code> *'''Port number:''' 3306 (default) *'''Table name prefix:''' only enter this if you have multiple installations of Drupal in your database So it should look something like this the screenshot to the right. In the next steps Drupal will install the website and you will need to fill in your own preferences. Finally you will be prompted to with your own Drupal website. Now the installation is finished. ==Setting up multiple instances of Drupal== If you want to have multiple instances of a Drupal site there are two options. The multiple instances can either share Drupal code or be fully separate. For a fully separate installation, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular Drupal installation, i.e. the steps in the section above. If you wish for multiple websites to share the same code base it is easiest to use multiple domains. More information about how to set this up in your Drupal is available in the Drupal documentation: https://www.drupal.org/documentation/install/multi-site. As soon as you have made your preparations you can contact us about setting up the domain name, more info about that on [[Adding domain names]]. [[Category:CMSs]] 11e4f224cafadce27ebadfe56cb7c1b0fafc91cc 6 209 1554 2021-09-04T08:33:43Z Casper 39 wikitext text/x-wiki joomla installer d3b20419a3deb78ea80e1bb40170f276cbe4c2e8 6 210 1555 2021-09-04T08:35:43Z Casper 39 wikitext text/x-wiki joomla db e93d9a58c4762a0292c1a26b5a8390bcc7044f8a 0 49 1556 1156 2021-09-04T08:38:17Z Casper 39 /* How to install Joomla for your account */ wikitext text/x-wiki ==How to install Joomla for your account== First you need to download Joomla from their website, https://downloads.joomla.org/. After you've received a zip file, you have to extract it using your file manager (Windows: use right-click and select "extract all"; OSX: double-click the zip, it automatically extracts; Linux: right-click the file, and select "extract here"). This will give you some files and directories so preferably, you want to extract this zip in a new empty directory. Next, you have to move the '''extracted contents''' of the zip to your webroot directory on our servers. In most cases this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Joomla on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there.<br> {{notice| Warning| Postgresql databases can be used for Joomla as well, but they often bring many different issues, so we recommend to use MySQL instead.}} Now we are ready to install Joomla, so we need to go to the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. On the first tab you have to create a name and optionally a description for your Joomla website. Besides that, you also have to fill in the information of the "Super User Account", this is the administrator account of your website. Finally, there is also a switch if you'd want your site to be offline after the installation (this can be changed later), but it's better to leave the switch on "NO" by default. When you are done with the configuration, you click on next.<br> The following image is an example screenshot of the configuration, so you will need to replace this with your own settings: [[File:Joomla Installer.png|center|thumb|674x674px]] Moving to the second tab, this is where we will select what database the website will use. You will need to follow our configuration here: *'''Database Type:''' select MySQL in the drop-down menu *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Table Prefix:''' only change this if you have multiple installations of Joomla in your database<br> Any other settings you leave on default.<br> So it will look something like this: [[File:Joomla db.png|center|thumb|663x663px]] Now we are done configuring the database and we can click next. {{notice| Warning | It is possible that you get the error: <code>To confirm that you are the owner of this website please delete the file named "_JoomlaXXXXXXXXXXXXXXX.txt" we have created in the "installation" folder of your Joomla site.</code> This means you need to go back to one of our shell servers and delete that file inside the directory <code>installation</code> in the <code>www</code> folder. (For information about going to our webservers, you can use this guide: [[Accessing your files]].) After doing this you can just click next again and it will continue to the last tab.}} The last tab will give you an overview of the installation. We can leave anything here by default and scroll down to the button 'install' and click it. Congratulations, you have installed your own Joomla website. There are just a few small things that need to be done. For example, you can install extra languages using the button on the page after the installation if you want.<br> If you are done setting up the configurations, you can go to your website at <code>username.ulyssis.be</code> where you will be welcomed by a standard Joomla webpage. To start building your own website, it can be very interesting to check https://docs.joomla.org/Special:MyLanguage/Tutorials:Beginners for some beginner tutorials. If you have any problems regarding your installation, feel free to contact us at ulyssis@ulyssis.org ==Setting up multiple instances of Joomla== If you want to have multiple instances of a Joomla site then you the create a new folder in your homedir from your shell account. You need a new virtual host, you can send us an [mailto:ulyssis@ulyssis.org email] and we will create one for you. After your new virtual host is ready, you need to do all the same steps as for a regular Joomla installation. Another option is to use the Joomla [https://docs.joomla.org/Multiple_Domains_and_Web_Sites_in_a_single_Joomla!_installation multisite] option. [[Category:CMSs]] 196c2323b320463d19b01888ae4753123fcd19b9 1557 1556 2021-09-04T08:42:17Z Casper 39 wikitext text/x-wiki ==How to install Joomla for your account== First you need to download Joomla from their website, https://downloads.joomla.org/. After you've received a zip file, you have to extract it using your file manager (Windows: use right-click and select "extract all"; OSX: double-click the zip, it automatically extracts; Linux: right-click the file, and select "extract here"). This will give you some files and directories so preferably, you want to extract this zip in a new empty directory. Next, you have to move the '''extracted contents''' of the zip to your webroot directory on our servers. In most cases this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. Besides files, we also need a database to install Joomla on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there.<br> {{notice| Warning| Postgresql databases can be used for Joomla as well, but they often bring many different issues, so we recommend to use MySQL instead.}} Now we are ready to install Joomla, so we need to go to the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. On the first tab you have to create a name and optionally a description for your Joomla website. Besides that, you also have to fill in the information of the "Super User Account", this is the administrator account of your website. Finally, there is also a switch if you'd want your site to be offline after the installation (this can be changed later), but it's better to leave the switch on "NO" by default. When you are done with the configuration, you click on next.<br> The following image is an example screenshot of the configuration, so you will need to replace this with your own settings: [[File:Joomla Installer.png|center|thumb|674x674px]] Moving to the second tab, this is where we will select what database the website will use. You will need to follow our configuration here: *'''Database Type:''' select MySQL in the drop-down menu *'''Host Name/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Table Prefix:''' only change this if you have multiple installations of Joomla in your database *'''Connection Encryption:''' leave this on default Any other settings you leave on default.<br> So it will look something like this: [[File:Joomla db.png|center|thumb|663x663px]] Now we are done configuring the database and we can click next. {{notice| Warning | It is possible that you get the error: <code>To confirm that you are the owner of this website please delete the file named "_JoomlaXXXXXXXXXXXXXXX.txt" we have created in the "installation" folder of your Joomla site.</code> This means you need to go back to one of our shell servers and delete that file inside the directory <code>installation</code> of the <code>www</code> folder. (For information about going to our webservers, you can use this guide: [[Accessing your files]].) After doing this you can just click next again and it will continue to the last tab.}} The last tab will give you an overview of the installation. We can leave anything here by default and scroll down to the button 'install' and click it. Congratulations, you have installed your own Joomla website. There are just a few small things that need to be done. For example, you can install extra languages using the button on the page after the installation if you want.<br> If you are done setting up the configurations, you can go to your website at <code>username.ulyssis.be</code> where you will be welcomed by a standard Joomla webpage. To start building your own website, it can be very interesting to check https://docs.joomla.org/Special:MyLanguage/Tutorials:Beginners for some beginner tutorials. If you have any problems regarding your installation, feel free to contact us at ulyssis@ulyssis.org ==Setting up multiple instances of Joomla== If you want to have multiple instances of a Joomla site then you the create a new folder in your homedir from your shell account. You need a new virtual host, you can send us an [mailto:ulyssis@ulyssis.org email] and we will create one for you. After your new virtual host is ready, you need to do all the same steps as for a regular Joomla installation. Another option is to use the Joomla [https://docs.joomla.org/Multiple_Domains_and_Web_Sites_in_a_single_Joomla!_installation multisite] option. [[Category:CMSs]] 71ab46de4e8ca2d0aeb59e7fb949dac76db22dad 1570 1557 2021-09-16T17:10:17Z Casper 39 wikitext text/x-wiki This page will go through a basic setup of Joomla, and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. ==Putting setup-files in place== First you need to download Joomla from their website, https://downloads.joomla.org/. After you've received a zip file, you have to extract it using your file manager (Windows: use right-click and select "extract all"; OSX: double-click the zip, it automatically extracts; Linux: right-click the file, and select "extract here"). This will give you some files and directories so preferably, you want to extract this zip in a new empty directory. Next, you have to move the '''extracted contents''' of the zip to your webroot directory on our servers. In most cases this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. == Setting up a database == Besides files, we also need a database to install Joomla on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. {{notice| Warning| Postgresql databases can be used for Joomla as well, but they often bring many different issues, so we recommend to use MySQL instead.}} == Installing WordPress == Now we are ready to install Joomla, so we need to go to the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. On the first tab you have to create a name and optionally a description for your Joomla website. Besides that, you also have to fill in the information of the "Super User Account", this is the administrator account of your website. Finally, there is also a switch if you'd want your site to be offline after the installation (this can be changed later), but it's better to leave the switch on "NO" by default. When you are done with the configuration, you click on next.<br> The following image is an example screenshot of the configuration, so you will need to replace this with your own settings: [[File:Joomla Installer.png|center|thumb|674x674px]] Moving to the second tab, this is where we will select what database the website will use. You will need to follow our configuration here: *'''Database Type:''' select MySQL in the drop-down menu *'''Host Name/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Table Prefix:''' only change this if you have multiple installations of Joomla in your database *'''Connection Encryption:''' leave this on default Any other settings you leave on default.<br> So it will look something like this: [[File:Joomla db.png|center|thumb|663x663px]] Now we are done configuring the database and we can click next. {{notice| Warning | It is possible that you get the error: <code>To confirm that you are the owner of this website please delete the file named "_JoomlaXXXXXXXXXXXXXXX.txt" we have created in the "installation" folder of your Joomla site.</code> This means you need to go back to one of our shell servers and delete that file inside the directory <code>installation</code> of the <code>www</code> folder. (For information about going to our webservers, you can use this guide: [[Accessing your files]].) After doing this you can just click next again and it will continue to the last tab.}} The last tab will give you an overview of the installation. We can leave anything here by default and scroll down to the button 'install' and click it. == Finishing up installation == Congratulations, you have installed your own Joomla website. There are just a few small things that need to be done. For example, you can install extra languages using the button on the page after the installation if you want.<br> If you are done setting up the configurations, you can go to your website at <code>username.ulyssis.be</code> where you will be welcomed by a standard Joomla webpage. To start building your own website, it can be very interesting to check https://docs.joomla.org/Special:MyLanguage/Tutorials:Beginners for some beginner tutorials. If you have any problems regarding your installation, feel free to contact us at ulyssis@ulyssis.org ==Setting up multiple instances of Joomla== If you want to have multiple instances of a Joomla site then you the create a new folder in your homedir from your shell account. You need a new virtual host, you can send us an [mailto:ulyssis@ulyssis.org email] and we will create one for you. After your new virtual host is ready, you need to do all the same steps as for a regular Joomla installation. Another option is to use the Joomla [https://docs.joomla.org/Multiple_Domains_and_Web_Sites_in_a_single_Joomla!_installation multisite] option. [[Category:CMSs]] f7b5aef2c1806439bb49a339477188504dd600f8 1572 1570 2021-09-16T17:12:23Z Casper 39 /* Installing WordPress */ wikitext text/x-wiki This page will go through a basic setup of Joomla, and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. ==Putting setup-files in place== First you need to download Joomla from their website, https://downloads.joomla.org/. After you've received a zip file, you have to extract it using your file manager (Windows: use right-click and select "extract all"; OSX: double-click the zip, it automatically extracts; Linux: right-click the file, and select "extract here"). This will give you some files and directories so preferably, you want to extract this zip in a new empty directory. Next, you have to move the '''extracted contents''' of the zip to your webroot directory on our servers. In most cases this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. == Setting up a database == Besides files, we also need a database to install Joomla on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there. {{notice| Warning| Postgresql databases can be used for Joomla as well, but they often bring many different issues, so we recommend to use MySQL instead.}} == Installing Joomla == Now we are ready to install Joomla, so we need to go to the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. On the first tab you have to create a name and optionally a description for your Joomla website. Besides that, you also have to fill in the information of the "Super User Account", this is the administrator account of your website. Finally, there is also a switch if you'd want your site to be offline after the installation (this can be changed later), but it's better to leave the switch on "NO" by default. When you are done with the configuration, you click on next.<br> The following image is an example screenshot of the configuration, so you will need to replace this with your own settings: [[File:Joomla Installer.png|center|thumb|674x674px]] Moving to the second tab, this is where we will select what database the website will use. You will need to follow our configuration here: *'''Database Type:''' select MySQL in the drop-down menu *'''Host Name/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Table Prefix:''' only change this if you have multiple installations of Joomla in your database *'''Connection Encryption:''' leave this on default Any other settings you leave on default.<br> So it will look something like this: [[File:Joomla db.png|center|thumb|663x663px]] Now we are done configuring the database and we can click next. {{notice| Warning | It is possible that you get the error: <code>To confirm that you are the owner of this website please delete the file named "_JoomlaXXXXXXXXXXXXXXX.txt" we have created in the "installation" folder of your Joomla site.</code> This means you need to go back to one of our shell servers and delete that file inside the directory <code>installation</code> of the <code>www</code> folder. (For information about going to our webservers, you can use this guide: [[Accessing your files]].) After doing this you can just click next again and it will continue to the last tab.}} The last tab will give you an overview of the installation. We can leave anything here by default and scroll down to the button 'install' and click it. == Finishing up installation == Congratulations, you have installed your own Joomla website. There are just a few small things that need to be done. For example, you can install extra languages using the button on the page after the installation if you want.<br> If you are done setting up the configurations, you can go to your website at <code>username.ulyssis.be</code> where you will be welcomed by a standard Joomla webpage. To start building your own website, it can be very interesting to check https://docs.joomla.org/Special:MyLanguage/Tutorials:Beginners for some beginner tutorials. If you have any problems regarding your installation, feel free to contact us at ulyssis@ulyssis.org ==Setting up multiple instances of Joomla== If you want to have multiple instances of a Joomla site then you the create a new folder in your homedir from your shell account. You need a new virtual host, you can send us an [mailto:ulyssis@ulyssis.org email] and we will create one for you. After your new virtual host is ready, you need to do all the same steps as for a regular Joomla installation. Another option is to use the Joomla [https://docs.joomla.org/Multiple_Domains_and_Web_Sites_in_a_single_Joomla!_installation multisite] option. [[Category:CMSs]] 7273bd9781c58606b51d632629121657a3f9faff 0 144 1558 1210 2021-09-06T07:35:03Z Bert 8 /* CMSs and other popular software */ wikitext text/x-wiki ULYSSIS considers security an important part of its services. While we of course make sure our software is up-to-date, there is also the security of the applications our users use, the emails they receive, and the account they have on our servers. Even though it's obvious our users are responsible for their own software, passwords and emails, we attempt to safeguard them from harm and adhere to good general standards as well as those agreed upon with KU Leuven ICTS when we started. == Web == As the main service of our hosting accounts, most of our security revolves around securing the many applications our users run. The main responsibility for these applications lies of course with the users who should frequently apply updates and make sure the code they write is secure. === General measures === Under normal circumstances, most web applications will not have interaction with non-http(s) third party applications and APIs (if they have any external interaction in the first place), therefore we only allow general outgoing connections from our webworkers to ports 80 and 443. Based on requests from users and ICTS, we do allow specific outgoing connections to the KU Leuven LDAP and KU Leuven Dingnet MQTT server. If you require access to an unusual port on a specific service, preferably of some kind of academic value or offered by KU Leuven, feel free to contact us with a description of what you would like to do and what services, IP addresses and ports are relevant (and why). As part of our arrangement with KU Leuven ICTS, we pass all our mail through their central email and anti-virus system (CAV). Because of this restriction, it's not possible to connect to external services for email from within our network. You can however easily use local email on our servers, which will be processed as you would expect. To prevent spam and other problems, we do monitor volume and assess spaminess before forwarding emails. More details are available on [[Sending email from websites]] and in the section about email on this page. Most users are aware of Google and Bing, as well as their bots that scan the internet for interesting and useful websites. There are however many other search bots out there, some of which have far from the best reputation. These cause problems with high amounts of traffic due to lack of rate limiting within these bots (which can create problems for resource usage) and almost always collect data for commercial use within products such as SEO services. As these search bots bring no real benefits to our users, bots such as AhrefsBot, Majestic12 and LinkdexBot have been blocked from visiting our webservers in general. Beyond these measures, we also make sure to follow-up any problematic situation and move to suspend the user or website to prevent further harm. Some of these situations include sudden spikes in resource usage, unexpected large email queues, large email delivery failures, high amounts of attempts to connect to blocked ports, or the use of very insecure/outdated software. === CMSs and other popular software === On CMSs and certain pieces of popular software, security is even more important as they are often attacked. Installing updates frequently is therefore paramount. To make sure updates are taken seriously, we have implemented a [[Software Version Checker]] for organisation and kring accounts. Beyond updates, common or short passwords can also be a big problem with CMSs. With the growing popularity of WordPress, we've noticed more frequent dictionary and brute force attacks on WordPress login forms and XML RPC management interfaces. To protect our users, as well as to prevent problematic increases in traffic and resource usage, we automatically block IPs that attempt to access wp-login.php or xmlrpc.php too often and we've installed extra monitoring systems. This of course doesn't mean we don't expect our users to use strong passwords and perhaps even consider disabling XML RPC. We've also noticed an increasing amount of disclosed security issues in popular CMSs and especially their extensions, modules or plugins have attracted a wide array of attacks to attempt to gain control over a website or account. While of course updating frequently and rigorously is the best way to prevent the exploitation of these issues, we also automatically block IPs that attempt to access certain known exploitation patterns, to protect our users, as well as to prevent problematic increases in traffic and resource usage. == Email and spam == All emails that are processed by ULYSSIS pass through our spam setup as well as the central anti-virus (CAV) of the KU Leuven. While the KU Leuven focuses specifically on malware, we apply a more broad approach. Every email is given a spam score based on its headers and content. The score and tests are included in every email. If the score surpasses 5.0, the email is marked as spam but still delivered, if it surpasses 7.5 it is no longer delivered. Emails that include executables (even hidden within an archive or a screensaver) are never delivered and our team is notified. As we receive a lot of exotic spam that is often not in English, regular spam rules often don't suffice to prevent spam from being delivered. At ULYSSIS we therefore use a large set of custom spam rules we've written based on samples. Please refer to the [[spam]] article on this documentation website for details on how to submit spam samples. If you are having issues with emails that are processed by our servers being marked as spam, keep in mind that as our email has to pass through the CAV, we depend on the KU Leuven to maintain a good reputation with other email providers. == Other == Beyond specific measures on our web and email services, we also take certain security measures on other services or on our entire network. === Shellservers === On our shellservers we implement a simple technique to prevent brute forcing or dictionary attacks through SSH by temporarily blocking IP addresses after several failed login attempts. While this usually goes completely unnoticed by users, in circumstances where a user uses the wrong password many times, they may get hit by this security measure and would have to either wait for a few minutes or try to connect to our other shellserver. Similar to all of our webservers, connecting to external email servers is not allowed. You can refer to that part of this article or to [[Sending email from websites]] for more information. === Blocklists === We maintain automatic as well as manual blocklists to prevent spam and attacks from IP addresses or ranges that are known to commit these kinds of actions. We only block those IP addresses that have been implicated in illegal activities, and try to always prevent undue implications for addresses within the same range that have not necessarily been part of any activity. In case of addresses that may change operator, we may also consider a block to be temporary. [[Category:Security & anti-spam‏‎]] [[Category:Webserver]] [[Category:Mail]] [[Category:Shell]] d8f9947cd54dfb8e4767304ca0e5469fb71ed398 1559 1558 2021-09-06T08:30:42Z Bert 8 wikitext text/x-wiki ULYSSIS considers security an important part of its services. While we of course make sure our software is up-to-date, there is also the security of the applications our users use, the emails they receive, and the account they have on our servers. Even though it's obvious our users are responsible for their own software, passwords and emails, we attempt to safeguard them from harm and adhere to good general standards as well as those agreed upon with KU Leuven ICTS when we started. == Web == As the main service of our hosting accounts, most of our security revolves around securing the many applications our users run. The main responsibility for these applications lies of course with the users who should frequently apply updates and make sure the code they write is secure. === General measures === Under normal circumstances, most web applications will not have interaction with non-http(s) third party applications and APIs (if they have any external interaction in the first place), therefore we only allow general outgoing connections from our webworkers to ports 80 and 443. Based on requests from users and ICTS, we do allow specific outgoing connections to the KU Leuven LDAP and KU Leuven Dingnet MQTT server. If you require access to an unusual port on a specific service, preferably of some kind of academic value or offered by KU Leuven, feel free to contact us with a description of what you would like to do and what services, IP addresses and ports are relevant (and why). As part of our arrangement with KU Leuven ICTS, we pass all our mail through their central email and anti-virus system (CAV). Because of this restriction, it's not possible to connect to external services for email from within our network. You can however easily use local email on our servers, which will be processed as you would expect. To prevent spam and other problems, we do monitor volume and assess spaminess before forwarding emails. More details are available on [[Sending email from websites]] and in the section about email on this page. Most users are aware of Google and Bing, as well as their bots that scan the internet for interesting and useful websites. There are however many other search bots out there, some of which have far from the best reputation. These cause problems with high amounts of traffic due to lack of rate limiting within these bots (which can create problems for resource usage) and almost always collect data for commercial use within products such as SEO services. As these search bots bring no real benefits to our users, bots such as AhrefsBot, Majestic12 and LinkdexBot have been blocked from visiting our webservers in general. It's common to have certain hidden files and folders prefixed with a dot (so called dotfiles and dotfolders) to hide them from sight while managing files. However, these files and folders can still be accessed when placed inside a website, and if they contain configuration could result in security breaches. We therefore by default block access to common configuration files (.htaccess, .htpasswd, .passwd, .user.ini, .env and its variants, .dockerfile, .dockercfg, .drone.yml, .netrc, .gitlab-ci.yml), version control system folders and files (.git, .hg, .bzr, .svn, .subversion) and some other files and folders that shouldn't be accessible (.ssh, .idea, .docker, .composer, history files). If you specifically want to make one of these files or folders available, you can overwrite this global configuration using a .htaccess file containing <code>Require all granted</code> to allow access to a folder, for a specific file that same line should be wrapper inside a [[https://httpd.apache.org/docs/2.4/mod/core.html#filesmatch FilesMatch expression]]. Beyond these measures, we also make sure to follow-up any problematic situation and move to suspend the user or website to prevent further harm. Some of these situations include sudden spikes in resource usage, unexpected large email queues, large email delivery failures, high amounts of attempts to connect to blocked ports, or the use of very insecure/outdated software. === CMSs and other popular software === On CMSs and certain pieces of popular software, security is even more important as they are often attacked. Installing updates frequently is therefore paramount. To make sure updates are taken seriously, we have implemented a [[Software Version Checker]] for organisation and kring accounts. Beyond updates, common or short passwords can also be a big problem with CMSs. With the growing popularity of WordPress, we've noticed more frequent dictionary and brute force attacks on WordPress login forms and XML RPC management interfaces. To protect our users, as well as to prevent problematic increases in traffic and resource usage, we automatically block IPs that attempt to access wp-login.php or xmlrpc.php too often and we've installed extra monitoring systems. This of course doesn't mean we don't expect our users to use strong passwords and perhaps even consider disabling XML RPC. We've also noticed an increasing amount of disclosed security issues in popular CMSs and especially their extensions, modules or plugins have attracted a wide array of attacks to attempt to gain control over a website or account. While of course updating frequently and rigorously is the best way to prevent the exploitation of these issues, we also automatically block IPs that attempt to access certain known exploitation patterns, to protect our users, as well as to prevent problematic increases in traffic and resource usage. == Email and spam == All emails that are processed by ULYSSIS pass through our spam setup as well as the central anti-virus (CAV) of the KU Leuven. While the KU Leuven focuses specifically on malware, we apply a more broad approach. Every email is given a spam score based on its headers and content. The score and tests are included in every email. If the score surpasses 5.0, the email is marked as spam but still delivered, if it surpasses 7.5 it is no longer delivered. Emails that include executables (even hidden within an archive or a screensaver) are never delivered and our team is notified. As we receive a lot of exotic spam that is often not in English, regular spam rules often don't suffice to prevent spam from being delivered. At ULYSSIS we therefore use a large set of custom spam rules we've written based on samples. Please refer to the [[spam]] article on this documentation website for details on how to submit spam samples. If you are having issues with emails that are processed by our servers being marked as spam, keep in mind that as our email has to pass through the CAV, we depend on the KU Leuven to maintain a good reputation with other email providers. == Other == Beyond specific measures on our web and email services, we also take certain security measures on other services or on our entire network. === Shellservers === On our shellservers we implement a simple technique to prevent brute forcing or dictionary attacks through SSH by temporarily blocking IP addresses after several failed login attempts. While this usually goes completely unnoticed by users, in circumstances where a user uses the wrong password many times, they may get hit by this security measure and would have to either wait for a few minutes or try to connect to our other shellserver. Similar to all of our webservers, connecting to external email servers is not allowed. You can refer to that part of this article or to [[Sending email from websites]] for more information. === Blocklists === We maintain automatic as well as manual blocklists to prevent spam and attacks from IP addresses or ranges that are known to commit these kinds of actions. We only block those IP addresses that have been implicated in illegal activities, and try to always prevent undue implications for addresses within the same range that have not necessarily been part of any activity. In case of addresses that may change operator, we may also consider a block to be temporary. [[Category:Security & anti-spam‏‎]] [[Category:Webserver]] [[Category:Mail]] [[Category:Shell]] a996c17d384931eda4099f76967585ba2e50501c 1560 1559 2021-09-06T08:31:00Z Bert 8 wikitext text/x-wiki ULYSSIS considers security an important part of its services. While we of course make sure our software is up-to-date, there is also the security of the applications our users use, the emails they receive, and the account they have on our servers. Even though it's obvious our users are responsible for their own software, passwords and emails, we attempt to safeguard them from harm and adhere to good general standards as well as those agreed upon with KU Leuven ICTS when we started. == Web == As the main service of our hosting accounts, most of our security revolves around securing the many applications our users run. The main responsibility for these applications lies of course with the users who should frequently apply updates and make sure the code they write is secure. === General measures === Under normal circumstances, most web applications will not have interaction with non-http(s) third party applications and APIs (if they have any external interaction in the first place), therefore we only allow general outgoing connections from our webworkers to ports 80 and 443. Based on requests from users and ICTS, we do allow specific outgoing connections to the KU Leuven LDAP and KU Leuven Dingnet MQTT server. If you require access to an unusual port on a specific service, preferably of some kind of academic value or offered by KU Leuven, feel free to contact us with a description of what you would like to do and what services, IP addresses and ports are relevant (and why). As part of our arrangement with KU Leuven ICTS, we pass all our mail through their central email and anti-virus system (CAV). Because of this restriction, it's not possible to connect to external services for email from within our network. You can however easily use local email on our servers, which will be processed as you would expect. To prevent spam and other problems, we do monitor volume and assess spaminess before forwarding emails. More details are available on [[Sending email from websites]] and in the section about email on this page. Most users are aware of Google and Bing, as well as their bots that scan the internet for interesting and useful websites. There are however many other search bots out there, some of which have far from the best reputation. These cause problems with high amounts of traffic due to lack of rate limiting within these bots (which can create problems for resource usage) and almost always collect data for commercial use within products such as SEO services. As these search bots bring no real benefits to our users, bots such as AhrefsBot, Majestic12 and LinkdexBot have been blocked from visiting our webservers in general. It's common to have certain hidden files and folders prefixed with a dot (so called dotfiles and dotfolders) to hide them from sight while managing files. However, these files and folders can still be accessed when placed inside a website, and if they contain configuration could result in security breaches. We therefore by default block access to common configuration files (.htaccess, .htpasswd, .passwd, .user.ini, .env and its variants, .dockerfile, .dockercfg, .drone.yml, .netrc, .gitlab-ci.yml), version control system folders and files (.git, .hg, .bzr, .svn, .subversion) and some other files and folders that shouldn't be accessible (.ssh, .idea, .docker, .composer, history files). If you specifically want to make one of these files or folders available, you can overwrite this global configuration using a .htaccess file containing <code>Require all granted</code> to allow access to a folder, for a specific file that same line should be wrapper inside a [https://httpd.apache.org/docs/2.4/mod/core.html#filesmatch FilesMatch expression]. Beyond these measures, we also make sure to follow-up any problematic situation and move to suspend the user or website to prevent further harm. Some of these situations include sudden spikes in resource usage, unexpected large email queues, large email delivery failures, high amounts of attempts to connect to blocked ports, or the use of very insecure/outdated software. === CMSs and other popular software === On CMSs and certain pieces of popular software, security is even more important as they are often attacked. Installing updates frequently is therefore paramount. To make sure updates are taken seriously, we have implemented a [[Software Version Checker]] for organisation and kring accounts. Beyond updates, common or short passwords can also be a big problem with CMSs. With the growing popularity of WordPress, we've noticed more frequent dictionary and brute force attacks on WordPress login forms and XML RPC management interfaces. To protect our users, as well as to prevent problematic increases in traffic and resource usage, we automatically block IPs that attempt to access wp-login.php or xmlrpc.php too often and we've installed extra monitoring systems. This of course doesn't mean we don't expect our users to use strong passwords and perhaps even consider disabling XML RPC. We've also noticed an increasing amount of disclosed security issues in popular CMSs and especially their extensions, modules or plugins have attracted a wide array of attacks to attempt to gain control over a website or account. While of course updating frequently and rigorously is the best way to prevent the exploitation of these issues, we also automatically block IPs that attempt to access certain known exploitation patterns, to protect our users, as well as to prevent problematic increases in traffic and resource usage. == Email and spam == All emails that are processed by ULYSSIS pass through our spam setup as well as the central anti-virus (CAV) of the KU Leuven. While the KU Leuven focuses specifically on malware, we apply a more broad approach. Every email is given a spam score based on its headers and content. The score and tests are included in every email. If the score surpasses 5.0, the email is marked as spam but still delivered, if it surpasses 7.5 it is no longer delivered. Emails that include executables (even hidden within an archive or a screensaver) are never delivered and our team is notified. As we receive a lot of exotic spam that is often not in English, regular spam rules often don't suffice to prevent spam from being delivered. At ULYSSIS we therefore use a large set of custom spam rules we've written based on samples. Please refer to the [[spam]] article on this documentation website for details on how to submit spam samples. If you are having issues with emails that are processed by our servers being marked as spam, keep in mind that as our email has to pass through the CAV, we depend on the KU Leuven to maintain a good reputation with other email providers. == Other == Beyond specific measures on our web and email services, we also take certain security measures on other services or on our entire network. === Shellservers === On our shellservers we implement a simple technique to prevent brute forcing or dictionary attacks through SSH by temporarily blocking IP addresses after several failed login attempts. While this usually goes completely unnoticed by users, in circumstances where a user uses the wrong password many times, they may get hit by this security measure and would have to either wait for a few minutes or try to connect to our other shellserver. Similar to all of our webservers, connecting to external email servers is not allowed. You can refer to that part of this article or to [[Sending email from websites]] for more information. === Blocklists === We maintain automatic as well as manual blocklists to prevent spam and attacks from IP addresses or ranges that are known to commit these kinds of actions. We only block those IP addresses that have been implicated in illegal activities, and try to always prevent undue implications for addresses within the same range that have not necessarily been part of any activity. In case of addresses that may change operator, we may also consider a block to be temporary. [[Category:Security & anti-spam‏‎]] [[Category:Webserver]] [[Category:Mail]] [[Category:Shell]] be43d0f948a5adb10c5320e03b8323fd0f954952 0 176 1561 1538 2021-09-07T21:09:50Z Thomasd 40 /* Finalizing the update */ wikitext text/x-wiki The MediaWiki project provides an official [https://www.mediawiki.org/wiki/Manual:Upgrading wiki page] which explains the procedure to update a wiki. Unfortunately, their instructions are complex, and the page contains a lot of information that is outdated or irrelevant for our users. To make it easier for our users to update, this documentation page aims to be more accessible and easier to understand. However, this page is not an authoritative source on the subject. If the instructions on this page are unclear at any point, you should always refer back to the official instructions. {{info|In this guide, we assume you are familiar with the files on your ULYSSIS account. If you don't know how to access these files, please read [[Accessing your files]] first.}} == Downloading the right version == To start updating MediaWiki, you will need to download the archive file of the version you want to update to. If you did not receive an email from our [[Software Version Checker]], follow the instructions in the next subsection. Otherwise, you can skip to the subsection [[#Downloading the right version using the Software Version Checker | Downloading the right version using the Software Version Checker]]. === Downloading the right version based on your wiki === You can find your current MediaWiki version by going to the <code>Special:Version</code> page on your wiki (simply paste this in the search box) and looking for the "MediaWiki" version under "Installed software". For example, for this wiki, you can find the current version at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed software.png|center|frame]] A table of all recent MediaWiki versions can be found on [https://en.wikipedia.org/wiki/MediaWiki_version_history wikipedia]. Currently supported versions are indicated by a green or yellow color in the first column. To determine which version you want to download, follow these steps: * If the ''branch'' of your version ('''the first two numbers''', like <code>1.xx</code>) is currently supported (green or yellow), you should choose the latest version for this branch. For example, for version 1.35.3, the branch is 1.35. * If this branch is not supported anymore, you should choose the most recent LTS branch. This is indicated by '''(LTS)''' in the second column. '''Make sure this LTS branch is not older than your current branch!''' * If the most recent LTS branch is older than your current branch, you should choose the newest supported branch (green). Now, click on the link of the branch you want to download. This will redirect you to a page with information about this version. The first paragraph on this page contains a link to <code>mediawiki-1.xx.yy.tar.gz</code>. Download this archive and save it somewhere on your computer. === Downloading the right version using the Software Version Checker === The email you received will contain a link to the correct MediaWiki version. This link looks something like: https://releases.wikimedia.org/mediawiki/1.xx/mediawiki-core-1.xx.yy.tar.gz Simply click this link to download the archive and save it somewhere on your computer. == Renaming the old installation == An important step in the update process is to rename the old installation directory. This way, you can simply copy your data from the old installation directory to the new installation directory during the update. Additionally, you can easily restore your old wiki if something goes wrong. The easiest way to do this, is to '''rename''' your wiki location (the directory containing your <code>LocalSettings.php</code> configuration file) to a new directory. If you don't know how to access your files on your ULYSSIS account, refer to [[Accessing your files]] for easy instructions. For example, if <code>LocalSettings.php</code> is stored in <code>www/wiki</code>, you should '''rename''' the wiki folder to <code>wiki_old</code>. == Installing the new files == Now, you will need to upload the <code>mediawiki-1.xx.yy.tar.gz</code> file you downloaded in step 1 next to the old installation directory. For example, if your old installation directory is located in <code>www/wiki_old</code>, upload <code>mediawiki-1.xx.yy.tar.gz</code> to <code>www/</code>. After uploading, you can extract the archive file on the server by using the Cyberduck "Expand Archive" feature. Simply right click the archive and click "Expand Archive". [[File:Cyberduck expand.png|thumb|center]] This will create a directory named <code>mediawiki-1.xx.yy</code>. Rename this directory to the original name of your wiki directory on your ULYSSIS account. For example, if the original name was <code>wiki</code>, rename this directory from <code>mediawiki-1.xx.yy</code> to <code>wiki</code>. This can be done using Cyberduck by right clicking the directory and clicking "Rename". [[File:Cyberduck rename.png|thumb|center]] Finally, you need to move certain other other files and directories from the '''old''' directory to the '''new''' directory. The easiest way to do this using Cyberduck is by going up a directory (so if your wiki is in <code>www/wiki</code>, go to <code>www</code>), and drag-and-dropping the necessary files and directories. For example, moving <code>LocalSettings.php</code> by drag-and-dropping it from <code>wiki_old</code> into <code>wiki</code>: [[File:Cyberduck wiki move 1.png|500px]] [[File:Cyberduck wiki move 2.png|500px]] Although the exact files you need to move are different depending on your wiki, here are some suggestions from the [https://www.mediawiki.org/wiki/Manual:Upgrading#Other_files official instructions]: * <code>LocalSettings.php</code>, which contains your old configuration settings. * The <code>images/</code> directory, containing the uploaded files to the wiki. Because the new wiki directory already contains an (empty) <code>images</code> directory, you need to delete that one first by right-clicking on it and pressing "Delete". Make sure to only delete the <code>images</code> directory in the '''new''' wiki directory. Then you can move the old <code>images</code> directory into the new wiki directory. * Custom extensions from within the <code>extensions/</code> directory. Be careful not to overwrite the default extensions that are bundled with the new MediaWiki version. * Custom skins from within the <code>skins/</code> directory. Be careful not to overwrite the default skins that are bundled with the new MediaWiki version. * Any <code>.htaccess</code> file, if present. '''Make sure you can view hidden files'''; to enable this for Cyberduck, you can look at [[Accessing_your_files#Viewing_hidden_files|Accessing your files]]. == Updating extensions == If you use any extensions that are not bundled with MediaWiki by default, you should update them too. A list of bundled extensions can be found at https://www.mediawiki.org/wiki/Bundled_extensions_and_skins, these extensions will be updated automatically. However, for example, you might have the ULYSSIS extensions [[Securing MediaWiki using Centrale KU Leuven Login|MediaWikiShibboleth]] or [https://github.com/ULYSSIS-KUL/CompressUploads CompressUploads] installed. As with MediaWiki itself, you can find the versions of your installed extensions on the <code>Special:Version</code> page, under "Installed extensions". Extensions will often link to a website where you can download the latest versions. For example, for this wiki, you can find the installed extensions at [[Special:Version]]. At the time of writing, it looks like this: [[File:Installed extensions.png|center|frame]] Because the update instructions are different for each extension, you will have to refer to the update instructions of the extension you want to update. However, most extensions follow the same template as the MediaWiki upgrade itself: * Downloading the latest version: make sure to download the correct update for your new MediaWiki version. * Making a backup of the extension: you should already have a backup in the directory you created in step 2. * Extracting the archive files: similar to the MediaWiki tar.gz archive files, you might have to copy the new extension files to a directory in the new <code>extension/</code> directory. == Finalizing the update == The final step in the update process is to update the database structure of your wiki. Your MediaWiki installation contains a script, called <code>update.php</code>, to perform the necessary database upgrades. This script can be executed using the Cyberduck "Send Command" feature. [[File:Cyberduck send command.png|thumb|center]] Enter the following command in the pop-up box (of course, replace <code><wiki installation location></code> with the location of your new installation): php <wiki installation location>/maintenance/update.php For example, if your wiki is located at <code>www/wiki</code>, the command should be as follows: [[File:Cyberduck update.png|center|750px]] After pressing "Send", the command will be executed on the server. If everything went well, you should see a lot of output, ending with something like: [[File:Cyberduck update output.png|center|750px]] If you get the error <code>Could not open input file</code>, you might have misspelled the installation location. Double check the path to make sure everything is correct. If you encounter any other errors while executing the script, you could try taking a look at the [https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line_2 official instructions]. If this does not resolve your problems, feel free to send us an email. We will try to assist you in completing the update. Congratulations! You successfully updated MediaWiki. Still, there are two more important steps you must perform: * Test your new MediaWiki installation: make sure all basic functionality (viewing, editing pages, file upload) works and all your extensions function properly. * Delete the old installation: you should remove the previously created <code>www/wiki_old</code> directory, using the command line or through a GUI. A simple GUI explanation can be found on [[Accessing_your_files#Creating_and_Deleting_files_and_folders|Accessing your files]]. == If something goes wrong == If something goes wrong during the update so your wiki doesn't work anymore, you can revert the process to go back to your old wiki. If you already moved files or directories such as <code>LocalSettings.php</code> or <code>images</code> from <code>wiki_old</code> to <code>wiki</code>, move them back into <code>wiki_old</code>. Then delete <code>wiki</code> and rename <code>wiki_old</code> back to <code>wiki</code>. Your old wiki is then restored so you can retry the update process. If you still run into any trouble, feel free to email us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. 497f6a14dc3acc9e5655a6dce1f06350e6362067 0 3 1562 1520 2021-09-07T21:21:09Z Thomasd 40 /* CMSs */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Reducing disk usage|Help, my account uses too much disk space]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Making Backups]] * [[Secure file permissions]] * [[Reducing disk usage]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2020]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Sending email from websites]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL/TLS|Getting SSL/TLS (HTTPS security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Claiming a port]] * [[ULYSSIS security measures]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] * [[Spam]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up WordPress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] * [[Updating WordPress]] * [[Updating MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] * [[Using PHPPgAdmin]] * [[Using Adminer]] * [[Making Backups]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[Exporting your KU Leuven class schedule and calendar]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 5d192724b4e1a3e23716797fa3241df947a62c52 0 56 1563 1303 2021-09-09T16:12:42Z Casper 39 wikitext text/x-wiki == Restricting comments == By default, Drupal allows anyone to comment freely on any post you make on your website. While this makes sense when you maintain a blog, it makes less sense when you're using Drupal as the basis for your student organization's website or for something with little to no reader interaction. We therefore advise those with a Drupal installation to consider disabling comments by following these instructions: * If you just installed your website and have not created any pages with comments enabled, you can skip this step. If not, go to your admin panel. From here go to the tab Extend and find the 'comment' module. In the description of this module, open the small triangle by clicking it, and press 'Configure'. In the next interface, go to 'Content' and delete every comment section that has been created on your website. * Disabling the comment module itself on Drupal is very difficult. The alternative solution is to check whenever creating new content on your website, to check the tab 'Comment settings' and make sure that it is on 'close'. ==Detecting spam== As mentioned above, it's better in most cases to simply not allow comments or to restrict them very heavily than having to deal with spam. If you have no other choice, there are some options available to help you out. === Honeypot === Honeypot uses both the honeypot and timestamp methods of deterring spam bots from completing forms on your Drupal site. The module currently supports enabling for all forms on the site, or particular forms like user registration or password reset forms, webforms, contact forms, node forms, and comment forms. To install Honeypot follow these instructions: * First of all make sure that you have the 'Update Manager' module enabled in the 'Extend' tab of your admin panel. If not check the box next to it and press install at the bottom of the page. * Now go to https://www.drupal.org/project/honeypot, to the downloads section. Here right click the link to the download (often .zip or .tar) and press 'copy link'. * Next go back to your website and in your URL bar, go to /admin/modules/install. So it will look something like username.ulyssis.be/admin/modules/install . If you get an error that this page can't be found, check step 1 again. * Now you will get a box that says 'Add from a URL'. Here you enter the link from the module download page, and press continue. This should give a message that the modules has been installed. * Now you will still need to enable this module, in the same way as with the 'Update Manager' module from step 1. * At last you can configure the module to your own liking by opening the triangle in the description of the module en selecting 'Configure'. ===What is recaptcha and how/will it help prevent spam ?=== For answers to those questions you can look at google's page about recaptcha (https://google.com/recaptcha) ===Installation=== This installation guide requires drupal '''6,7 or preferably 8''' (or higher). '''Note this installation requires captcha and recaptcha, these are different plugins and not a type error.''' * Go to drupal's captcha page and download the appropriate version at the bottom of the page (https://www.drupal.org/project/captcha) * Go to drupal's recaptcha page and download the appropriate version at the bottom of the page (https://www.drupal.org/project/recaptcha) ** Extract the archives into '''sites/all/modules/[recaptcha/captcha]'''respectively and relative to your own drupal installation '''(this folder may need to be created manually)''' * Now navigate to your drupal administration page in your browser (/admin/modules) ** Search for captcha and enable it ** Search for recaptcha and enable it * Once complete it is '''critical''' to configure your captcha setting in the web interface (/admin/config/people/captcha) '''and do not forget to enable the captcha-points (/admin/config/people/captcha/captcha-points). [[Category:Security & anti-spam]] [[Category:CMSs]] 3a47d1c341a4fd860babad9556d22a2b95e6750f 1564 1563 2021-09-09T17:26:38Z Casper 39 /* What is recaptcha and how/will it help prevent spam ? */ wikitext text/x-wiki == Restricting comments == By default, Drupal allows anyone to comment freely on any post you make on your website. While this makes sense when you maintain a blog, it makes less sense when you're using Drupal as the basis for your student organization's website or for something with little to no reader interaction. We therefore advise those with a Drupal installation to consider disabling comments by following these instructions: * If you just installed your website and have not created any pages with comments enabled, you can skip this step. If not, go to your admin panel. From here go to the tab Extend and find the 'comment' module. In the description of this module, open the small triangle by clicking it, and press 'Configure'. In the next interface, go to 'Content' and delete every comment section that has been created on your website. * Disabling the comment module itself on Drupal is very difficult. The alternative solution is to check whenever creating new content on your website, to check the tab 'Comment settings' and make sure that it is on 'close'. ==Detecting spam== As mentioned above, it's better in most cases to simply not allow comments or to restrict them very heavily than having to deal with spam. If you have no other choice, there are some options available to help you out. === Honeypot === Honeypot uses both the honeypot and timestamp methods of deterring spam bots from completing forms on your Drupal site. The module currently supports enabling for all forms on the site, or particular forms like user registration or password reset forms, webforms, contact forms, node forms, and comment forms. To install Honeypot follow these instructions: * First of all make sure that you have the 'Update Manager' module enabled in the 'Extend' tab of your admin panel. If not check the box next to it and press install at the bottom of the page. * Now go to https://www.drupal.org/project/honeypot, to the downloads section. Here right click the link to the download (often .zip or .tar) and press 'copy link'. * Next go back to your website and in your URL bar, go to /admin/modules/install. So it will look something like username.ulyssis.be/admin/modules/install . If you get an error that this page can't be found, check step 1 again. * Now you will get a box that says 'Add from a URL'. Here you enter the link from the module download page, and press continue. This should give a message that the modules has been installed. * Now you will still need to enable this module, in the same way as with the 'Update Manager' module from step 1. * At last you can configure the module to your own liking by opening the triangle in the description of the module en selecting 'Configure'. ===Google's reCAPTCHA=== For answers to those questions you can look at google's page about recaptcha (https://google.com/recaptcha) ===Installation=== This installation guide requires drupal '''6,7 or preferably 8''' (or higher). '''Note this installation requires captcha and recaptcha, these are different plugins and not a type error.''' * Go to drupal's captcha page and download the appropriate version at the bottom of the page (https://www.drupal.org/project/captcha) * Go to drupal's recaptcha page and download the appropriate version at the bottom of the page (https://www.drupal.org/project/recaptcha) ** Extract the archives into '''sites/all/modules/[recaptcha/captcha]'''respectively and relative to your own drupal installation '''(this folder may need to be created manually)''' * Now navigate to your drupal administration page in your browser (/admin/modules) ** Search for captcha and enable it ** Search for recaptcha and enable it * Once complete it is '''critical''' to configure your captcha setting in the web interface (/admin/config/people/captcha) '''and do not forget to enable the captcha-points (/admin/config/people/captcha/captcha-points). [[Category:Security & anti-spam]] [[Category:CMSs]] 5d512cc78daa2d61d8a1b6d29f150a9f107ec7cf 1565 1564 2021-09-09T17:44:48Z Casper 39 /* Google's reCAPTCHA */ wikitext text/x-wiki == Restricting comments == By default, Drupal allows anyone to comment freely on any post you make on your website. While this makes sense when you maintain a blog, it makes less sense when you're using Drupal as the basis for your student organization's website or for something with little to no reader interaction. We therefore advise those with a Drupal installation to consider disabling comments by following these instructions: * If you just installed your website and have not created any pages with comments enabled, you can skip this step. If not, go to your admin panel. From here go to the tab Extend and find the 'comment' module. In the description of this module, open the small triangle by clicking it, and press 'Configure'. In the next interface, go to 'Content' and delete every comment section that has been created on your website. * Disabling the comment module itself on Drupal is very difficult. The alternative solution is to check whenever creating new content on your website, to check the tab 'Comment settings' and make sure that it is on 'close'. ==Detecting spam== As mentioned above, it's better in most cases to simply not allow comments or to restrict them very heavily than having to deal with spam. If you have no other choice, there are some options available to help you out. === Honeypot === Honeypot uses both the honeypot and timestamp methods of deterring spam bots from completing forms on your Drupal site. The module currently supports enabling for all forms on the site, or particular forms like user registration or password reset forms, webforms, contact forms, node forms, and comment forms. To install Honeypot follow these instructions: * First of all make sure that you have the 'Update Manager' module enabled in the 'Extend' tab of your admin panel. If not check the box next to it and press install at the bottom of the page. * Now go to https://www.drupal.org/project/honeypot, to the downloads section. Here right click the link to the download (often .zip or .tar) and press 'copy link'. * Next go back to your website and in your URL bar, go to /admin/modules/install. So it will look something like username.ulyssis.be/admin/modules/install . If you get an error that this page can't be found, check step 1 again. * You will see a box that says 'Add from a URL'. Here you enter the link from the module download page, and press continue. This should give a message that the modules has been installed. * Now you will still need to enable this module, in the same way as with the 'Update Manager' module from step 1. * At last you can configure the module to your own liking by opening the triangle in the description of the module en selecting 'Configure'. ===Google's reCAPTCHA=== CAPTCHA, originally from a complicated acronym, is a term used for different kinds of challenges to prevent automated scripts from trying to comment, register or login on websites. reCAPTCHA is a project owned by Google that is quite successful at designing these challenges. You probably know reCAPTCHA as the "I'm not a robot" checkbox you often have to press. More details are available on <nowiki>https://google.com/recaptcha</nowiki> You can follow these instructions to get started: * First of all make sure that you have the 'Update Manager' module enabled in the 'Extend' tab of your admin panel. If not check the box next to it and press install at the bottom of the page. * Now go to https://www.drupal.org/project/captcha, to the downloads section. Here right click the link to the download (often .zip or .tar) and press 'copy link'. * Next go back to your website and in your URL bar, go to /admin/modules/install. So it will look something like "<nowiki>https://username.ulyssis.be/admin/modules/install</nowiki>" . If you get an error that this page can't be found, check step 1 again. * You will see a box that says 'Add from a URL'. Here you enter the link from the module download page, and press continue. This should give a message that the modules has been installed. * Now you will still need to enable this module, in the same way as with the 'Update Manager' module from step 1. * Next you will also need to install the reCAPTCHA module, by performing the same steps above but using the following link instead: https://www.drupal.org/project/captcha. * To use the reCAPTCHA module, it is '''critical''' you first go to the configuration page of this module, where you will need to enter the keys to use reCAPTCHA. You can register these on <nowiki>https://www.google.com/recaptcha/admin</nowiki> ** Go to reCAPTCHA's configuration page by going to the 'Extend' tab, finding the reCAPTCHA module, expanding the small triangle, and clicking configure. ** Now fill in the required keys you got on google's reCAPTCHA's administrator page before ** When finished entering these keys, press the "Save configuration" button to save your settings '''[[Category:Security & anti-spam]] [[Category:CMSs]]''' 621477d3ea322dce51b53c4354dda944246ba45a 1567 1565 2021-09-16T16:33:39Z Casper 39 /* Honeypot */ wikitext text/x-wiki == Restricting comments == By default, Drupal allows anyone to comment freely on any post you make on your website. While this makes sense when you maintain a blog, it makes less sense when you're using Drupal as the basis for your student organization's website or for something with little to no reader interaction. We therefore advise those with a Drupal installation to consider disabling comments by following these instructions: * If you just installed your website and have not created any pages with comments enabled, you can skip this step. If not, go to your admin panel. From here go to the tab Extend and find the 'comment' module. In the description of this module, open the small triangle by clicking it, and press 'Configure'. In the next interface, go to 'Content' and delete every comment section that has been created on your website. * Disabling the comment module itself on Drupal is very difficult. The alternative solution is to check whenever creating new content on your website, to check the tab 'Comment settings' and make sure that it is on 'close'. ==Detecting spam== As mentioned above, it's better in most cases to simply not allow comments or to restrict them very heavily than having to deal with spam. If you have no other choice, there are some options available to help you out. === Honeypot === Honeypot uses both the honeypot and timestamp methods of deterring spam bots from completing forms on your Drupal site. The module currently supports enabling for all forms on the site, or particular forms like user registration or password reset forms, webforms, contact forms, node forms, and comment forms. To install Honeypot follow these instructions: * First of all make sure that you have the 'Update Manager' module enabled in the 'Extend' tab of your admin panel. If not check the box next to it and press install at the bottom of the page. * Now go to https://www.drupal.org/project/honeypot, to the downloads section. Here right click the link to the download (often .zip or .tar) and press 'copy link'. * Next go back to your website and in your URL bar, go to /admin/modules/install. So it will look something like username.ulyssis.be/admin/modules/install . If you get an error that this page can't be found, check step 1 again. * You will see a box that says 'Add from a URL'. Here you enter the link from the module download page, and press continue. This should give a message that the modules has been installed. * Now you will still need to enable this module, in the same way as with the 'Update Manager' module from step 1. * At last you can configure the module to your own liking by opening the triangle in the description of the module en selecting 'Configure'. Of course, beside this extension, there are many more similar extensions which you can use to prevent spam. Though if you install multiple, we would advice to check if the extensions are compatible with each other before installing. ===Google's reCAPTCHA=== CAPTCHA, originally from a complicated acronym, is a term used for different kinds of challenges to prevent automated scripts from trying to comment, register or login on websites. reCAPTCHA is a project owned by Google that is quite successful at designing these challenges. You probably know reCAPTCHA as the "I'm not a robot" checkbox you often have to press. More details are available on <nowiki>https://google.com/recaptcha</nowiki> You can follow these instructions to get started: * First of all make sure that you have the 'Update Manager' module enabled in the 'Extend' tab of your admin panel. If not check the box next to it and press install at the bottom of the page. * Now go to https://www.drupal.org/project/captcha, to the downloads section. Here right click the link to the download (often .zip or .tar) and press 'copy link'. * Next go back to your website and in your URL bar, go to /admin/modules/install. So it will look something like "<nowiki>https://username.ulyssis.be/admin/modules/install</nowiki>" . If you get an error that this page can't be found, check step 1 again. * You will see a box that says 'Add from a URL'. Here you enter the link from the module download page, and press continue. This should give a message that the modules has been installed. * Now you will still need to enable this module, in the same way as with the 'Update Manager' module from step 1. * Next you will also need to install the reCAPTCHA module, by performing the same steps above but using the following link instead: https://www.drupal.org/project/captcha. * To use the reCAPTCHA module, it is '''critical''' you first go to the configuration page of this module, where you will need to enter the keys to use reCAPTCHA. You can register these on <nowiki>https://www.google.com/recaptcha/admin</nowiki> ** Go to reCAPTCHA's configuration page by going to the 'Extend' tab, finding the reCAPTCHA module, expanding the small triangle, and clicking configure. ** Now fill in the required keys you got on google's reCAPTCHA's administrator page before ** When finished entering these keys, press the "Save configuration" button to save your settings '''[[Category:Security & anti-spam]] [[Category:CMSs]]''' 702494a81c46fd2d1487b2ceac044a8071fdc0af 0 152 1566 1207 2021-09-16T07:31:33Z Allys 44 wikitext text/x-wiki It's definitely possible to run multiple websites on a single ULYSSIS account. So you do not need to buy a new account to run a secondary website on. Very often this is used for running a wiki installation together with a WordPress installation, but in fact you can combine almost any CMS (like WordPress, Drupal or Joomla) or software. This is also called 'running multiple instances'. As an example: You have a primary WordPress installation on youroganization.be, but beside that you would also like a blog that runs on Joomla. By following this guide, you can have a main WordPress installation while also having a separate blog on blog.yourorganization.be . The "blog." of this URL is also called a subdomain. If you would like more information regarding subdomains and what they can be used for, you can visit [https://www.domain.com/blog/2019/01/15/subdomain/ this] website. So to run multiple installations on your website, you will need to follow a few steps: First of all, you will need access to one of our shell servers. If you need more information on how to do this, you can visit the following page: [[Accessing your files]]. Continuing, we need to make a new directory in your home folder, preferably next to the <code>www</code> folder where you installed the software that is running on your main website. It is also possible to install the new software to a new directory inside your <code>www</code>, but we do not recommend this for most users because it will be very confusing for later maintenance and updates. We also recommend to name the new directory to something obvious (e.g. a directory named <code>wiki</code> for a wiki installation), this will help future maintainers of your account. Next, you will need to send us an email at ulyssis@ulyssis.org to connect the newly made directory to your subdomain. The information you need to send us is: the '''path''' to the new directory (often this will look something like this: /home/user/<your_username>/<name_of_the_directory>), and the '''subdomain''' you want this website to run on (e.g. blog.yourorganization.be). When you receive a reply back from us that everything is in order, you will need to follow the steps from https://docs.ulyssis.org/Setting_up_WordPress, https://docs.ulyssis.org/Setting_up_Joomla, https://docs.ulyssis.org/Setting_up_Drupal or something else. This depends on what software you are planning to install on the new subdomain. While running the setup for your software, make sure to you install it to the '''right directory''', and adjust the configurations where needed. If you have made edits to the .htaccess file for your website in the past, be cautious as it may interfere with your new installation on the subdomain. When everything is complete, you should now have another website running at e.g. <chosen_subdomain>.yourorganization.be . If you have further questions or problems regarding the guide above, do not hesitate to contact us. ac58dc16cd6612471c83a4eddb5dd923a85a312d 0 20 1568 1525 2021-09-16T17:08:11Z Casper 39 wikitext text/x-wiki This page will go through a basic setup of WordPress, and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. ==Putting setup-files in place== First you need to download WordPress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your webroot directory on our servers. Mostly this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. == Setting up database == Besides files, we also need a database to install WordPress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there.<br> '''Warning:''' Postgresql databases are not supported by WordPress, only use MySQL databases. == Installing WordPress == Now we are ready to install WordPress, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. The setup will ask you for your database configuration: *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Table Prefix:''' only change this if you have multiple installations of WordPress in your database<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]] In the next step you need to fill in your own preferences. == Finishing up installation == Finally you will be prompted to log into your WordPress website. Now the installation is finished. {{info|We advise all WordPress users to enable automatic updates for their plugins, themes and WordPres itself. You can find detailed instructions on [[Updating WordPress]].}} To help you design your website, there are a few guides from WordPress that can help you: *https://wordpress.org/support/article/first-steps-with-wordpress-b/ *https://wordpress.org/support/article/using-themes/#get-new-themes *https://wordpress.org/support/article/managing-plugins/ ==Setting up multiple instances of WordPress== If you want to have multiple instances of a WordPress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular WordPress installation, i.e. the steps in the section above. You can also use WordPress' [https://wordpress.org/support/article/create-a-network/ multisite] option. If you need more help with this, you can find it [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 8929692154d8611c163ef3dfc8d2a52f7c02149c 1569 1568 2021-09-16T17:08:26Z Casper 39 /* Setting up database */ wikitext text/x-wiki This page will go through a basic setup of WordPress, and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. ==Putting setup-files in place== First you need to download WordPress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your webroot directory on our servers. Mostly this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. == Setting up a database == Besides files, we also need a database to install WordPress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there.<br> '''Warning:''' Postgresql databases are not supported by WordPress, only use MySQL databases. == Installing WordPress == Now we are ready to install WordPress, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. The setup will ask you for your database configuration: *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Table Prefix:''' only change this if you have multiple installations of WordPress in your database<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]] In the next step you need to fill in your own preferences. == Finishing up installation == Finally you will be prompted to log into your WordPress website. Now the installation is finished. {{info|We advise all WordPress users to enable automatic updates for their plugins, themes and WordPres itself. You can find detailed instructions on [[Updating WordPress]].}} To help you design your website, there are a few guides from WordPress that can help you: *https://wordpress.org/support/article/first-steps-with-wordpress-b/ *https://wordpress.org/support/article/using-themes/#get-new-themes *https://wordpress.org/support/article/managing-plugins/ ==Setting up multiple instances of WordPress== If you want to have multiple instances of a WordPress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular WordPress installation, i.e. the steps in the section above. You can also use WordPress' [https://wordpress.org/support/article/create-a-network/ multisite] option. If you need more help with this, you can find it [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 125e9ce49299907e705b45a324f3a8a70238d5a5 0 11 1573 1532 2021-09-23T22:06:07Z Bert 8 wikitext text/x-wiki While your ULYSSIS account comes with a subdomain of ulyssis.be and studentenweb.org based on your username, it can be useful and practical to use a personalised domain like a .be, .com or .org for a specific organisation, person or event. To register such a domain, you will have to purchase it from an external registrar, as ULYSSIS doesn't currently offer these kinds of services. You are free to chose any registrar (or reseller) that offers the kind of domain you are looking for. Some registrars are more or less expensive depending on what level of service they offer. You can use lists like the one made available by [https://www.dnsbelgium.be/nl/domeinnaam-registreren/vind-registrar#tld=be DNS Belgium] and [https://www.icann.org/en/accredited-registrars ICANN] if you are unsure where to start. {{notice|Caution!|Please don't configure your domain to use ns4.ulyssis.student.kuleuven.be, not only will it not work, it may result in unpredictable behaviour.}} After you have registered your own domain and you want to use it with your ULYSSIS account, you need to: # Point your domain name to the following ULYSSIS nameservers: #* ns.ulyssis.student.kuleuven.be #* ns2.ulyssis.student.kuleuven.be #* ns3.ulyssis.student.kuleuven.be # Mail us at ulyssis@ulyssis.org, with the following details: #* Your ULYSSIS username #* The domain name you registered #* The directory that you want the domain to point at. If you onle have one website, this will almost always be the <code>www</code> folder, but any other folder within your home directory is possible. It's also possible to configure a domain to redirect to another domain or website. In that case please mention the specific URL. #* Whether you want to receive e-mail at that domain name via ULYSSIS. Note that we need to request this with ICTS, so this will take a while. Please do keep in mind that, just like any change to an account, this can only be requested by the account holder. You can find more information about DNS at http://en.wikipedia.org/wiki/Domain_Name_System. [[Category:Webserver]] f5328202f38fa0b35e9aa7d1d8128d024b14208b 1574 1573 2021-09-23T22:06:30Z Bert 8 wikitext text/x-wiki While your ULYSSIS account comes with a subdomain of ulyssis.be and studentenweb.org based on your username, it can be useful and practical to use a personalised domain like a .be, .com or .org for a specific organisation, person or event. To register such a domain, you will have to purchase it from an external registrar, as ULYSSIS doesn't currently offer these kinds of services. You are free to chose any registrar (or reseller) that offers the kind of domain you are looking for. Some registrars are more or less expensive depending on what level of service they offer. You can use lists like the one made available by [https://www.dnsbelgium.be/nl/domeinnaam-registreren/vind-registrar#tld=be DNS Belgium] and [https://www.icann.org/en/accredited-registrars ICANN] if you are unsure where to start. {{notice|Caution!|Please don't configure your domain to use ns4.ulyssis.student.kuleuven.be, not only will it not work, it may result in unpredictable behaviour.}} After you have registered your own domain and you want to use it with your ULYSSIS account, you need to: # Point your domain name to the following ULYSSIS nameservers: #* ns.ulyssis.student.kuleuven.be #* ns2.ulyssis.student.kuleuven.be #* ns3.ulyssis.student.kuleuven.be # Mail us at ulyssis@ulyssis.org, with the following details: #* Your ULYSSIS username #* The domain name you registered #* The directory that you want the domain to point at. If you only have one website, this will almost always be the <code>www</code> folder, but any other folder within your home directory is possible. It's also possible to configure a domain to redirect to another domain or website. In that case please mention the specific URL. #* Whether you want to receive e-mail at that domain name via ULYSSIS. Note that we need to request this with ICTS, so this will take a while. Please do keep in mind that, just like any change to an account, this can only be requested by the account holder. You can find more information about DNS at http://en.wikipedia.org/wiki/Domain_Name_System. [[Category:Webserver]] 22082111661a0398c6c89f10bdbc4d9b199ef3e0 0 98 1575 1392 2021-10-08T15:47:22Z Yoa 30 /* Translations */ wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for login through the Central KU Leuven Login (Shibboleth). The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Central KU Leuven Login) enabled on your domain. * For instructions on how to get SSL: https://docs.ulyssis.org/Getting_SSL * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest/download/MediaWikiShibboleth.zip github]. Unzip the zip file in the <code>extensions/</code> directory in your MediaWiki installation folder. Make sure there is now a <code>MediaWikiShibboleth</code> folder in <code>extensions/</code>. Finally, locate the <code>LocalSettings.php</code> file in your MediaWiki installation folder and add the following lines to it: wfLoadExtension('MediaWikiShibboleth'); $wgGroupPermissions['*']['createaccount'] = false; $wgRevokePermissions['Shibboleth']['editmyprivateinfo'] = true; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 2 lines of the previous paragraph. This really defeats the purpose of the extension though. ==Configuration== MediaWikiShibboleth has some configuration options which allow for restricting who can log in to your wiki. These restrictions are cumulative. For example, it is possible to allow only students enrolled in a specific degree or programme to log in. These options work especially well with restricting the access of the wiki to logged-in users only. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code>LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code>LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code>LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow students enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code>LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. === Translations === It's possible to translate and modify all public MediaWikiShibboleth messages. The translations can be found in the <code>extensions/MediaWikiShibboleth/i18n/</code>. Dutch (<code>nl.json</code>) and English (<code>en.json</code>) translations are already provided. Even the provided translations can be customized, and we strongly advise you to do so, in order to match them with your wiki situation. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Login without Central KU Leuven login" to expand a login menu. The new log in page looks like this with "Login without Central KU Leuven login" expanded: [[File:Login.png|thumb|none]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png|thumb|none]] [[Category:Security & anti-spam]] [[Category:CMSs]] dc5dff7bcc642e44c95d3592d3935c4c72ce420a 6 211 1576 2021-10-09T13:20:17Z Thomasd 40 wikitext text/x-wiki Log file overview with edit button 62e00fd5c488fce69faf0366c70e50855424c0ec 0 9 1577 1529 2021-10-09T13:40:18Z Thomasd 40 wikitext text/x-wiki You can find all your Apache logs (like <code>access.log</code> and <code>error.log</code>) on all of our shell servers in the directory <code>/var/log/apache_user/''username''</code>. For more information on how to access your files, please visit [[Accessing your files]]. ==Using Cyberduck (graphical interface)== You can access the log files using an SFTP client like Cyberduck. After logging in to one of our shell servers as per [[Accessing your files]], click on "Go" on the top bar and then click "Go to Folder...": [[File:Getting Apache Logs - Cyberduck 1.png]] Then enter <code>/var/log/apache_user/''username''</code> as path name (replace ''username'' with your own username): [[File:Getting Apache Logs - Cyberduck 2.png]] After pressing "Go", you will see a directory for each of your websites, containing their Apache logs. [[File:Getting Apache Logs - Cyberduck 3.png]] You can view a log file by selecting it and pressing the "Edit" button. [[File:Getting Apache Logs - Cyberduck Edit button.png]] After a few days, logs will be compressed into a <code>bz2</code> file. You can download such a file and open it with [https://www.7-zip.org/ 7-Zip]. ==Using the command line== You can also access your logs by [[Accessing shell servers over SSH|logging in to one of our shell servers over SSH]] and navigating to the correct directory: username@ssh1:~$ cd /var/log/apache_user/username username@ssh1:/var/log/apache_user/username$ ls username.ulyssis.be username@ssh1:/var/log/apache_user/username$ cd username.ulyssis.be username@ssh1:/var/log/apache_user/username/username.ulyssis.be$ ls access-2014-05-07.log error-2014-05-07.log username@ssh1:/var/log/apache_user/username/username.ulyssis.be$ tail error-2014-05-07.log [Wed May 07 01:27:14 2014] [error] [client 10.0.0.1] File does not exist: /home/user/username/www/favicon.ico If you can't find your username inside of <code>/var/log/apache_user</code>, don't worry. If you enter it with <code>cd username</code>, it will automatically appear. [[Category:Webserver]] c37e934ed36661bd8c72856bb644d8656e78d0bb 0 43 1580 1403 2021-10-13T08:56:15Z Bert 8 wikitext text/x-wiki Forwarders are, as the name implies, addresses that forward email for one address to a set of other addresses. As your ULYSSIS account only comes with one potential mailbox, you will probably use many forwarders if you have your own domain for email in UCC. You can use forwarders for example to ensure that your organisation is always reachable on specific addresses known amongst students, faculty staff, partners you work with, etc. even though the team behind those addresses changes frequently. Below you can find detailed instructions how to create and edit these forwarders. == Change the forwarders for your @ulyssis.org email address == # Go to [https://ucc.ulyssis.org UCC] and log in with your username and password. # On the right side, click on '''Mail'''. # Under '''Address forward''' you can change the forward address of your ULYSSIS mail by clicking on '''edit'''. # Choose '''forward''' and enter the email address(es) you want to forward your ULYSSIS mail to and save the changes. # If you forward to Gmail, Hotmail. or use Thunderbird, we recommend looking at [[Using a forwarder as an alias]] so you can send mails under the forwarding address instead of just your own. If you want to forward emails received on your @ulyssis.org email address to other addresses as well as have them delivered in your [[mailbox]], you can add ''username''@ulyssis.org to the forwarders list. This will ensure that the email is delivered to your mailbox as if the destination was set to '''Inbox''', while emails are still forwarded to the other addresses. == Change the forwarders for other domains == # Go to [https://ucc.ulyssis.org UCC] and log in with your username and password. # On the right side, click on '''Mail'''. [[File:Forwarder Step1.png|left|alt=|thumb|700px]] 3. Under '''Virtual Domains''', click on the domain you want to change. [[File:Forwarder Step2.png|left|alt=|thumb|700px]] 4. You can change a forwarder by clicking on '''edit''' or on '''Add alias''' and add the forwarders you want. [[File:Forwarder Step3.png|left|alt=|thumb|700px]] 5. Save your changes [[Category:Mail]] a01fd67513acb4b0f17c641f97bfa824e5298bde 6 212 1584 2021-11-30T20:30:55Z Debber 46 wikitext text/x-wiki This is a screenshot of the interface to add a mailbox ca5318ccf366a99b6b714ac9efc2b3470c459c20 6 213 1585 2021-11-30T20:35:09Z Debber 46 wikitext text/x-wiki Highlighted in blue, is the button to add another mailbox 58953a78e25cbbec125bbe7162cb1574b3206b14 6 214 1586 2021-11-30T20:42:38Z Debber 46 wikitext text/x-wiki The email address has been filled in. 7ecc4f3aae50c533e80a56bdbe1c4bdb292e58c2 6 215 1587 2021-11-30T20:47:12Z Debber 46 wikitext text/x-wiki This is how the popup should look with the manual settings 1cb5825962e1a478efa9f598d5b3b5bee34187ee 6 216 1588 2021-11-30T20:56:18Z Debber 46 wikitext text/x-wiki The right way to fill in the advanced settings 7479e667dc86ac972988f8a11d485bbc51fc2fa3 6 217 1589 2021-11-30T21:08:56Z Debber 46 wikitext text/x-wiki The popup after clicking retest 278ff2db283e7dda3022ad82a2c73468ed5c60e3 6 218 1590 2021-11-30T21:17:31Z Debber 46 wikitext text/x-wiki Right after adding the mailbox 4fa6f1093858c4d4e280a1606f31f0536f8579fb 6 219 1591 2021-11-30T21:24:37Z Debber 46 wikitext text/x-wiki Full mailbox 0458177d29c41db26f17cf250a931973edc47c65 0 220 1592 2021-11-30T21:26:43Z Debber 46 Created page with "When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. It is possible to check this mailbox via https://webmail.ulyssis.org. Howev..." wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open-source email client made by Mozilla. It is available for download at https://thunderbird.net. The installation process is fairly easy and thus will not be covered in this article. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following popup should come up: [[File:First Open TB.png|thumb|Dialogue to add a mailbox|left]] If the popup did not come up, or this is not your first mailbox; it is possible to click the Email button (highlighted in blue) under the "Set Up Another Account" section: [[File:New Mailbox.png|thumb|Button (in blue) to add another mailbox|left]] Once the popup is present, it becomes possible to dial in the settings for a mailbox. The first step is to fill in the Email adress field: [[File:Fill in email.png|thumb|The Email address field has been filled in|left]] Notice, the button "Configure manually..." on the bottom left has become clickable. When this button is clicked, the popup should look like this: [[File:Click Configure Manually.png|thumb|Configure manually popup|left]] Now, fill in the information as follows: [[File:Fill advanced.png|thumb|left|Filled in manual settings]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | Protocol:|| IMAP || SMTP |- | Server: || mail.ulyssis.org || smtps.kuleuven.be |- |Port: || 993 || 443 |- |SSL: || SSL/TLS || SSL/TLS |- |Authentication: || Autodetect || Autodetect |- | Username: || ULYSSIS-username || r-number |} The "Re-test" button on the bottom right is used to validate the settings. When pressed, the popup should look like this: [[File:After Clicking Retest GOOD.png|thumb|Popup after clicking Re-test|left]] If this test succeeds, the popup can be closed by pressing the "Done" button on the bottom right. When the popup closes, a mailbox should be added to the left side of the main Thunderbird window. [[File:After Clicking Done.png|thumb|Mailbox on the left of the window|left]] Notice, there is no email present yet. This can be resolved by pressing the "Get Messages" button on the top left of the window: [[File:After Clicking GetMessages.png|thumb|left|Mailbox after pressing Get Messages]] After this first setup, the mailbox should synchronize automatically. [[Category:Mail]] 1f54c13a41f2cbd57208a9de9b2c9f3d8994d611 1593 1592 2021-11-30T21:36:14Z Debber 46 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open-source email client made by Mozilla. It is available for download at https://thunderbird.net. The installation process is fairly easy and thus will not be covered in this article. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|thumb|Dialogue to add a mailbox|left]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the Email button (highlighted in blue) under the "Set Up Another Account" section: [[File:New Mailbox.png|thumb|Button (in blue) to add another mailbox|left]] Once the pop-up is present, it becomes possible to dial in the settings for a mailbox. The first step is to fill in the Email adress field: [[File:Fill in email.png|thumb|The Email address field has been filled in|left]] Notice, the button "Configure manually..." on the bottom left has become clickable. When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|thumb|Configure manually pop-up|left]] Now, fill in the information as follows: [[File:Fill advanced.png|thumb|left|Filled in manual settings]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | Protocol:|| IMAP || SMTP |- | Server: || mail.ulyssis.org || smtps.kuleuven.be |- |Port: || 993 || 443 |- |SSL: || SSL/TLS || SSL/TLS |- |Authentication: || Autodetect || Autodetect |- | Username: || ULYSSIS-username || r-number |} The "Re-test" button on the bottom right is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|thumb|Pop-up after clicking Re-test|left]] If this test succeeds, the pop-up can be closed by pressing the "Done" button on the bottom right. When the pop-up closes, a mailbox should be added to the left side of the main Thunderbird window. [[File:After Clicking Done.png|thumb|Mailbox on the left of the window|left]] Notice, there is no email present yet. This can be resolved by pressing the "Get Messages" button on the top left of the window: [[File:After Clicking GetMessages.png|thumb|left|Mailbox after pressing Get Messages]] After this first setup, the mailbox should synchronize automatically. [[Category:Mail]] 9059153245a9c628ea08a533547756a134d8a14e 1594 1593 2021-11-30T21:40:15Z Debber 46 /* Adding a ULYSSIS mailbox to Thunderbird */ wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open-source email client made by Mozilla. It is available for download at https://thunderbird.net. The installation process is fairly easy and thus will not be covered in this article. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|thumb|Dialogue to add a mailbox|left]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the Email button (highlighted in blue) under the "Set Up Another Account" section: [[File:New Mailbox.png|thumb|Button (in blue) to add another mailbox|left]] Once the pop-up is present, it becomes possible to dial in the settings for a mailbox. The first step is to fill in the Email adress field: [[File:Fill in email.png|thumb|The Email address field has been filled in|left]] Notice, the button "Configure manually..." on the bottom left has become clickable. When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|thumb|Configure manually pop-up|left]] Now, fill in the information as follows: [[File:Fill advanced.png|thumb|left|Filled in manual settings]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | Protocol:|| IMAP || SMTP |- | Server: || mail.ulyssis.org || smtps.kuleuven.be |- |Port: || 993 || 443 |- |SSL: || SSL/TLS || SSL/TLS |- |Authentication: || Autodetect || Autodetect |- | Username: || ULYSSIS-username || r-number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.]]}} The "Re-test" button on the bottom right is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|thumb|Pop-up after clicking Re-test|left]] If this test succeeds, the pop-up can be closed by pressing the "Done" button on the bottom right. When the pop-up closes, a mailbox should be added to the left side of the main Thunderbird window. [[File:After Clicking Done.png|thumb|Mailbox on the left of the window|left]] Notice, there is no email present yet. This can be resolved by pressing the "Get Messages" button on the top left of the window: [[File:After Clicking GetMessages.png|thumb|left|Mailbox after pressing Get Messages]] After this first setup, the mailbox should synchronize automatically. [[Category:Mail]] 090e47748b40644a0a496ec77d14224dcea0fb9d 1595 1594 2021-11-30T21:41:35Z Debber 46 /* Adding a ULYSSIS mailbox to Thunderbird */ wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open-source email client made by Mozilla. It is available for download at https://thunderbird.net. The installation process is fairly easy and thus will not be covered in this article. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|thumb|Dialogue to add a mailbox|left]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the Email button (highlighted in blue) under the "Set Up Another Account" section: [[File:New Mailbox.png|thumb|Button (in blue) to add another mailbox|left]] Once the pop-up is present, it becomes possible to dial in the settings for a mailbox. The first step is to fill in the Email adress field: [[File:Fill in email.png|thumb|The Email address field has been filled in|left]] Notice, the button "Configure manually..." on the bottom left has become clickable. When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|thumb|Configure manually pop-up|left]] Now, fill in the information as follows: [[File:Fill advanced.png|thumb|left|Filled in manual settings]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | Protocol:|| IMAP || SMTP |- | Server: || mail.ulyssis.org || smtps.kuleuven.be |- |Port: || 993 || 443 |- |SSL: || SSL/TLS || SSL/TLS |- |Authentication: || Autodetect || Autodetect |- | Username: || ULYSSIS-username || r-number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.]]}} The "Re-test" button on the bottom right is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|thumb|Pop-up after clicking Re-test|left]] If this test succeeds, the pop-up can be closed by pressing the "Done" button on the bottom right. When the pop-up closes, a mailbox should be added to the left side of the main Thunderbird window. [[File:After Clicking Done.png|thumb|Mailbox on the left of the window|left]] Notice, there is no email present yet. This can be resolved by pressing the "Get Messages" button on the top left of the window: [[File:After Clicking GetMessages.png|thumb|left|Mailbox after pressing Get Messages]] After this first setup, the mailbox should synchronize automatically. [[Category:Mail]] f643f7f24fb018d4c05df17e8678362c50037b1d 0 220 1596 1595 2021-11-30T21:45:07Z Debber 46 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. Do note: this article is written for users who opted for a ULYSSIS mailbox. not for users who opted for a forwarded email address. ==Thunderbird== Thunderbird is a free and open-source email client made by Mozilla. It is available for download at https://thunderbird.net. The installation process is fairly easy and thus will not be covered in this article. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|thumb|Dialogue to add a mailbox|left]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the Email button (highlighted in blue) under the "Set Up Another Account" section: [[File:New Mailbox.png|thumb|Button (in blue) to add another mailbox|left]] Once the pop-up is present, it becomes possible to dial in the settings for a mailbox. The first step is to fill in the Email adress field: [[File:Fill in email.png|thumb|The Email address field has been filled in|left]] Notice, the button "Configure manually..." on the bottom left has become clickable. When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|thumb|Configure manually pop-up|left]] Now, fill in the information as follows: [[File:Fill advanced.png|thumb|left|Filled in manual settings]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | Protocol:|| IMAP || SMTP |- | Server: || mail.ulyssis.org || smtps.kuleuven.be |- |Port: || 993 || 443 |- |SSL: || SSL/TLS || SSL/TLS |- |Authentication: || Autodetect || Autodetect |- | Username: || ULYSSIS-username || r-number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.]]}} The "Re-test" button on the bottom right is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|thumb|Pop-up after clicking Re-test|left]] If this test succeeds, the pop-up can be closed by pressing the "Done" button on the bottom right. When the pop-up closes, a mailbox should be added to the left side of the main Thunderbird window. [[File:After Clicking Done.png|thumb|Mailbox on the left of the window|left]] Notice, there is no email present yet. This can be resolved by pressing the "Get Messages" button on the top left of the window: [[File:After Clicking GetMessages.png|thumb|left|Mailbox after pressing Get Messages]] After this first setup, the mailbox should synchronize automatically. [[Category:Mail]] bec8c75efb13f6af44000cb40fccb56a838eccd0 1597 1596 2021-11-30T21:51:48Z Debber 46 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. Do note: this article is written for users who opted for a ULYSSIS mailbox. not for users who opted for a forwarded email address. ==Thunderbird== Thunderbird is a free and open-source email client made by Mozilla. It is available for download at https://thunderbird.net. The installation process is fairly easy and thus will not be covered in this article. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|thumb|left]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the Email button (highlighted in blue) under the "Set Up Another Account" section: [[File:New Mailbox.png|thumb|left]] Once the pop-up is present, it becomes possible to dial in the settings for a mailbox. The first step is to fill in the Email adress field: [[File:Fill in email.png|thumb|left]] Notice, the button "Configure manually..." on the bottom left has become clickable. When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|thumb|left]] Now, fill in the information as follows: [[File:Fill advanced.png|thumb|left]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | Protocol:|| IMAP || SMTP |- | Server: || mail.ulyssis.org || smtps.kuleuven.be |- |Port: || 993 || 443 |- |SSL: || SSL/TLS || SSL/TLS |- |Authentication: || Autodetect || Autodetect |- | Username: || ULYSSIS-username || r-number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|thumb|left]] If this test succeeds, the pop-up can be closed by pressing the "Done" button on the bottom right. When the pop-up closes, a mailbox should be added to the left side of the main Thunderbird window. [[File:After Clicking Done.png|thumb|left]] Notice, there is no email present yet. This can be resolved by pressing the "Get Messages" button on the top left of the window: [[File:After Clicking GetMessages.png|thumb|left|]] After this first setup, the mailbox should synchronize automatically. [[Category:Mail]] 4f181f29afcd0ae7be7601a48c0a7705a94ba114 1606 1597 2021-12-01T14:39:42Z Debber 46 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. Do note: this article is written for users who opted for a ULYSSIS mailbox. not for users who opted for a forwarded email address. ==Thunderbird== Thunderbird is a free and open-source email client made by Mozilla. It is available for download at https://thunderbird.net. The installation process is fairly easy and thus will not be covered in this article. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|thumb|left]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the Email button (highlighted in blue) under the "Set Up Another Account" section: [[File:New Mailbox.png|thumb|left]] Once the pop-up is present, it becomes possible to dial in the settings for a mailbox. The first step is to fill in the Email adress field: [[File:Fill in email.png|thumb|left]] Notice, the button "Configure manually..." on the bottom left has become clickable. When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|thumb|left]] Now, fill in the information as follows: [[File:Fill advanced.png|thumb|left]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | Protocol:|| IMAP || SMTP |- | Server: || mail.ulyssis.org || smtps.kuleuven.be |- |Port: || 993 || 443 |- |SSL: || SSL/TLS || SSL/TLS |- |Authentication: || Autodetect || Autodetect |- | Username: || ULYSSIS-username || r-number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|thumb|left]] If this test succeeds, the pop-up can be closed by pressing the "Done" button on the bottom right. When the pop-up closes, a mailbox should be added to the left side of the main Thunderbird window. After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|thumb|left|]] [[Category:Mail]] dfe3e5fc9a71b55c9de053d3c7d6bc182c9c525a 1607 1606 2021-12-01T14:44:50Z Debber 46 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. Do note: this article is written for users who opted for a ULYSSIS mailbox. not for users who opted for a forwarded email address. ==Thunderbird== Thunderbird is a free and open-source email client made by Mozilla. It is available for download at https://thunderbird.net. The installation process is fairly easy and thus will not be covered in this article. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|thumb|left]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the Email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|thumb|left]] Once the pop-up is present, it becomes possible to dial in the settings for a mailbox. The first step is to fill in the Email adress field: [[File:Fill in email.png|thumb|left]] Notice, the button "Configure manually..." on the bottom left has become clickable (as seen on the above screenshot). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|thumb|left]] Now, fill in the information as follows: [[File:Fill advanced.png|thumb|left]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | Protocol:|| IMAP || SMTP |- | Server: || mail.ulyssis.org || smtps.kuleuven.be |- |Port: || 993 || 443 |- |SSL: || SSL/TLS || SSL/TLS |- |Authentication: || Autodetect || Autodetect |- | Username: || ULYSSIS-username || r-number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|thumb|left]] If this test succeeds, the pop-up can be closed by pressing the "Done" button on the bottom right of the previous screenshot. When the pop-up closes, a mailbox should be added to the left side of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|thumb|left|]] [[Category:Mail]] 8b4aba0b7ce33e9fe4bd197cefc99867829ac1a4 1612 1607 2021-12-01T19:35:19Z Debber 46 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. Do note: this article is written for users who opted for a ULYSSIS mailbox. not for users who opted for a forwarded email address. ==Thunderbird== Thunderbird is a free and open-source email client made by Mozilla. It is available for download at https://thunderbird.net. The installation process is fairly easy and thus will not be covered in this article. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|thumb|left]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the Email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|thumb|left]] Once the pop-up is present, it becomes possible to dial in the settings for a mailbox. The first step is to fill in the Email adress field: [[File:Fill in email.png|thumb|left]] Notice, the button "Configure manually..." on the bottom left has become clickable (as seen on the above screenshot). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|thumb|left]] Now, fill in the information as follows: [[File:Fill advanced.png|thumb|left]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | Protocol:|| IMAP || SMTP |- | Server: || mail.ulyssis.org || smtps.kuleuven.be |- |Port: || 993 || 443 |- |SSL: || SSL/TLS || SSL/TLS |- |Authentication: || Autodetect || Autodetect |- | Username: || ULYSSIS-username || r-number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|thumb|left]] If this test succeeds, the pop-up can be closed by pressing the "Done" button on the bottom right of the previous screenshot. When the pop-up closes, a mailbox should be added to the left side of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|thumb|left|]] {{notice|notice|When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent.}} [[Category:Mail]] a6dd78d16fd78f681b4f91b9ecb407bd12883b00 1613 1612 2021-12-01T19:46:18Z Debber 46 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. Do note: this article is written for users who opted for a ULYSSIS mailbox. not for users who opted for a forwarded email address. ==Thunderbird== Thunderbird is a free and open-source email client made by Mozilla. It is available for download at https://thunderbird.net. The installation process is fairly easy and thus will not be covered in this article. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|frame|left]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the Email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|frame|left]] Once the pop-up is present, it becomes possible to dial in the settings for a mailbox. The first step is to fill in the Email adress field: [[File:Fill in email.png|frame|left]] Notice, the button "Configure manually..." on the bottom left has become clickable (as seen on the above screenshot). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|frame|left]] Now, fill in the information as follows: [[File:Fill advanced.png|frame|left]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | Protocol:|| IMAP || SMTP |- | Server: || mail.ulyssis.org || smtps.kuleuven.be |- |Port: || 993 || 443 |- |SSL: || SSL/TLS || SSL/TLS |- |Authentication: || Autodetect || Autodetect |- | Username: || ULYSSIS-username || r-number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|frame|left]] If this test succeeds, the pop-up can be closed by pressing the "Done" button on the bottom right of the previous screenshot. When the pop-up closes, a mailbox should be added to the left side of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|frame|left|]] {{notice|notice|When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent.}} [[Category:Mail]] 981808c149305823ef6f52d64a95de888e3f7136 1614 1613 2021-12-01T19:49:51Z Debber 46 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. Do note: this article is written for users who opted for a ULYSSIS mailbox. not for users who opted for a forwarded email address (more information about forwarders is available at https://docs.ulyssis.org/Forwarders). ==Thunderbird== Thunderbird is a free and open-source email client made by Mozilla. It is available for download at https://thunderbird.net. The installation process is fairly easy and thus will not be covered in this article. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|frame|left]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the Email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|frame|left]] Once the pop-up is present, it becomes possible to dial in the settings for a mailbox. The first step is to fill in the Email adress field: [[File:Fill in email.png|frame|left]] Notice, the button "Configure manually..." on the bottom left has become clickable (as seen on the above screenshot). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|frame|left]] Now, fill in the information as follows: [[File:Fill advanced.png|frame|left]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | Protocol:|| IMAP || SMTP |- | Server: || mail.ulyssis.org || smtps.kuleuven.be |- |Port: || 993 || 443 |- |SSL: || SSL/TLS || SSL/TLS |- |Authentication: || Autodetect || Autodetect |- | Username: || ULYSSIS-username || r-number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|frame|left]] If this test succeeds, the pop-up can be closed by pressing the "Done" button on the bottom right of the previous screenshot. When the pop-up closes, a mailbox should be added to the left side of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|frame|left|]] {{notice|notice|When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent.}} [[Category:Mail]] 54697d6d4d5cec5c0852cf5842c81b0c886c1f00 1615 1614 2021-12-01T19:55:55Z Debber 46 /* Adding a ULYSSIS mailbox to Thunderbird */ wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. Do note: this article is written for users who opted for a ULYSSIS mailbox. not for users who opted for a forwarded email address (more information about forwarders is available at https://docs.ulyssis.org/Forwarders). ==Thunderbird== Thunderbird is a free and open-source email client made by Mozilla. It is available for download at https://thunderbird.net. The installation process is fairly easy and thus will not be covered in this article. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|10px|left|frame]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the Email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|frame|left]] Once the pop-up is present, it becomes possible to dial in the settings for a mailbox. The first step is to fill in the Email adress field: [[File:Fill in email.png|frame|left]] Notice, the button "Configure manually..." on the bottom left has become clickable (as seen on the above screenshot). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|frame|left]] Now, fill in the information as follows: [[File:Fill advanced.png|frame|left]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | Protocol:|| IMAP || SMTP |- | Server: || mail.ulyssis.org || smtps.kuleuven.be |- |Port: || 993 || 443 |- |SSL: || SSL/TLS || SSL/TLS |- |Authentication: || Autodetect || Autodetect |- | Username: || ULYSSIS-username || r-number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|frame|left]] If this test succeeds, the pop-up can be closed by pressing the "Done" button on the bottom right of the previous screenshot. When the pop-up closes, a mailbox should be added to the left side of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|frame|left|]] {{notice|notice|When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent.}} [[Category:Mail]] 7c9cadfa4a72435452dc35d6242b7a428269f6b3 1616 1615 2021-12-01T19:56:32Z Debber 46 /* Adding a ULYSSIS mailbox to Thunderbird */ wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. Do note: this article is written for users who opted for a ULYSSIS mailbox. not for users who opted for a forwarded email address (more information about forwarders is available at https://docs.ulyssis.org/Forwarders). ==Thunderbird== Thunderbird is a free and open-source email client made by Mozilla. It is available for download at https://thunderbird.net. The installation process is fairly easy and thus will not be covered in this article. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|frame]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the Email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|frame|left]] Once the pop-up is present, it becomes possible to dial in the settings for a mailbox. The first step is to fill in the Email adress field: [[File:Fill in email.png|frame|left]] Notice, the button "Configure manually..." on the bottom left has become clickable (as seen on the above screenshot). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|frame|left]] Now, fill in the information as follows: [[File:Fill advanced.png|frame|left]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | Protocol:|| IMAP || SMTP |- | Server: || mail.ulyssis.org || smtps.kuleuven.be |- |Port: || 993 || 443 |- |SSL: || SSL/TLS || SSL/TLS |- |Authentication: || Autodetect || Autodetect |- | Username: || ULYSSIS-username || r-number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|frame|left]] If this test succeeds, the pop-up can be closed by pressing the "Done" button on the bottom right of the previous screenshot. When the pop-up closes, a mailbox should be added to the left side of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|frame|left|]] {{notice|notice|When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent.}} [[Category:Mail]] e9ed68b2fb30126f67077e6e23451652a6fae6e5 1617 1616 2021-12-01T20:01:39Z Debber 46 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. Do note: this article is written for users who opted for a ULYSSIS mailbox. not for users who opted for a forwarded email address (more information about forwarders is available at https://docs.ulyssis.org/Forwarders). ==Thunderbird== Thunderbird is a free and open-source email client made by Mozilla. It is available for download at https://thunderbird.net. The installation process is fairly easy and thus will not be covered in this article. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the Email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it becomes possible to dial in the settings for a mailbox. The first step is to fill in the Email adress field: [[File:Fill in email.png|left|alt=|thumb|432x432px]] Notice, the button "Configure manually..." on the bottom left has become clickable (as seen on the above screenshot). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | Protocol:|| IMAP || SMTP |- | Server: || mail.ulyssis.org || smtps.kuleuven.be |- |Port: || 993 || 443 |- |SSL: || SSL/TLS || SSL/TLS |- |Authentication: || Autodetect || Autodetect |- | Username: || ULYSSIS-username || r-number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up can be closed by pressing the "Done" button on the bottom right of the previous screenshot. When the pop-up closes, a mailbox should be added to the left side of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] {{notice|notice|When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent.}} [[Category:Mail]] 2d25b899c5f8fcd5f2dc7745eab5bb80232279d5 1618 1617 2021-12-01T20:05:01Z Debber 46 /* Adding a ULYSSIS mailbox to Thunderbird */ wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. Do note: this article is written for users who opted for a ULYSSIS mailbox. not for users who opted for a forwarded email address (more information about forwarders is available at https://docs.ulyssis.org/Forwarders). ==Thunderbird== Thunderbird is a free and open-source email client made by Mozilla. It is available for download at https://thunderbird.net. The installation process is fairly easy and thus will not be covered in this article. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the Email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it becomes possible to fill in the settings for a mailbox. The first step is to fill in the Email adress field: [[File:Fill in email.png|left|alt=|thumb|432x432px]] Notice, the button "Configure manually..." on the bottom left has become clickable (as seen on the above screenshot). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | Protocol:|| IMAP || SMTP |- | Server: || mail.ulyssis.org || smtps.kuleuven.be |- |Port: || 993 || 443 |- |SSL: || SSL/TLS || SSL/TLS |- |Authentication: || Autodetect || Autodetect |- | Username: || ULYSSIS-username || r-number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up can be closed by pressing the "Done" button on the bottom right of the previous screenshot. When the pop-up closes, a mailbox should be added to the left side of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] {{notice|notice|When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent.}} [[Category:Mail]] 870f7daf684df264fd920a786f48804b5fc9efcb 1619 1618 2021-12-01T20:14:55Z Debber 46 /* Adding a ULYSSIS mailbox to Thunderbird */ wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. Do note: this article is written for users who opted for a ULYSSIS mailbox. not for users who opted for a forwarded email address (more information about forwarders is available at https://docs.ulyssis.org/Forwarders). ==Thunderbird== Thunderbird is a free and open-source email client made by Mozilla. It is available for download at https://thunderbird.net. The installation process is fairly easy and thus will not be covered in this article. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the Email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it becomes possible to fill in the settings for a mailbox. The first step is to fill in the Email adress field (notice, this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Notice, the button "Configure manually..." on the bottom left has become clickable (as seen on the above screenshot). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | Protocol:|| IMAP || SMTP |- | Server: || mail.ulyssis.org || smtps.kuleuven.be |- |Port: || 993 || 443 |- |SSL: || SSL/TLS || SSL/TLS |- |Authentication: || Autodetect || Autodetect |- | Username: || ULYSSIS-username || r-number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up can be closed by pressing the "Done" button on the bottom right of the previous screenshot. When the pop-up closes, a mailbox should be added to the left side of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] {{notice|notice|When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent.}} [[Category:Mail]] 0d648a3fe4add25de37fe50bfd8f800ca90cb378 1627 1619 2021-12-02T08:30:22Z Debber 46 /* Thunderbird */ wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. Do note: this article is written for users who opted for a ULYSSIS mailbox. not for users who opted for a forwarded email address (more information about forwarders is available at https://docs.ulyssis.org/Forwarders). ==Thunderbird== Thunderbird is a free and open-source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the Email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it becomes possible to fill in the settings for a mailbox. The first step is to fill in the Email adress field (notice, this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Notice, the button "Configure manually..." on the bottom left has become clickable (as seen on the above screenshot). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | Protocol:|| IMAP || SMTP |- | Server: || mail.ulyssis.org || smtps.kuleuven.be |- |Port: || 993 || 443 |- |SSL: || SSL/TLS || SSL/TLS |- |Authentication: || Autodetect || Autodetect |- | Username: || ULYSSIS-username || r-number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up can be closed by pressing the "Done" button on the bottom right of the previous screenshot. When the pop-up closes, a mailbox should be added to the left side of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] {{notice|notice|When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent.}} [[Category:Mail]] 098870f500c11f7480ce747bed7ee25a70792e70 1628 1627 2021-12-02T19:53:21Z Debber 46 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to create your very own ULYSSIS mailbox (for more information see: https://docs.ulyssis.org/Introduction_to_ULYSSIS_email). It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. {{notice|Do note:| This article is written for users who opted for a ULYSSIS mailbox. not for users who opted for a forwarded email address (more information about forwarders is available at https://docs.ulyssis.org/Forwarders).}} ==Thunderbird== Thunderbird is a free and open-source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the Email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it becomes possible to fill in the settings for a mailbox. The first step is to fill in the Email adress field (notice, this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Notice, the button "Configure manually..." on the bottom left has become clickable (as seen on the above screenshot). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | Protocol:|| IMAP || SMTP |- | Server: || mail.ulyssis.org || smtps.kuleuven.be |- |Port: || 993 || 443 |- |SSL: || SSL/TLS || SSL/TLS |- |Authentication: || Autodetect || Autodetect |- | Username: || ULYSSIS-username || r-number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up can be closed by pressing the "Done" button on the bottom right of the previous screenshot. When the pop-up closes, a mailbox should be added to the left side of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] {{notice|notice|When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent.}} [[Category:Mail]] a2e8333d351bc2a34e57417935657ae8d4a5de00 1629 1628 2021-12-02T20:08:10Z Debber 46 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to create your very own ULYSSIS mailbox (for more information see: https://docs.ulyssis.org/Introduction_to_ULYSSIS_email). It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open-source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the Email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it becomes possible to fill in the settings for a mailbox. The first step is to fill in the Email adress field (notice, this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Notice, the button "Configure manually..." on the bottom left has become clickable (as seen on the above screenshot). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | Protocol:|| IMAP || SMTP |- | Server: || mail.ulyssis.org || smtps.kuleuven.be |- |Port: || 993 || 443 |- |SSL: || SSL/TLS || SSL/TLS |- |Authentication: || Autodetect || Autodetect |- | Username: || ULYSSIS-username || r-number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up can be closed by pressing the "Done" button on the bottom right of the previous screenshot. When the pop-up closes, a mailbox should be added to the left side of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] {{notice|notice|When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent.}} [[Category:Mail]] e55a16992cc482cff08a210545c3a3360858c2bd 1630 1629 2021-12-02T20:13:45Z Debber 46 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to create your very own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open-source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the Email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it becomes possible to fill in the settings for a mailbox. The first step is to fill in the Email adress field (notice, this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Notice, the button "Configure manually..." on the bottom left has become clickable (as seen on the above screenshot). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | Protocol:|| IMAP || SMTP |- | Server: || mail.ulyssis.org || smtps.kuleuven.be |- |Port: || 993 || 443 |- |SSL: || SSL/TLS || SSL/TLS |- |Authentication: || Autodetect || Autodetect |- | Username: || ULYSSIS-username || r-number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up can be closed by pressing the "Done" button on the bottom right of the previous screenshot. When the pop-up closes, a mailbox should be added to the left side of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] {{notice|notice|When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent.}} [[Category:Mail]] 5efe9eb564e4b6765b16a540274a749805ee032d 1631 1630 2021-12-02T20:14:00Z Debber 46 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to create your very own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open-source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the Email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it becomes possible to fill in the settings for a mailbox. The first step is to fill in the Email adress field (notice, this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Notice, the button "Configure manually..." on the bottom left has become clickable (as seen on the above screenshot). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | Protocol:|| IMAP || SMTP |- | Server: || mail.ulyssis.org || smtps.kuleuven.be |- |Port: || 993 || 443 |- |SSL: || SSL/TLS || SSL/TLS |- |Authentication: || Autodetect || Autodetect |- | Username: || ULYSSIS-username || r-number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up can be closed by pressing the "Done" button on the bottom right of the previous screenshot. When the pop-up closes, a mailbox should be added to the left side of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] {{notice|notice|When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent.}} [[Category:Mail]] b2d34467d1181db1811bb0a3910cf1095ce164bf 1632 1631 2021-12-02T20:16:32Z Debber 46 /* Thunderbird */ wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to create your very own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the Email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it becomes possible to fill in the settings for a mailbox. The first step is to fill in the Email adress field (notice, this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Notice, the button "Configure manually..." on the bottom left has become clickable (as seen on the above screenshot). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | Protocol:|| IMAP || SMTP |- | Server: || mail.ulyssis.org || smtps.kuleuven.be |- |Port: || 993 || 443 |- |SSL: || SSL/TLS || SSL/TLS |- |Authentication: || Autodetect || Autodetect |- | Username: || ULYSSIS-username || r-number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up can be closed by pressing the "Done" button on the bottom right of the previous screenshot. When the pop-up closes, a mailbox should be added to the left side of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] {{notice|notice|When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent.}} [[Category:Mail]] 14cf10b862f945b04635820eea13f7128a733503 1633 1632 2021-12-02T20:17:59Z Debber 46 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to create your very own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the Email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it is possible to fill in the settings for a mailbox. The first step is to fill in the Email adress field (notice, this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Notice, the button "Configure manually..." on the bottom left has become clickable (as seen on the above screenshot). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | Protocol:|| IMAP || SMTP |- | Server: || mail.ulyssis.org || smtps.kuleuven.be |- |Port: || 993 || 443 |- |SSL: || SSL/TLS || SSL/TLS |- |Authentication: || Autodetect || Autodetect |- | Username: || ULYSSIS-username || r-number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up can be closed by pressing the "Done" button on the bottom right of the previous screenshot. When the pop-up closes, a mailbox should be added to the left side of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] {{notice|notice|When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent.}} [[Category:Mail]] fbcaeef95209dda6b5d9e51c3c7a4090dcc85671 1634 1633 2021-12-02T20:21:17Z Debber 46 /* Adding a ULYSSIS mailbox to Thunderbird */ wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to create your very own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the Email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it is possible to fill in the login details for a mailbox. The first step is to fill in your name, Email address and password: (notice, this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Notice, the button "Configure manually..." on the bottom left has become clickable (as seen on the above screenshot). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | Protocol:|| IMAP || SMTP |- | Server: || mail.ulyssis.org || smtps.kuleuven.be |- |Port: || 993 || 443 |- |SSL: || SSL/TLS || SSL/TLS |- |Authentication: || Autodetect || Autodetect |- | Username: || ULYSSIS-username || r-number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up can be closed by pressing the "Done" button on the bottom right of the previous screenshot. When the pop-up closes, a mailbox should be added to the left side of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] {{notice|notice|When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent.}} [[Category:Mail]] 944999e9dfe79cf1140b1474df433753b7fae77d 1635 1634 2021-12-02T20:31:17Z Debber 46 /* Adding a ULYSSIS mailbox to Thunderbird */ wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to create your very own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it is possible to fill in the login details for a mailbox. The first step is to fill in your name, email address and password: (notice, this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Notice, the button "Configure manually..." on the bottom left has become clickable (as seen on the above screenshot). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | Protocol:|| IMAP || SMTP |- | Server: || mail.ulyssis.org || smtps.kuleuven.be |- |Port: || 993 || 443 |- |SSL: || SSL/TLS || SSL/TLS |- |Authentication: || Autodetect || Autodetect |- | Username: || ULYSSIS-username || r-number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up can be closed by pressing the "Done" button on the bottom right of the previous screenshot. When the pop-up closes, a mailbox should be added to the left side of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] {{notice|notice|When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent.}} [[Category:Mail]] a78ef4f52c70715d47b7bdc1cbba08a95a298826 1636 1635 2021-12-02T20:44:00Z Debber 46 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to create your very own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it is possible to fill in the login details for a mailbox. The first step is to fill in your name, email address and password: (notice, this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Notice, the button "Configure manually..." on the bottom left has become clickable (as seen on the above screenshot). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | Protocol:|| IMAP || SMTP |- | Server: || mail.ulyssis.org || smtps.kuleuven.be |- |Port: || 993 || 443 |- |SSL: || SSL/TLS || SSL/TLS |- |Authentication: || Autodetect || Autodetect |- | Username: || ULYSSIS-username || r-number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up can be closed by pressing the "Done" button on the bottom right of the previous screenshot. When the pop-up closes, a mailbox should be added to the left side of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent. [[Category:Mail]] 14c53f9b9a6b68385c1891de16b90c546650ef4a 1638 1636 2021-12-02T21:23:33Z Debber 46 /* Adding a ULYSSIS mailbox to Thunderbird */ wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to create your very own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it is possible to fill in the login details for a mailbox. The first step is to fill in your name, email address and password (this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Next, the button "Configure manually..." on the bottom left will have become clickable (as seen on the screenshot above). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | Protocol:|| IMAP || SMTP |- | Server: || mail.ulyssis.org || smtps.kuleuven.be |- |Port: || 993 || 443 |- |SSL: || SSL/TLS || SSL/TLS |- |Authentication: || Autodetect || Autodetect |- | Username: || ULYSSIS-username || r-number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up will close when the "Done" button has been clicked. After the pop-up closes, a mailbox should be added to the left sidebar of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent. [[Category:Mail]] 6f8dd051dbaddf6bc95d4428d0f07ea77d6d1f71 1639 1638 2021-12-02T21:27:34Z Debber 46 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to create your very own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it is possible to fill in the login details for a mailbox. The first step is to fill in your name, email address and password (this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Next, the button "Configure manually..." on the bottom left will have become clickable (as seen on the screenshot above). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- |style="padding: 10px" | Protocol:|| IMAP || SMTP |- |style="padding: 10px" | Server: || mail.ulyssis.org || smtps.kuleuven.be |- |style="padding: 10px" |Port: || 993 || 443 |- style="padding: 10px" ||SSL: || SSL/TLS || SSL/TLS |- |style="padding: 10px" |Authentication: || Autodetect || Autodetect |- |style="padding: 10px" | Username: || ULYSSIS username || m/r/s/u number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up will close when the "Done" button has been clicked. After the pop-up closes, a mailbox should be added to the left sidebar of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent. [[Category:Mail]] b23a3fe53090a1d53460eb8747b3afe6cabece55 1640 1639 2021-12-02T21:28:31Z Debber 46 Undo revision 1639 by [[Special:Contributions/Debber|Debber]] ([[User talk:Debber|talk]]) wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to create your very own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it is possible to fill in the login details for a mailbox. The first step is to fill in your name, email address and password (this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Next, the button "Configure manually..." on the bottom left will have become clickable (as seen on the screenshot above). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | Protocol:|| IMAP || SMTP |- | Server: || mail.ulyssis.org || smtps.kuleuven.be |- |Port: || 993 || 443 |- |SSL: || SSL/TLS || SSL/TLS |- |Authentication: || Autodetect || Autodetect |- | Username: || ULYSSIS-username || r-number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up will close when the "Done" button has been clicked. After the pop-up closes, a mailbox should be added to the left sidebar of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent. [[Category:Mail]] 6f8dd051dbaddf6bc95d4428d0f07ea77d6d1f71 1641 1640 2021-12-02T21:36:01Z Debber 46 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to create your very own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it is possible to fill in the login details for a mailbox. The first step is to fill in your name, email address and password (this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Next, the button "Configure manually..." on the bottom left will have become clickable (as seen on the screenshot above). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | Protocol:|| IMAP || SMTP |- | Server: || mail.ulyssis.org || smtps.kuleuven.be |- |Port: || 993 || 443 |- |SSL: || SSL/TLS || SSL/TLS |- |Authentication: || Autodetect || Autodetect |- | Username: || ULYSSIS username || r/m/s/u number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up will close when the "Done" button has been clicked. After the pop-up closes, a mailbox should be added to the left sidebar of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent. [[Category:Mail]] 8e7708c2152ac4979991fdb8c20d0e4e9c748b35 1642 1641 2021-12-02T21:40:11Z Debber 46 /* Adding a ULYSSIS mailbox to Thunderbird */ wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to create your very own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it is possible to fill in the login details for a mailbox. The first step is to fill in your name, email address and password (this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Next, the button "Configure manually..." on the bottom left will have become clickable (as seen on the screenshot above). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | style="padding: 10px" | Protocol:|| IMAP || SMTP |- | style="padding: 10px" |Server: || mail.ulyssis.org || smtps.kuleuven.be |- |style="padding: 10px" |Port: || 993 || 443 |- |style="padding: 10px" |SSL: || SSL/TLS || SSL/TLS |- |style="padding: 10px" |Authentication: || Autodetect || Autodetect |- |style="padding: 10px" | Username: || ULYSSIS username || r/m/s/u number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up will close when the "Done" button has been clicked. After the pop-up closes, a mailbox should be added to the left sidebar of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent. [[Category:Mail]] 1d40ba96c1eeeb90a9cd84bb4b6e8dbb5abfa325 1643 1642 2021-12-02T21:43:26Z Bert 8 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to create your very own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it is possible to fill in the login details for a mailbox. The first step is to fill in your name, email address and password (this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Next, the button "Configure manually..." on the bottom left will have become clickable (as seen on the screenshot above). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- | style="padding: 0px 10px" | Protocol:|| IMAP || SMTP |- | style="padding: 0px 10px" |Server: || mail.ulyssis.org || smtps.kuleuven.be |- |style="padding: 0px 10px" |Port: || 993 || 443 |- |style="padding: 0px 10px" |SSL: || SSL/TLS || SSL/TLS |- |style="padding: 0px 10px" |Authentication: || Autodetect || Autodetect |- |style="padding: 0px 10px" | Username: || ULYSSIS username || r/m/s/u number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up will close when the "Done" button has been clicked. After the pop-up closes, a mailbox should be added to the left sidebar of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent. [[Category:Mail]] ed51f143a8a47ec4d65fbd78591f3e1c88129469 1644 1643 2021-12-02T21:47:16Z Bert 8 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to create your very own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it is possible to fill in the login details for a mailbox. The first step is to fill in your name, email address and password (this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Next, the button "Configure manually..." on the bottom left will have become clickable (as seen on the screenshot above). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" ! ! style="padding-right: 10px;" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- || Protocol: || IMAP || SMTP |- || Server: || mail.ulyssis.org || smtps.kuleuven.be |- || Port: || 993 || 443 |- || SSL: || SSL/TLS || SSL/TLS |- || Authentication: || Autodetect || Autodetect |- || Username: || ULYSSIS username || r/m/s/u number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up will close when the "Done" button has been clicked. After the pop-up closes, a mailbox should be added to the left sidebar of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent. [[Category:Mail]] 15f39386535b1ba81001d70168ac63e0c3b9836b 1645 1644 2021-12-02T21:48:09Z Bert 8 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to create your very own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it is possible to fill in the login details for a mailbox. The first step is to fill in your name, email address and password (this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Next, the button "Configure manually..." on the bottom left will have become clickable (as seen on the screenshot above). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- ! ! style="padding-right: 10px;" ! INCOMING !! OUTGOING |- || Protocol: || IMAP || SMTP |- || Server: || mail.ulyssis.org || smtps.kuleuven.be |- || Port: || 993 || 443 |- || SSL: || SSL/TLS || SSL/TLS |- || Authentication: || Autodetect || Autodetect |- || Username: || ULYSSIS username || r/m/s/u number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up will close when the "Done" button has been clicked. After the pop-up closes, a mailbox should be added to the left sidebar of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent. [[Category:Mail]] e4e699d4c90f7cc31086d550a1647a3af0df9ffd 0 221 1598 2021-11-30T22:51:13Z Sydon 48 nieuwe introductie, comments in vgl met de oude? @sydon wikitext text/x-wiki ==Introduction== Nieuw : Content Management Systems, also known as CMS', are easy-to-use tools that help set up a website while not requiring a lot of knowledge of programming or configuration. However, as is common in many popular and widespread software, various bug or errors can occur in the program. These system flaws can be exploited by hackers to gain access to websites or databases connected to the CMS'. Whenever a new update is released for a CMS or any other popular software (E.g., MediaWiki, PhPBB) hackers will find out which security flaws have been patched, and with this knowledge, they try to find new systems flaws to gain access to the websites or databases. This is the reason why it is so critical to update a CMS, plugins, themes, or any related software as soon as the updates roll out. To help you facilitate this, we have created a tool to help you keep the most used software up-to-date. Currently, this feature is only active if you have an organization or student (dutch = Kring/Facultair overlegorgaan) account. oud: Content Management Systems, or CMSs, are easy tools to set up a website without requiring much programming or configuration. However, as is common in a lot of popular and wide-spread software, bugs or errors in the code occur. These errors can be exploited by hackers to gain access to websites or databases connected to those CMSs. Whenever a new update for a CMS, or other popular software (MediaWiki, PhpBB) is released, hackers will know which security flaws have been fixed, and try to hack websites using this knowledge. This is why it's critical to update a CMS, plugins/themes, or any related software as soon as the update comes out. To help you facilitate this, we have created a tool to help you keep the most popular software up-to-date. Currently this feature is only active if you have an organisation or student union (kring/facultair overlegorgaan) account. ==I received an e-mail!== If you receive an e-mail from the Version Checker, it's best you update the software mentioned in the e-mail as soon as possible. Make sure to download the latest public version, not just any newer version. It's also best to check if any other software you run is up-to-date: not all software is checked by the tool (as seen below). ==Supported Software== *Drupal, Drupal Modules, Drupal Themes *Joomla (Joomla Plugins are not supported yet) *MediaWiki (MediaWiki Extensions and Themes are not supported yet) *PhpBB, PhpBB Plugins, PhpBB Styles *WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the Version Checker does the following: *Scan relevant files, detect supported software, and store in database *Check the version and validity of outdated software *Mail accounts using outdated software ==Stored Data== The following data is stored in the database: *The location of the CMS, plugin/extension or theme *The responsible organisation or student union (kring/facultair overlegorgaan) *The detected software version *The type and name of the software *The update URL for the software *The date the entry was added ==Ignored Paths== The Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. ==Ignored Organisations/Student Unions== In addition to the ignored paths feature, the Version Checker can also ignore specific Organisations or Student Unions entirely. This feature is possible on request, but only after extensive deliberation with ULYSSIS. Enabling this feature also carries possible consequences: no more mails about outdated software, ever (unless enabled on request), and no support if/when your account gets hacked (the account will be suspended immediately). 3b2acac5bf7ec6a4044463612d9f36f708706805 1620 1598 2021-12-01T21:50:37Z Sydon 48 /* Introduction */ wikitext text/x-wiki ==Introduction== Nieuw : Many of our users use the same populair software. However, as is common in many popular and widespread software, various bug or errors can occur in the program. These flaws can be exploited by hackers to gain access to websites or databases connected. Whenever a new update is released for any other popular software (E.g., Wordpress, MediaWiki, Joomla) hackers will find out which security flaws have been patched, and with this knowledge, they try to find new systems flaws to gain access to the websites or databases. This is the reason why it is so critical to update the software itself, plugins, themes, or any related software as soon as the updates roll out. To help facilitate this and prevent security breaches, we have created a tool to help you keep the most used software up-to-date. Currently, this feature is only active if you have an organization or student union account. oud: Content Management Systems, or CMSs, are easy tools to set up a website without requiring much programming or configuration. However, as is common in a lot of popular and wide-spread software, bugs or errors in the code occur. These errors can be exploited by hackers to gain access to websites or databases connected to those CMSs. Whenever a new update for a CMS, or other popular software (MediaWiki, PhpBB) is released, hackers will know which security flaws have been fixed, and try to hack websites using this knowledge. This is why it's critical to update a CMS, plugins/themes, or any related software as soon as the update comes out. To help you facilitate this, we have created a tool to help you keep the most popular software up-to-date. Currently this feature is only active if you have an organisation or student union (kring/facultair overlegorgaan) account. ==I received an e-mail!== If you receive an e-mail from the Version Checker, it's best you update the software mentioned in the e-mail as soon as possible. Make sure to download the latest public version, not just any newer version. It's also best to check if any other software you run is up-to-date: not all software is checked by the tool (as seen below). ==Supported Software== *Drupal, Drupal Modules, Drupal Themes *Joomla (Joomla Plugins are not supported yet) *MediaWiki (MediaWiki Extensions and Themes are not supported yet) *PhpBB, PhpBB Plugins, PhpBB Styles *WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the Version Checker does the following: *Scan relevant files, detect supported software, and store in database *Check the version and validity of outdated software *Mail accounts using outdated software ==Stored Data== The following data is stored in the database: *The location of the CMS, plugin/extension or theme *The responsible organisation or student union (kring/facultair overlegorgaan) *The detected software version *The type and name of the software *The update URL for the software *The date the entry was added ==Ignored Paths== The Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. ==Ignored Organisations/Student Unions== In addition to the ignored paths feature, the Version Checker can also ignore specific Organisations or Student Unions entirely. This feature is possible on request, but only after extensive deliberation with ULYSSIS. Enabling this feature also carries possible consequences: no more mails about outdated software, ever (unless enabled on request), and no support if/when your account gets hacked (the account will be suspended immediately). 1164de0b2b673522f25f149352af9889bf4ff578 1621 1620 2021-12-01T21:52:02Z Sydon 48 /* I received an e-mail! */ wikitext text/x-wiki ==Introduction== Nieuw : Many of our users use the same populair software. However, as is common in many popular and widespread software, various bug or errors can occur in the program. These flaws can be exploited by hackers to gain access to websites or databases connected. Whenever a new update is released for any other popular software (E.g., Wordpress, MediaWiki, Joomla) hackers will find out which security flaws have been patched, and with this knowledge, they try to find new systems flaws to gain access to the websites or databases. This is the reason why it is so critical to update the software itself, plugins, themes, or any related software as soon as the updates roll out. To help facilitate this and prevent security breaches, we have created a tool to help you keep the most used software up-to-date. Currently, this feature is only active if you have an organization or student union account. oud: Content Management Systems, or CMSs, are easy tools to set up a website without requiring much programming or configuration. However, as is common in a lot of popular and wide-spread software, bugs or errors in the code occur. These errors can be exploited by hackers to gain access to websites or databases connected to those CMSs. Whenever a new update for a CMS, or other popular software (MediaWiki, PhpBB) is released, hackers will know which security flaws have been fixed, and try to hack websites using this knowledge. This is why it's critical to update a CMS, plugins/themes, or any related software as soon as the update comes out. To help you facilitate this, we have created a tool to help you keep the most popular software up-to-date. Currently this feature is only active if you have an organisation or student union (kring/facultair overlegorgaan) account. ==What to do once you receive an e-mail!== If you receive an e-mail from the Version Checker, it's best you update the software mentioned in the e-mail as soon as possible. Make sure to download the latest public version, not just any newer version. It's also best to check if any other software you run is up-to-date: not all software is checked by the tool (as seen below). ==Supported Software== *Drupal, Drupal Modules, Drupal Themes *Joomla (Joomla Plugins are not supported yet) *MediaWiki (MediaWiki Extensions and Themes are not supported yet) *PhpBB, PhpBB Plugins, PhpBB Styles *WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the Version Checker does the following: *Scan relevant files, detect supported software, and store in database *Check the version and validity of outdated software *Mail accounts using outdated software ==Stored Data== The following data is stored in the database: *The location of the CMS, plugin/extension or theme *The responsible organisation or student union (kring/facultair overlegorgaan) *The detected software version *The type and name of the software *The update URL for the software *The date the entry was added ==Ignored Paths== The Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. ==Ignored Organisations/Student Unions== In addition to the ignored paths feature, the Version Checker can also ignore specific Organisations or Student Unions entirely. This feature is possible on request, but only after extensive deliberation with ULYSSIS. Enabling this feature also carries possible consequences: no more mails about outdated software, ever (unless enabled on request), and no support if/when your account gets hacked (the account will be suspended immediately). 5e8147b3dc1b0e151da1a1dea0d4156ddc31112a 1622 1621 2021-12-01T21:54:05Z Sydon 48 /* Supported Software */ wikitext text/x-wiki ==Introduction== Many of our users use the same populair software. However, as is common in many popular and widespread software, various bug or errors can occur in the program. These flaws can be exploited by hackers to gain access to websites or databases connected. Whenever a new update is released for any other popular software (E.g., Wordpress, MediaWiki, Joomla) hackers will find out which security flaws have been patched, and with this knowledge, they try to find new systems flaws to gain access to the websites or databases. This is the reason why it is so critical to update the software itself, plugins, themes, or any related software as soon as the updates roll out. To help facilitate this and prevent security breaches, we have created a tool to help you keep the most used software up-to-date. Currently, this feature is only active if you have an organization or student union account. ==What to do once you receive an e-mail!== If you receive an e-mail from the Version Checker, it's best you update the software mentioned in the e-mail as soon as possible. Make sure to download the latest public version, not just any newer version. It's also best to check if any other software you run is up-to-date: not all software is checked by the tool (as seen below). ==Supported Software== kan niet alles supporteren etc, hebben populairste gekozen en gekeken welke het vaakste security breaches krijgen. die worden gekozen om te supporten. en die ook GEKUNNEN GESUPPORT WORDEN; *Drupal, Drupal Modules, Drupal Themes *Joomla (Joomla Plugins are not supported yet) *MediaWiki (MediaWiki Extensions and Themes are not supported yet) *PhpBB, PhpBB Plugins, PhpBB Styles *WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the Version Checker does the following: *Scan relevant files, detect supported software, and store in database *Check the version and validity of outdated software *Mail accounts using outdated software ==Stored Data== The following data is stored in the database: *The location of the CMS, plugin/extension or theme *The responsible organisation or student union (kring/facultair overlegorgaan) *The detected software version *The type and name of the software *The update URL for the software *The date the entry was added ==Ignored Paths== The Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. ==Ignored Organisations/Student Unions== In addition to the ignored paths feature, the Version Checker can also ignore specific Organisations or Student Unions entirely. This feature is possible on request, but only after extensive deliberation with ULYSSIS. Enabling this feature also carries possible consequences: no more mails about outdated software, ever (unless enabled on request), and no support if/when your account gets hacked (the account will be suspended immediately). cc697b7d3cefd439cc442312c05f51c2c71648be 1623 1622 2021-12-01T22:13:55Z Sydon 48 /* Supported Software */ wikitext text/x-wiki ==Introduction== Many of our users use the same popular software. However, as is common in many popular and widespread software, various bug or errors can occur in the program. These flaws can be exploited by hackers to gain access to websites or databases connected. Whenever a new update is released for any other popular software (E.g., Wordpress, MediaWiki, Joomla) hackers will find out which security flaws have been patched, and with this knowledge, they try to find new systems flaws to gain access to the websites or databases. This is the reason why it is so critical to update the software itself, plugins, themes, or any related software as soon as the updates roll out. To help facilitate this and prevent security breaches, we have created a tool to help you keep the most used software up-to-date. Currently, this feature is only active if you have an organization or student union account. ==What to do once you receive an e-mail!== Once you receive an e-mail from the Software Version Checker, it is of upmost importance to update the sofware mentioned in the e-mail. Make sure that you have downloaded the lastest '''public version'''. It is also the best time to check if the other software you use is up-to-date. As mentioned below, our tool does not check all software. You can find more information [[Updating WordPress|here]] on how to automate this for Wordpress to save a lot of time and effort. Since updating MediaWiki can be a somewhat daunting process we have made a more detailed guide accessible on [[Updating MediaWiki]]. ==Supported Software== kan niet alles supporteren etc, hebben populairste gekozen en gekeken welke het vaakste security breaches krijgen. die worden gekozen om te supporten. en die ook GEKUNNEN GESUPPORT WORDEN; *Drupal,(including modules and themes) Drupal Modules, Drupal Themes *Joomla (Plugins are not supported) *MediaWiki (MediaWiki Extensions and Themes are not supported) *PhpBB, PhpBB Plugins, PhpBB Styles *WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the Version Checker does the following: *Scan relevant files, detect supported software, and store in database *Check the version and validity of outdated software *Mail accounts using outdated software ==Stored Data== The following data is stored in the database: *The location of the CMS, plugin/extension or theme *The responsible organisation or student union (kring/facultair overlegorgaan) *The detected software version *The type and name of the software *The update URL for the software *The date the entry was added ==Ignored Paths== The Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. ==Ignored Organisations/Student Unions== In addition to the ignored paths feature, the Version Checker can also ignore specific Organisations or Student Unions entirely. This feature is possible on request, but only after extensive deliberation with ULYSSIS. Enabling this feature also carries possible consequences: no more mails about outdated software, ever (unless enabled on request), and no support if/when your account gets hacked (the account will be suspended immediately). 1a12cf68977571cef47b048f73eab4721af13272 1624 1623 2021-12-01T22:15:07Z Sydon 48 /* What to do once you receive an e-mail! */ wikitext text/x-wiki ==Introduction== Many of our users use the same popular software. However, as is common in many popular and widespread software, various bug or errors can occur in the program. These flaws can be exploited by hackers to gain access to websites or databases connected. Whenever a new update is released for any other popular software (E.g., Wordpress, MediaWiki, Joomla) hackers will find out which security flaws have been patched, and with this knowledge, they try to find new systems flaws to gain access to the websites or databases. This is the reason why it is so critical to update the software itself, plugins, themes, or any related software as soon as the updates roll out. To help facilitate this and prevent security breaches, we have created a tool to help you keep the most used software up-to-date. Currently, this feature is only active if you have an organization or student union account. ==What to do when you receive an e-mail== When you receive an e-mail from the Software Version Checker, it is of upmost importance to update the sofware mentioned in the e-mail. Make sure that you have downloaded the lastest '''public version'''. It is also the best time to check if the other software you use is up-to-date. As mentioned below, our tool does not check all software. You can find more information [[Updating WordPress|here]] on how to automate this for Wordpress to save a lot of time and effort. Since updating MediaWiki can be a somewhat daunting process we have made a more detailed guide accessible on [[Updating MediaWiki]]. ==Supported Software== kan niet alles supporteren etc, hebben populairste gekozen en gekeken welke het vaakste security breaches krijgen. die worden gekozen om te supporten. en die ook GEKUNNEN GESUPPORT WORDEN; *Drupal,(including modules and themes) Drupal Modules, Drupal Themes *Joomla (Plugins are not supported) *MediaWiki (MediaWiki Extensions and Themes are not supported) *PhpBB, PhpBB Plugins, PhpBB Styles *WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the Version Checker does the following: *Scan relevant files, detect supported software, and store in database *Check the version and validity of outdated software *Mail accounts using outdated software ==Stored Data== The following data is stored in the database: *The location of the CMS, plugin/extension or theme *The responsible organisation or student union (kring/facultair overlegorgaan) *The detected software version *The type and name of the software *The update URL for the software *The date the entry was added ==Ignored Paths== The Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. ==Ignored Organisations/Student Unions== In addition to the ignored paths feature, the Version Checker can also ignore specific Organisations or Student Unions entirely. This feature is possible on request, but only after extensive deliberation with ULYSSIS. Enabling this feature also carries possible consequences: no more mails about outdated software, ever (unless enabled on request), and no support if/when your account gets hacked (the account will be suspended immediately). 6e6e3e09a0488a9cb2cacf94ed3a1088749b4315 1625 1624 2021-12-01T22:15:54Z Sydon 48 /* What to do when you receive an e-mail */ wikitext text/x-wiki ==Introduction== Many of our users use the same popular software. However, as is common in many popular and widespread software, various bug or errors can occur in the program. These flaws can be exploited by hackers to gain access to websites or databases connected. Whenever a new update is released for any other popular software (E.g., Wordpress, MediaWiki, Joomla) hackers will find out which security flaws have been patched, and with this knowledge, they try to find new systems flaws to gain access to the websites or databases. This is the reason why it is so critical to update the software itself, plugins, themes, or any related software as soon as the updates roll out. To help facilitate this and prevent security breaches, we have created a tool to help you keep the most used software up-to-date. Currently, this feature is only active if you have an organization or student union account. ==What to do when you receive an e-mail== When you receive an e-mail from the Software Version Checker, it is of upmost importance to update the sofware mentioned in the e-mail. It is also the best time to check if the other software you use is up-to-date. As mentioned below, our tool does not check all software. You can find more information [[Updating WordPress|here]] on how to automate this for Wordpress to save a lot of time and effort. Since updating MediaWiki can be a somewhat daunting process we have made a more detailed guide accessible on [[Updating MediaWiki]]. ==Supported Software== kan niet alles supporteren etc, hebben populairste gekozen en gekeken welke het vaakste security breaches krijgen. die worden gekozen om te supporten. en die ook GEKUNNEN GESUPPORT WORDEN; *Drupal,(including modules and themes) Drupal Modules, Drupal Themes *Joomla (Plugins are not supported) *MediaWiki (MediaWiki Extensions and Themes are not supported) *PhpBB, PhpBB Plugins, PhpBB Styles *WordPress, WordPress Plugins, WordPress Themes ==Operation== In general, the Version Checker does the following: *Scan relevant files, detect supported software, and store in database *Check the version and validity of outdated software *Mail accounts using outdated software ==Stored Data== The following data is stored in the database: *The location of the CMS, plugin/extension or theme *The responsible organisation or student union (kring/facultair overlegorgaan) *The detected software version *The type and name of the software *The update URL for the software *The date the entry was added ==Ignored Paths== The Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. ==Ignored Organisations/Student Unions== In addition to the ignored paths feature, the Version Checker can also ignore specific Organisations or Student Unions entirely. This feature is possible on request, but only after extensive deliberation with ULYSSIS. Enabling this feature also carries possible consequences: no more mails about outdated software, ever (unless enabled on request), and no support if/when your account gets hacked (the account will be suspended immediately). 9e763da174a9adfe0e04cf99d33c90dcc2734a6b 1626 1625 2021-12-01T22:47:48Z Sydon 48 /* What to do when you receive an e-mail */ wikitext text/x-wiki ==Introduction== Many of our users use the same popular software. However, as is common in many popular and widespread software, various bug or errors can occur in the program. These flaws can be exploited by hackers to gain access to websites or databases connected. Whenever a new update is released for any other popular software (E.g., WordPress, MediaWiki, Joomla) hackers will find out which security flaws have been patched, and with this knowledge, they try to find new systems flaws to gain access to the websites or databases. This is the reason why it is so critical to update the software itself, plugins, themes, or any related software as soon as the updates roll out. To help facilitate this and prevent security breaches, we have created a tool to help you keep the most used software up-to-date. Currently, this feature is only active if you have an organization or student union account. ==What to do when you receive an e-mail== When you receive an e-mail from the Software Version Checker, it is of upmost importance to update the software mentioned in the e-mail. It is a good habit to make sure the software you use is up-to-date It is also the best time to check if the other software you use is up-to-date. As mentioned below, our tool does not check all software. You can find more information [[Updating WordPress|here]] on how to automate this for WordPress to save a lot of time and effort. Since updating MediaWiki can be a somewhat daunting process, we have made a more detailed guide available on [[Updating MediaWiki]]. ==Supported Software== Sadly enough we cannot support every program, because of this we have picked the most popular software. Because of the popularity of the various software they are more likely to get security breaches. Sadly enough not every piece of software can be supported. *Drupal (including modules and themes) *Joomla (Plugins are not supported) *MediaWiki (MediaWiki Extensions and Themes are not supported) *phpBB (including plugins and styles) *WordPress(including plugins and themes) ==Operation== In general, the Version Checker does the following: *Scan relevant files, detect supported software, and store in database *Check the version and validity of outdated software *Mail accounts using outdated software ==Stored Data== The following data is stored in the database: *The location of the CMS, plugin/extension or theme *The responsible organisation or student union (kring/facultair overlegorgaan) *The detected software version *The type and name of the software *The update URL for the software *The date the entry was added ==Ignored Paths== The Version Checker has a feature allowing ULYSSIS members to specify paths that will not be searched for software. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. ==Ignored Organisations/Student Unions== In addition to the ignored paths feature, the Version Checker can also ignore specific Organisations or Student Unions entirely. This feature is possible on request, but only after extensive deliberation with ULYSSIS. Enabling this feature also carries possible consequences: no more mails about outdated software, ever (unless enabled on request), and no support if/when your account gets hacked (the account will be suspended immediately). f975d98ff313d8004553c77007a9c45c3d8f91b1 6 212 1599 1584 2021-12-01T13:35:17Z Debber 46 Debber uploaded a new version of [[File:First Open TB.png]] wikitext text/x-wiki This is a screenshot of the interface to add a mailbox ca5318ccf366a99b6b714ac9efc2b3470c459c20 6 213 1600 1585 2021-12-01T14:34:40Z Debber 46 Debber uploaded a new version of [[File:New Mailbox.png]] wikitext text/x-wiki Highlighted in blue, is the button to add another mailbox 58953a78e25cbbec125bbe7162cb1574b3206b14 6 214 1601 1586 2021-12-01T14:35:31Z Debber 46 Debber uploaded a new version of [[File:Fill in email.png]] wikitext text/x-wiki The email address has been filled in. 7ecc4f3aae50c533e80a56bdbe1c4bdb292e58c2 1608 1601 2021-12-01T19:28:02Z Debber 46 Debber uploaded a new version of [[File:Fill in email.png]] wikitext text/x-wiki The email address has been filled in. 7ecc4f3aae50c533e80a56bdbe1c4bdb292e58c2 6 215 1602 1587 2021-12-01T14:36:04Z Debber 46 Debber uploaded a new version of [[File:Click Configure Manually.png]] wikitext text/x-wiki This is how the popup should look with the manual settings 1cb5825962e1a478efa9f598d5b3b5bee34187ee 1609 1602 2021-12-01T19:28:49Z Debber 46 Debber uploaded a new version of [[File:Click Configure Manually.png]] wikitext text/x-wiki This is how the popup should look with the manual settings 1cb5825962e1a478efa9f598d5b3b5bee34187ee 6 216 1603 1588 2021-12-01T14:36:35Z Debber 46 Debber uploaded a new version of [[File:Fill advanced.png]] wikitext text/x-wiki The right way to fill in the advanced settings 7479e667dc86ac972988f8a11d485bbc51fc2fa3 1610 1603 2021-12-01T19:29:24Z Debber 46 Debber uploaded a new version of [[File:Fill advanced.png]] wikitext text/x-wiki The right way to fill in the advanced settings 7479e667dc86ac972988f8a11d485bbc51fc2fa3 6 217 1604 1589 2021-12-01T14:36:57Z Debber 46 Debber uploaded a new version of [[File:After Clicking Retest GOOD.png]] wikitext text/x-wiki The popup after clicking retest 278ff2db283e7dda3022ad82a2c73468ed5c60e3 1611 1604 2021-12-01T19:30:00Z Debber 46 Debber uploaded a new version of [[File:After Clicking Retest GOOD.png]] wikitext text/x-wiki The popup after clicking retest 278ff2db283e7dda3022ad82a2c73468ed5c60e3 6 219 1605 1591 2021-12-01T14:37:25Z Debber 46 Debber uploaded a new version of [[File:After Clicking GetMessages.png]] wikitext text/x-wiki Full mailbox 0458177d29c41db26f17cf250a931973edc47c65 1637 1605 2021-12-02T20:44:37Z Debber 46 Debber uploaded a new version of [[File:After Clicking GetMessages.png]] wikitext text/x-wiki Full mailbox 0458177d29c41db26f17cf250a931973edc47c65 0 220 1646 1645 2021-12-02T21:49:27Z Bert 8 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to create your very own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it is possible to fill in the login details for a mailbox. The first step is to fill in your name, email address and password (this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Next, the button "Configure manually..." on the bottom left will have become clickable (as seen on the screenshot above). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- ! ! style="padding-right: 10px;" ! INCOMING !! OUTGOING |- || Protocol: || IMAP || SMTP |- || Server: || mail.ulyssis.org || smtps.kuleuven.be |- || Port: || 993 || 443 |- || SSL: || SSL/TLS || SSL/TLS |- || Authentication: || Autodetect || Autodetect |- || Username: || ULYSSIS username || r/m/s/u number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up will close when the "Done" button has been clicked. After the pop-up closes, a mailbox should be added to the left sidebar of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent. [[Category:Mail]] c0eb60fc38b10918329af1655357c3af929c8f2b 1647 1646 2021-12-02T21:50:09Z Bert 8 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to create your very own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it is possible to fill in the login details for a mailbox. The first step is to fill in your name, email address and password (this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Next, the button "Configure manually..." on the bottom left will have become clickable (as seen on the screenshot above). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- ! ! style="padding-right: 10px;" | INCOMING !! OUTGOING |- || Protocol: || IMAP || SMTP |- || Server: || mail.ulyssis.org || smtps.kuleuven.be |- || Port: || 993 || 443 |- || SSL: || SSL/TLS || SSL/TLS |- || Authentication: || Autodetect || Autodetect |- || Username: || ULYSSIS username || r/m/s/u number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up will close when the "Done" button has been clicked. After the pop-up closes, a mailbox should be added to the left sidebar of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent. [[Category:Mail]] 7f674a50bcde7c751209c957663a6576feb01a75 1648 1647 2021-12-02T21:50:30Z Bert 8 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to create your very own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it is possible to fill in the login details for a mailbox. The first step is to fill in your name, email address and password (this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Next, the button "Configure manually..." on the bottom left will have become clickable (as seen on the screenshot above). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- || Protocol: || IMAP || SMTP |- || Server: || mail.ulyssis.org || smtps.kuleuven.be |- || Port: || 993 || 443 |- || SSL: || SSL/TLS || SSL/TLS |- || Authentication: || Autodetect || Autodetect |- || Username: || ULYSSIS username || r/m/s/u number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up will close when the "Done" button has been clicked. After the pop-up closes, a mailbox should be added to the left sidebar of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent. [[Category:Mail]] 1ba22d93d5f4c1bcd6684c3d0821955a86766704 1649 1648 2021-12-02T21:50:55Z Bert 8 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to create your very own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it is possible to fill in the login details for a mailbox. The first step is to fill in your name, email address and password (this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Next, the button "Configure manually..." on the bottom left will have become clickable (as seen on the screenshot above). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- ! !! INCOMING !! OUTGOING |- || Protocol: || IMAP || SMTP |- || Server: || mail.ulyssis.org || smtps.kuleuven.be |- || Port: || 993 || 443 |- || SSL: || SSL/TLS || SSL/TLS |- || Authentication: || Autodetect || Autodetect |- || Username: || ULYSSIS username || r/m/s/u number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up will close when the "Done" button has been clicked. After the pop-up closes, a mailbox should be added to the left sidebar of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent. [[Category:Mail]] 3ff2d0a5b3a6cc4a8ec5f12d2bfd1778f33f5f3d 1650 1649 2021-12-02T21:51:28Z Bert 8 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to create your very own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it is possible to fill in the login details for a mailbox. The first step is to fill in your name, email address and password (this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Next, the button "Configure manually..." on the bottom left will have become clickable (as seen on the screenshot above). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- || | style="color:red" | INCOMING || OUTGOING |- || Protocol: || IMAP || SMTP |- || Server: || mail.ulyssis.org || smtps.kuleuven.be |- || Port: || 993 || 443 |- || SSL: || SSL/TLS || SSL/TLS |- || Authentication: || Autodetect || Autodetect |- || Username: || ULYSSIS username || r/m/s/u number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up will close when the "Done" button has been clicked. After the pop-up closes, a mailbox should be added to the left sidebar of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent. [[Category:Mail]] 288c282fcec523eef689252ea4493309f2524529 1651 1650 2021-12-02T21:52:02Z Bert 8 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to create your very own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it is possible to fill in the login details for a mailbox. The first step is to fill in your name, email address and password (this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Next, the button "Configure manually..." on the bottom left will have become clickable (as seen on the screenshot above). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- || bla | style="color:red" | INCOMING || OUTGOING |- || Protocol: || IMAP || SMTP |- || Server: || mail.ulyssis.org || smtps.kuleuven.be |- || Port: || 993 || 443 |- || SSL: || SSL/TLS || SSL/TLS |- || Authentication: || Autodetect || Autodetect |- || Username: || ULYSSIS username || r/m/s/u number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up will close when the "Done" button has been clicked. After the pop-up closes, a mailbox should be added to the left sidebar of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent. [[Category:Mail]] dac1d5b7ee3082e6c93ef41ee7ea1bbd8bbace1c 1652 1651 2021-12-02T21:52:14Z Bert 8 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to create your very own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it is possible to fill in the login details for a mailbox. The first step is to fill in your name, email address and password (this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Next, the button "Configure manually..." on the bottom left will have become clickable (as seen on the screenshot above). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- || | style="color:red" | INCOMING || OUTGOING |- || Protocol: || IMAP || SMTP |- || Server: || mail.ulyssis.org || smtps.kuleuven.be |- || Port: || 993 || 443 |- || SSL: || SSL/TLS || SSL/TLS |- || Authentication: || Autodetect || Autodetect |- || Username: || ULYSSIS username || r/m/s/u number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up will close when the "Done" button has been clicked. After the pop-up closes, a mailbox should be added to the left sidebar of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent. [[Category:Mail]] 5b230b84ec36799f1d456aa62e8d4c04183952b3 1653 1652 2021-12-02T21:52:39Z Bert 8 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to create your very own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it is possible to fill in the login details for a mailbox. The first step is to fill in your name, email address and password (this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Next, the button "Configure manually..." on the bottom left will have become clickable (as seen on the screenshot above). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- || | style="padding-right: 20px" | INCOMING || OUTGOING |- || Protocol: || IMAP || SMTP |- || Server: || mail.ulyssis.org || smtps.kuleuven.be |- || Port: || 993 || 443 |- || SSL: || SSL/TLS || SSL/TLS |- || Authentication: || Autodetect || Autodetect |- || Username: || ULYSSIS username || r/m/s/u number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up will close when the "Done" button has been clicked. After the pop-up closes, a mailbox should be added to the left sidebar of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent. [[Category:Mail]] e50ddccfe9f474562aa6f49d068aa990f7c9ace9 1654 1653 2021-12-02T21:53:08Z Bert 8 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to create your very own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it is possible to fill in the login details for a mailbox. The first step is to fill in your name, email address and password (this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Next, the button "Configure manually..." on the bottom left will have become clickable (as seen on the screenshot above). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- || | style="padding-right: 20px" | INCOMING || OUTGOING |- || Protocol: || IMAP || SMTP |- || Server: || mail.ulyssis.org || smtps.kuleuven.be |- || Port: || 993 || 443 |- || SSL: || SSL/TLS || SSL/TLS |- || Authentication: || Autodetect || Autodetect |- || Username: | style="padding-right: 20px" | ULYSSIS username || r/m/s/u number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up will close when the "Done" button has been clicked. After the pop-up closes, a mailbox should be added to the left sidebar of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent. [[Category:Mail]] 1fab3507be2b9d8325b22a55cb1287c68a03e693 1655 1654 2021-12-02T21:53:24Z Bert 8 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to create your very own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it is possible to fill in the login details for a mailbox. The first step is to fill in your name, email address and password (this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Next, the button "Configure manually..." on the bottom left will have become clickable (as seen on the screenshot above). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- || || INCOMING || OUTGOING |- || Protocol: || IMAP || SMTP |- || Server: || mail.ulyssis.org || smtps.kuleuven.be |- || Port: || 993 || 443 |- || SSL: || SSL/TLS || SSL/TLS |- || Authentication: || Autodetect || Autodetect |- || Username: | style="padding-right: 20px" | ULYSSIS username || r/m/s/u number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up will close when the "Done" button has been clicked. After the pop-up closes, a mailbox should be added to the left sidebar of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent. [[Category:Mail]] 97d70e21e2beed695ed727944827f2d5eb64bf06 1656 1655 2021-12-02T21:53:44Z Bert 8 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to create your very own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it is possible to fill in the login details for a mailbox. The first step is to fill in your name, email address and password (this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Next, the button "Configure manually..." on the bottom left will have become clickable (as seen on the screenshot above). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- || || INCOMING || OUTGOING |- || Protocol: || IMAP || SMTP |- || Server: || mail.ulyssis.org || smtps.kuleuven.be |- || Port: || 993 || 443 |- || SSL: || SSL/TLS || SSL/TLS |- || Authentication: || Autodetect || Autodetect |- | style="padding-right: 10px" | Username: | style="padding-right: 10px" | ULYSSIS username || r/m/s/u number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up will close when the "Done" button has been clicked. After the pop-up closes, a mailbox should be added to the left sidebar of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent. [[Category:Mail]] bba68c66aefb30b99abc0efc048123e58a30bbe0 1657 1656 2021-12-02T21:54:06Z Bert 8 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to create your very own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it is possible to fill in the login details for a mailbox. The first step is to fill in your name, email address and password (this email adress should be the username@ulyssis.org adress linked to a mailbox): {{notice|notice|the ULYSSIS username is the username which was picked when the ULYSSIS account was created. For more information please see: https://docs.ulyssis.org/Registering_a_new_account}} [[File:Fill in email.png|left|alt=|thumb|432x432px]] Next, the button "Configure manually..." on the bottom left will have become clickable (as seen on the screenshot above). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- || || INCOMING || OUTGOING |- || Protocol: || IMAP || SMTP |- || Server: || mail.ulyssis.org || smtps.kuleuven.be |- || Port: || 993 || 443 |- || SSL: || SSL/TLS || SSL/TLS |- | style="padding-right: 10px" | Authentication: || Autodetect || Autodetect |- || Username: | style="padding-right: 10px" | ULYSSIS username || r/m/s/u number |} {{notice|notice|The ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down.}} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up will close when the "Done" button has been clicked. After the pop-up closes, a mailbox should be added to the left sidebar of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent. [[Category:Mail]] 9a9a0a0f4b59c4d2ccdedb689c0ace8e0473fe7f 1658 1657 2021-12-03T07:28:55Z Debber 46 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to create your very own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it is possible to fill in the login details for a mailbox. The first step is to fill in your name, email address and password (this email adress should be the username@ulyssis.org adress linked to a mailbox): [[File:Fill in email.png|left|alt=|thumb|432x432px]] Next, the button "Configure manually..." on the bottom left will have become clickable (as seen on the screenshot above). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- || || INCOMING || OUTGOING |- || Protocol: || IMAP || SMTP |- || Server: || mail.ulyssis.org || smtps.kuleuven.be |- || Port: || 993 || 443 |- || SSL: || SSL/TLS || SSL/TLS |- | style="padding-right: 10px" | Authentication: || Autodetect || Autodetect |- || Username: | style="padding-right: 10px" | ULYSSIS username || r/m/s/u number |} Notice the ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down. The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up will close when the "Done" button has been clicked. After the pop-up closes, a mailbox should be added to the left sidebar of the main Thunderbird window. By clicking on the inbox tab, the emails should load in (as seen in the last screenshot). After this first setup, the mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent. [[Category:Mail]] 351da2ad52e26febebac1c7bc67b6f50b2d1715f 1659 1658 2021-12-03T12:03:19Z Debber 46 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to use it as your own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it is possible to fill in the login details for your mailbox. The first step is to fill in your name, email address and password (this email adress should be your ULYSSIS username followed by @ulyssis.org): [[File:Fill in email.png|left|alt=|thumb|432x432px]] Next, the button "Configure manually..." on the bottom left will become clickable (as seen on the screenshot above). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- || || INCOMING || OUTGOING |- || Protocol: || IMAP || SMTP |- || Server: || mail.ulyssis.org || smtps.kuleuven.be |- || Port: || 993 || 443 |- || SSL: || SSL/TLS || SSL/TLS |- | style="padding-right: 10px" | Authentication: || Autodetect || Autodetect |- || Username: | style="padding-right: 10px" | ULYSSIS username || r/m/s/u number |} Notice the ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down. The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up will close when the "Done" button has been clicked. After the pop-up closes, a mailbox should be added to the left sidebar of the main Thunderbird window. By clicking on the inbox tab, your emails should start showing up (as seen in the last screenshot). After finishing up this setup, your mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent. [[Category:Mail]] 35cc6b870a9eabb9972af98db6b16bd85bc1a99b 1660 1659 2021-12-03T12:04:26Z Debber 46 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to use it as your own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not come up, or this is not your first mailbox; it is possible to click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, it is possible to fill in the login details for your mailbox. The first step is to fill in your name, email address and password (this email adress should be your ULYSSIS username followed by @ulyssis.org): [[File:Fill in email.png|left|alt=|thumb|432x432px]] Next, the button "Configure manually..." on the bottom left will become clickable (as seen on the screenshot above). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- || || INCOMING || OUTGOING |- || Protocol: || IMAP || SMTP |- || Server: || mail.ulyssis.org || smtps.kuleuven.be |- || Port: || 993 || 443 |- || SSL: || SSL/TLS || SSL/TLS |- | style="padding-right: 10px" | Authentication: || Autodetect || Autodetect |- || Username: | style="padding-right: 10px" | ULYSSIS username || r/m/s/u number |- | colspan="3" | Notice the ports used to configure a ULYSSIS mailbox, are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down. |} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up will close when the "Done" button has been clicked. After the pop-up closes, a mailbox should be added to the left sidebar of the main Thunderbird window. By clicking on the inbox tab, your emails should start showing up (as seen in the last screenshot). After finishing up this setup, your mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent. [[Category:Mail]] 2723b81d102857ba89f23df50b679d6cd14b5b49 1662 1660 2021-12-03T17:27:52Z Pcy 37 spelling tweaks etc wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to use it as your own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not appear, or this is not your first mailbox; click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, proceed by entering the login details for your mailbox. The first step is to fill in your name, email address and password (this email adress should be your ULYSSIS username followed by <code>@ulyssis.org</code>): [[File:Fill in email.png|left|alt=|thumb|432x432px]] Next, the button "Configure manually..." on the bottom left will become clickable (as seen on the screenshot above). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- || || INCOMING || OUTGOING |- || Protocol: || IMAP || SMTP |- || Server: || mail.ulyssis.org || smtps.kuleuven.be |- || Port: || 993 || 443 |- || SSL: || SSL/TLS || SSL/TLS |- | style="padding-right: 10px" | Authentication: || Autodetect || Autodetect |- || Username: | style="padding-right: 10px" | ULYSSIS username || r/m/s/u number |- | colspan="3" | Notice the ports used to configure a ULYSSIS mailbox are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down. |} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, Thunderbird will try to connect to the mail server. When successful, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up will close when the "Done" button has been clicked. After the pop-up closes, a mailbox should be added to the left sidebar of the main Thunderbird window. By clicking on the inbox tab, your emails should start showing up (as seen in the last screenshot). After finishing up this setup, your mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent. [[Category:Mail]] 8abf0906e9046bb1097aacaf3061993acccb27b1 1663 1662 2021-12-03T17:31:00Z Pcy 37 /* Adding a ULYSSIS mailbox to Thunderbird */ wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to use it as your own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not appear, or this is not your first mailbox; click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, proceed by entering the login details for your mailbox. The first step is to fill in your name, email address and password (this email adress should be your ULYSSIS username followed by <code>@ulyssis.org</code>): [[File:Fill in email.png|left|alt=|thumb|432x432px]] Next, the button "Configure manually..." on the bottom left will become clickable (as seen on the screenshot above). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- || || INCOMING || OUTGOING |- || Protocol: || IMAP || SMTP |- || Server: || mail.ulyssis.org || smtps.kuleuven.be |- || Port: || 993 || 443 |- || SSL: || SSL/TLS || SSL/TLS |- | style="padding-right: 10px" | Authentication: || Autodetect || Autodetect |- || Username: | style="padding-right: 10px" | ULYSSIS username || r/m/s/u number |- | colspan="3" | Notice the ports used to configure a ULYSSIS mailbox are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down. |} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, Thunderbird will try to connect to the mail server. When successful, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up will close when the "Done" button has been clicked. After the pop-up closes, a mailbox should be added to the left sidebar of the main Thunderbird window. By clicking on the inbox tab, your emails should start showing up (as seen in the last screenshot). After finishing up this setup, your mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] {{notice|Use your KU Leuven login for the outgoing (SMTP) mailserver|When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent.}} [[Category:Mail]] 90e6239662148f15288eebd0e45803488f879a7f 1664 1663 2021-12-04T18:34:48Z Vincenttc 21 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to use it as your own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not appear, or this is not your first mailbox; click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, proceed by entering the login details for your mailbox. The first step is to fill in your name, email address and password (this email address should be your ULYSSIS username followed by <code>@ulyssis.org</code>): [[File:Fill in email.png|left|alt=|thumb|432x432px]] Next, the button "Configure manually..." on the bottom left will become clickable (as seen on the screenshot above). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- || || INCOMING || OUTGOING |- || Protocol: || IMAP || SMTP |- || Server: || mail.ulyssis.org || smtps.kuleuven.be |- || Port: || 993 || 443 |- || SSL: || SSL/TLS || SSL/TLS |- | style="padding-right: 10px" | Authentication: || Autodetect || Autodetect |- || Username: | style="padding-right: 10px" | ULYSSIS username || r/m/s/u number |- | colspan="3" | Notice the ports used to configure a ULYSSIS mailbox are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down. |} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, Thunderbird will try to connect to the mail server. When successful, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up will close when the "Done" button has been clicked. After the pop-up closes, a mailbox should be added to the left sidebar of the main Thunderbird window. By clicking on the inbox tab, your emails should start showing up (as seen in the last screenshot). After finishing up this setup, your mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] {{notice|Use your KU Leuven login for the outgoing (SMTP) mailserver|When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent.}} [[Category:Mail]] c0661998594a0fbe4077798ad83db80d0ee09e27 1666 1664 2021-12-09T19:22:14Z Debber 46 wikitext text/x-wiki When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to use it as your own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not appear, or this is not your first mailbox; click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, proceed by entering the login details for your mailbox. The first step is to fill in your name, email address and password (this email address should be your ULYSSIS username followed by <code>@ulyssis.org</code>): [[File:Fill in email.png|left|alt=|thumb|432x432px]] Next, the button "Configure manually..." on the bottom left will become clickable (as seen on the screenshot above). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- || || INCOMING || OUTGOING |- || Protocol: || IMAP || SMTP |- || Server: || mail.ulyssis.org || smtps.kuleuven.be |- || Port: || 993 || 443 |- || SSL: || SSL/TLS || SSL/TLS |- | style="padding-right: 10px" | Authentication: || Autodetect || Autodetect |- || Username: | style="padding-right: 10px" | ULYSSIS username || r/m/s/u number |- | colspan="3" | Notice the ports used to configure a ULYSSIS mailbox are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down. |} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, Thunderbird will try to connect to the mail server. When successful, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up will close when the "Done" button has been clicked. After the pop-up closes, a mailbox should be added to the left sidebar of the main Thunderbird window. By clicking on the inbox tab, your emails should start showing up (as seen in the last screenshot). After finishing up this setup, your mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent. [[Category:Mail]] 64b84b024f80b835205b860302325f7bb7cc3688 0 3 1661 1562 2021-12-03T12:05:37Z Debber 46 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Reducing disk usage|Help, my account uses too much disk space]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Making Backups]] * [[Secure file permissions]] * [[Reducing disk usage]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2020]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Sending email from websites]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL/TLS|Getting SSL/TLS (HTTPS security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Claiming a port]] * [[ULYSSIS security measures]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] * [[Spam]] * [[ULYSSIS security measures]] * [[Mailbox in Thunderbird]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up WordPress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] * [[Updating WordPress]] * [[Updating MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] * [[Using PHPPgAdmin]] * [[Using Adminer]] * [[Making Backups]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[Exporting your KU Leuven class schedule and calendar]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 735244e07560b23288755d2e4b8a4016f717cc63 1667 1661 2021-12-16T10:55:09Z Bert 8 /* Mail */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Reducing disk usage|Help, my account uses too much disk space]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Making Backups]] * [[Secure file permissions]] * [[Reducing disk usage]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2020]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Sending email from websites]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL/TLS|Getting SSL/TLS (HTTPS security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Claiming a port]] * [[ULYSSIS security measures]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Mailbox in Thunderbird]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Fetch your KU Leuven email into another email address]] * [[Spam]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up WordPress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] * [[Updating WordPress]] * [[Updating MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] * [[Using PHPPgAdmin]] * [[Using Adminer]] * [[Making Backups]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[Exporting your KU Leuven class schedule and calendar]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 8d896567fa07891bcdb878788acc3e239e558168 0 221 1665 1626 2021-12-05T20:59:12Z Sydon 48 /* Supported Software */ wikitext text/x-wiki ==Introduction== Many of our users use the same popular software. However, as is common in many popular and widespread software, various bug or errors can occur in the program. These flaws can be exploited by hackers to gain access to websites or databases connected. Whenever a new update is released for any other popular software (E.g., WordPress, MediaWiki, Joomla) hackers will find out which security flaws have been patched, and with this knowledge, they try to find new systems flaws to gain access to the websites or databases. This is the reason why it is so critical to update the software itself, plugins, themes, or any related software as soon as the updates roll out. To help facilitate this and prevent security breaches, we have created a tool, the Software Version Checker, to help you keep the most used software up-to-date. Currently, this feature is only active if you have an organization or student union account. ==What to do when you receive an e-mail== When you receive an e-mail from the Software Version Checker, it is of upmost importance to update the software mentioned in the e-mail. It is a good habit to make sure the software you use is up-to-date It is also the best time to check if the other software you use is up-to-date. As mentioned below, our tool does not check all software. You can find more information [[Updating WordPress|here]] on how to automate this for WordPress to save a lot of time and effort. Since updating MediaWiki can be a somewhat daunting process, we have made a more detailed guide available on [[Updating MediaWiki]]. ==Supported Software== Sadly enough not every piece of software can be supported. Because of this we have decided to choose the most popular software, since they are more likely to get security breaches. *Drupal (including modules and themes) *Joomla (Plugins are not supported) *MediaWiki (MediaWiki Extensions and Themes are not supported) *phpBB (including plugins and styles) *WordPress(including plugins and themes) ==Functionality of the Software Version Checker== The Software Version Checker fulfills the following functions: *Scan relevant files, detect supported software, and store in database *Check the version and validity of outdated software *Notify accounts that are using outdated software ==Stored Data in the database== The following data is stored in the database: *The location of the Software Version Checker, the plugins, extensions and themes *The responsible organisation or student union *The software version *The details of the software *The update URL for the software *The date the entry was added ==Ignoring specific software== The Software Version Checker has a feature that allows to specify paths that the Software Version Checker will not search. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. ==Ignoring Organisations/Student Unions== The Software Version Checker also allows our users to ignore specific Organisations or Student Unions entirely. This feature is possible on request, but only after extensive deliberation with ULYSSIS. Enabling this feature also has possible consequences; no more mails about software that is outdated, unless it is enabled on request, and no possible support if the users account gets hacked. If the account does get hacked it will be suspend immediately. c44878c9a931df54ebee253d680361d12fc00490 1669 1665 2021-12-18T16:22:23Z Sydon 48 /* Introduction */ wikitext text/x-wiki ==Introduction== Many of our users use the same popular software. However, as is common in popular and widespread software, various bugs or errors can occur in the program. These flaws can be exploited by hackers to gain access to websites or databases. Whenever a new update is released for any popular software (E.g., WordPress, MediaWiki, Joomla) hackers will find out which security flaws have been patched, and with this knowledge, they try to find new systems flaws to gain access to the websites or databases. This is the reason why it is so critical to update the software itself, plugins, themes, or any related software as soon as the updates roll out. To help facilitate this and prevent security breaches, we have created a tool, the Software Version Checker, to help you keep the most commonly used software up-to-date. Currently, this feature is only active if you have an organization or student union account. ==What to do when you receive an e-mail== When you receive an e-mail from the Software Version Checker, it is of utmost importance to update the software mentioned in the e-mail. I It is also the best time to check if the other software you use is up-to-date. As mentioned below, our tool does not check all software. You can find more information [[Updating WordPress|here]] on how to automate this for WordPress to save a lot of time and effort. Since updating MediaWiki can be a somewhat daunting process, we have made a more detailed guide available on [[Updating MediaWiki]]. ==Supported Software== Sadly not every piece of software can be supported. Because of this, we have decided to choose the most popular software, since they are more likely to get security breaches. *Drupal (including modules and themes) *Joomla (Plugins are not supported) *MediaWiki (MediaWiki Extensions and Themes are not supported) *phpBB (including plugins and styles) *WordPress(including plugins and themes) ==Functionality of the Software Version Checker== The Software Version Checker fulfills the following functions: *Scan relevant files, detect supported software, and store in database *Check the version and validity of outdated software *Notify accounts that are using outdated software ==Stored Data in the database== The following data is stored in the database: *The location of the Software Version Checker, the plugins, extensions and themes *The responsible organisation or student union *The software version *The details of the software *The update URL for the software *The date the entry was added ==Ignoring specific software== The Software Version Checker has a feature that allows to specify paths that the Software Version Checker will not search. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. ==Ignoring Organisations/Student Unions== The Software Version Checker also allows our users to ignore specific Organisations or Student Unions entirely. This feature is possible on request, but only after extensive deliberation with ULYSSIS. Enabling this feature also has possible consequences; no more mails about software that is outdated, unless it is enabled on request, and no possible support if the user's account gets hacked. If the account does get hacked it will be suspend immediately. f5c2eb11b3767fea347ed3c75d83f693548ef1ab 1670 1669 2021-12-18T16:24:31Z Sydon 48 /* Introduction */ wikitext text/x-wiki ==Introduction== Many of our users use the same popular software. However, as is common in popular and widespread software, various bugs or errors can occur in the program. These flaws can be exploited by hackers to gain access to websites or databases. Whenever a new update is released for any popular software (e.g., WordPress, MediaWiki, Joomla) hackers will find out which security flaws have been patched, and with this knowledge, they try to find new systems flaws to gain access to the websites or databases. This is the reason why it is so critical to update the software itself, plugins, themes, or any related software as soon as the updates roll out. To help facilitate this and prevent security breaches, we have created a tool, the Software Version Checker, to help you keep the most commonly used software up-to-date. Currently, this feature is only active if you have an organization or student union account. ==What to do when you receive an e-mail== When you receive an e-mail from the Software Version Checker, it is of utmost importance to update the software mentioned in the e-mail. I It is also the best time to check if the other software you use is up-to-date. As mentioned below, our tool does not check all software. You can find more information [[Updating WordPress|here]] on how to automate this for WordPress to save a lot of time and effort. Since updating MediaWiki can be a somewhat daunting process, we have made a more detailed guide available on [[Updating MediaWiki]]. ==Supported Software== Sadly not every piece of software can be supported. Because of this, we have decided to choose the most popular software, since they are more likely to get security breaches. *Drupal (including modules and themes) *Joomla (Plugins are not supported) *MediaWiki (MediaWiki Extensions and Themes are not supported) *phpBB (including plugins and styles) *WordPress(including plugins and themes) ==Functionality of the Software Version Checker== The Software Version Checker fulfills the following functions: *Scan relevant files, detect supported software, and store in database *Check the version and validity of outdated software *Notify accounts that are using outdated software ==Stored Data in the database== The following data is stored in the database: *The location of the Software Version Checker, the plugins, extensions and themes *The responsible organisation or student union *The software version *The details of the software *The update URL for the software *The date the entry was added ==Ignoring specific software== The Software Version Checker has a feature that allows to specify paths that the Software Version Checker will not search. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. ==Ignoring Organisations/Student Unions== The Software Version Checker also allows our users to ignore specific Organisations or Student Unions entirely. This feature is possible on request, but only after extensive deliberation with ULYSSIS. Enabling this feature also has possible consequences; no more mails about software that is outdated, unless it is enabled on request, and no possible support if the user's account gets hacked. If the account does get hacked it will be suspend immediately. d9992b999227127c7b79c4f29dd45b34260f29e1 1671 1670 2021-12-18T16:29:07Z Sydon 48 /* Introduction */ wikitext text/x-wiki ==Introduction== Many of our users use the same popular software. However, as is common in popular and widespread software, various bugs or errors can occur in the program. These flaws can be exploited by hackers to gain access to websites or databases. Whenever a new update is released for any popular software (e.g., WordPress, MediaWiki, Joomla) hackers will find out which security flaws have been patched, and using this knowledge, they try to find new systems flaws to gain access to the websites or databases. This is the reason why it is so critical to update the software itself, plugins, themes, or any related software as soon as the updates roll out. To help facilitate this and prevent security breaches, we have created a tool, the Software Version Checker, to help you keep the most commonly used software up-to-date. Currently, this feature is only active if you have an organization or student union account. ==What to do when you receive an e-mail== When you receive an e-mail from the Software Version Checker, it is of utmost importance to update the software mentioned in the e-mail. I It is also the best time to check if the other software you use is up-to-date. As mentioned below, our tool does not check all software. You can find more information [[Updating WordPress|here]] on how to automate this for WordPress to save a lot of time and effort. Since updating MediaWiki can be a somewhat daunting process, we have made a more detailed guide available on [[Updating MediaWiki]]. ==Supported Software== Sadly not every piece of software can be supported. Because of this, we have decided to choose the most popular software, since they are more likely to get security breaches. *Drupal (including modules and themes) *Joomla (Plugins are not supported) *MediaWiki (MediaWiki Extensions and Themes are not supported) *phpBB (including plugins and styles) *WordPress(including plugins and themes) ==Functionality of the Software Version Checker== The Software Version Checker fulfills the following functions: *Scan relevant files, detect supported software, and store in database *Check the version and validity of outdated software *Notify accounts that are using outdated software ==Stored Data in the database== The following data is stored in the database: *The location of the Software Version Checker, the plugins, extensions and themes *The responsible organisation or student union *The software version *The details of the software *The update URL for the software *The date the entry was added ==Ignoring specific software== The Software Version Checker has a feature that allows to specify paths that the Software Version Checker will not search. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. ==Ignoring Organisations/Student Unions== The Software Version Checker also allows our users to ignore specific Organisations or Student Unions entirely. This feature is possible on request, but only after extensive deliberation with ULYSSIS. Enabling this feature also has possible consequences; no more mails about software that is outdated, unless it is enabled on request, and no possible support if the user's account gets hacked. If the account does get hacked it will be suspend immediately. 5fa9b15de4e1372b5a398aaca1cb04f0c73313a8 1672 1671 2021-12-18T19:16:49Z Pcy 37 fix silly typos wikitext text/x-wiki ==Introduction== Many of our users use the same popular software. However, as is common in popular and widespread software, various bugs or errors can occur in the program. These flaws can be exploited by hackers to gain access to websites or databases. Whenever a new update is released for any popular software (e.g., WordPress, MediaWiki, Joomla) hackers will find out which security flaws have been patched, and using this knowledge, they try to find new systems flaws to gain access to the websites or databases. This is the reason why it is so critical to update the software itself, plugins, themes, or any related software as soon as the updates roll out. To help facilitate this and prevent security breaches, we have created a tool, the Software Version Checker, to help you keep the most commonly used software up-to-date. Currently, this feature is only active if you have an organization or student union account. ==What to do when you receive an e-mail== When you receive an e-mail from the Software Version Checker, it is of utmost importance to update the software mentioned in the e-mail. It is also the best time to check if the other software you use is up-to-date. As mentioned below, our tool does not check all software. You can find more information [[Updating WordPress|here]] on how to automate this for WordPress to save a lot of time and effort. Since updating MediaWiki can be a somewhat daunting process, we have made a more detailed guide available on [[Updating MediaWiki]]. ==Supported Software== Sadly not every piece of software can be supported. Because of this, we have decided to choose the most popular software, since they are more likely to get security breaches. *Drupal (including modules and themes) *Joomla (Plugins are not supported) *MediaWiki (MediaWiki Extensions and Themes are not supported) *phpBB (including plugins and styles) *WordPress (including plugins and themes) ==Functionality of the Software Version Checker== The Software Version Checker fulfills the following functions: *Scan relevant files, detect supported software, and store in database *Check the version and validity of outdated software *Notify accounts that are using outdated software ==Stored Data in the database== The following data is stored in the database: *The location of the Software Version Checker, the plugins, extensions and themes *The responsible organisation or student union *The software version *The details of the software *The update URL for the software *The date the entry was added ==Ignoring specific software== The Software Version Checker has a feature that allows to specify paths that the Software Version Checker will not search. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. ==Ignoring Organisations/Student Unions== The Software Version Checker also allows our users to ignore specific Organisations or Student Unions entirely. This feature is possible on request, but only after extensive deliberation with ULYSSIS. Enabling this feature also has possible consequences; no more mails about software that is outdated, unless it is enabled on request, and no possible support if the user's account gets hacked. If the account does get hacked it will be suspend immediately. 8e55e437b2d15c973430ace04f7ad92ecdfbb861 0 222 1668 2021-12-18T14:34:59Z Milanmeu 47 Add new page for alias in Outlook.com wikitext text/x-wiki You may want to send e-mail from Outlook.com using your @ulyssis.org-address, or another domain name that you use for your account. Outlook.com allows you to do this by configuring a few settings. # In Outlook.com, click on the gear icon at the top right. # Click '''View all Outlook settings''' (Dutch: '''Alle Outlook-instellingen weergeven'''). # Open the menu '''Mail''' (Dutch: '''E-mail'''), then: '''Sync email''' (Dutch: '''E-mail synchroniseren'''). # Under '''Email aliases''' (Dutch: '''E-mailaliassen''') select '''Other email accounts''' (Dutch: '''Andere e-mailaccounts'''). # Fill in the e-mail address you want to send from and your KU Leuven account password. # Check '''Manually configure account settings (POP, IMAP, or send-only account)''' (Dutch: '''Accountinstellingen (POP-/IMAP-account of account voor alleen verzenden) handmatig configureren'''). # Click '''OK''' and fill in the following SMTP information (https://admin.kuleuven.be/icts/services/email/begrippen): #* '''User name''': your KU Leuven intranet userid r or u number e.g. r0123456 #* '''Choose your connection type''': '''SMTP send-only connection settings''' #* '''Outgoing (SMTP) server''': '''smtps.kuleuven.be''' #* '''Outgoing server port''': '''465''' # Optionally: Enter a '''Display name''', the recipient will see this name instead of or next to your email address. # Press on '''OK'''. You can now send emails from this email address. # In Outlook.com, click '''New message''' (Dutch: ''' Nieuw bericht'''). # Click on '''From''' (Dutch: '''Van'''), and select '''Other email address...''' (Dutch: '''Ander e-mailadres...'''). # Enter the email address you want to send from. [[Category:Mail]] 5840a7b3f4e9ee9ce857fc93c8b4e04054f2aaf0 0 225 1679 2022-03-20T14:46:10Z Debber 46 Created page with "These are the docs for the new MediaWiki install" wikitext text/x-wiki These are the docs for the new MediaWiki install 69cd80c05ee2940bd2ebdebcafb0264e79f2cdc5 6 226 1680 2022-03-20T14:48:18Z Debber 46 wikitext text/x-wiki Open cyberduck a74b473dc44233fedcb78613caa3e4d789bd1750 6 227 1681 2022-03-20T14:51:25Z Debber 46 wikitext text/x-wiki Go to the WWW folder d6b8215cc824f802392033d30817c7eb20842800 6 228 1682 2022-03-20T14:53:14Z Debber 46 wikitext text/x-wiki Click on the upload button b279ac4a49537a2a8ca12f90a71142fda8a0ea5b 6 229 1683 2022-03-20T14:55:06Z Debber 46 wikitext text/x-wiki Select the MediaWiki zip 3d37261d961a9d5e99b258f4e88437b8346b8df2 6 230 1684 2022-03-20T14:56:21Z Debber 46 wikitext text/x-wiki Click allow 939308b732e89d00b521e318f5dbd17d93ca6f29 6 231 1685 2022-03-20T14:58:14Z Debber 46 wikitext text/x-wiki Wait until the upload is complete 0ad8731dc3e6bd083810879ebb54dfea854bab31 6 232 1686 2022-03-20T15:00:21Z Debber 46 wikitext text/x-wiki Right click on the zip and choose expand archive e473f60eabe0890dd5314046a90145c7dcd19782 6 233 1687 2022-03-20T15:02:07Z Debber 46 wikitext text/x-wiki The progress can be found on the bottom of the window a42fe5237dea394f973d6a7d7df6e29f0c30445f 6 234 1688 2022-03-20T15:03:49Z Debber 46 wikitext text/x-wiki Select everything in the MediaWiki folder 4d2f3dae824490820f4d515b168e9cc443aabb72 6 235 1689 2022-03-20T15:06:32Z Debber 46 wikitext text/x-wiki Delete the zip file and the original folder 7c90a6a7109478734d116ce0243be9952051afa2 6 236 1690 2022-03-20T15:07:58Z Debber 46 wikitext text/x-wiki Go to UCC 25f313a9ddafba34b7c555103f6d78ea37e26175 6 237 1691 2022-03-20T15:10:18Z Debber 46 wikitext text/x-wiki Create a new MYSQL database 06e2bbbd943231395cbf543c18d5b63fa6221393 6 238 1692 2022-03-20T15:15:52Z Debber 46 wikitext text/x-wiki Go to your wiki bfd943d5ef57a5549c5c13eb1a80594cc5862e56 6 239 1693 2022-03-20T15:19:45Z Debber 46 wikitext text/x-wiki Set your language cd8fa4ae3b5aec1e29c3e24cb80c46696cd0b40a 6 240 1694 2022-03-20T15:20:43Z Debber 46 wikitext text/x-wiki The installation page b910252a980c3f47301d0965af5917696041c51a 6 241 1695 2022-03-20T15:22:24Z Debber 46 wikitext text/x-wiki Configure the database in MediaWiki 3019e4f4ea3c16cdcf51376fb9b2dc6bd04776af 6 242 1696 2022-03-20T15:25:01Z Debber 46 wikitext text/x-wiki Database settings 73aa2872cc8b1a8efd768eba43212a55071dedb8 6 243 1697 2022-03-20T15:26:21Z Debber 46 wikitext text/x-wiki Configure MediaWiki settings 1c0d28ece56cea9da91ee2c6e437396b6571c982 6 244 1698 2022-03-20T15:31:35Z Debber 46 wikitext text/x-wiki This is the final install page 4c24bd4ef623a5fb247c4c698542cefb082d7f58 6 245 1699 2022-03-20T15:37:49Z Debber 46 wikitext text/x-wiki Download LocalSettings.php 0c66ce894c32ff797ca831222b9ff96962b9e40a 6 246 1700 2022-03-20T15:39:21Z Debber 46 wikitext text/x-wiki Upload LocalSettings.php 1a6872fb7e1a1cd90facf45055d9882cd079108c 6 247 1701 2022-03-20T15:44:16Z Debber 46 wikitext text/x-wiki Open a new tab and go to username.ulyssis.be 43324126b15d5be8cadf7513ea73fcda71b7d9d0 0 225 1702 1679 2022-03-20T15:44:55Z Debber 46 wikitext text/x-wiki These are the docs for the new MediaWiki install Get the MediaWiki zip from the official website. First open cyberduck (wtf is cyberduck: well, [[Accessing your files]]) [[File:OpenCyberduck.png|left|thumb|400x400px|Open Cyberduck]] Go to the WWW folder [[File:GoToWWW.png|left|thumb|394x394px|Go to the WWW folder]] Click on the upload button located at the top of the window [[File:ClickOnUpload.png|left|thumb|Click on the upload button]] Choose the MediaWiki zip [[File:SelectMediaWikiZIP.png|left|thumb|Select the MediaWiki zip]] You shall not pass, unless you press allow... [[File:WindowPopup.png|left|thumb|Click allow]] Let the dough rise for 30 minutes or until doubled in size [[File:WaitUntilComplete.png|left|thumb|Wait until the upload is complete]] Unzip your zipper [[File:RightClick ExpandArchive.png|left|thumb|405x405px|Right click on the zip and choose expand archive]] The progress on the bottom part of the window [[File:ProgressBottomWindow.png|left|thumb|411x411px|The progress can be found on the bottom of the window]] Select everything in the MediaWiki folder and move it outside of the folder by dragging your mouse [[File:SelectEverything.png|left|thumb|379x379px|Select everything in the MediaWiki folder]] Delete the zip file and the original folder by right clicking and choosing delete [[File:DeleteOGfiles.png|left|thumb|Delete the zip file and the original folder]] Now we'll go to UCC and choose your mysql crap (create account if you do not have one [[Using MySQL]]) [[File:GoToUCC.png|left|thumb|Go to UCC]] Create arnodb [[File:CreateDB.png|left|thumb|Create a new MySQL database]] Go to your new wiki page at username.ulyssis.be [[File:GoToWiki.png|left|thumb|412x412px|Go to your wiki at username.ulyssis.be]]Set you language [[File:SetLanguage.png|left|thumb|407x407px|Set your language ]] This is the installation page [[File:InstallPage.png|left|thumb|401x401px|This is the beginning of the installation ]] Configure arnodb [[File:ConfigureDB.png|left|thumb|423x423px|Configure the database in MediaWiki]] Configure wikidb settings [[File:DBSettings.png|left|thumb|449x449px|Database settings in MediaWiki]] Configure wiki settings (making the OG admin) [[File:WikiSettings.png|left|thumb|458x458px|Configure the final MediaWiki settings]] The install page [[File:InstalationPage.png|left|thumb|471x471px|This is the final install page]] Download LocalSettings.php [[File:DownloadLocalSettings.png|left|thumb|480x480px|Download LocalSettings.php]] Upload LocalSettings.php (via Cyberduck again) [[File:UploadLocalSettings.png|left|thumb|Upload LocalSettings.php]] Open new tab and go to username.ulyssis.be [[File:OpenNewTab.png|left|thumb|486x486px|Open a new tab and go to username.ulyssis.be]] Tadaaa 75a392b2775a8572fbfa7d4df863be9c471827ae 1703 1702 2022-03-22T17:21:05Z Debber 46 Layout dingen wikitext text/x-wiki This page will go through a basic setup of MediaWiki. It is based on [[mediawikiwiki:Manual:Installing_MediaWiki|the official MediaWiki installation wikipage]], and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. == Prerequisites== This tutorial assumes that you have [https://cyberduck.io/ Cyberduck] installed. A guide on how to install and use Cyberduck can be found on [[Accessing your files]]. You will also have to download the [https://www.mediawiki.org/wiki/Download MediaWiki installation files]. We reccomend using the latest version or the long-term support (LTS) version. == Installation == As mentioned in the Prerequisites, we'll use Cyberduck for the installation of MediaWiki. Make sure you are logged in to you ULYSSIS account, and that you see the following screen. [[File:OpenCyberduck.png|left|thumb|400x400px|Open Cyberduck]] In this tutorial, we will install our MediaWiki in the www folder. We can do this by double clicking the folder. [[File:GoToWWW.png|left|thumb|394x394px|Go to the WWW folder]] We are now ready to upload the necessary files for the MediaWiki installation. This can be done by clicking the 'Upload' button at the top of the Cyberduck window. A popup should appear on your screen. [[File:ClickOnUpload.png|left|thumb|Click on the upload button]] Navigate to the folder in which the installation files are stored. Select them and click on 'Choose' on the bottom right of the popup. [[File:SelectMediaWikiZIP.png|left|thumb|Select the MediaWiki zip]] The upload process wil now start automatically. It is possible that you get another popup, be sure to click 'Allow'. Otherwise, the files will not be uploaded. [[File:WindowPopup.png|left|thumb|Click allow]] If the upload has completed, you should get a window which looks like this: [[File:WaitUntilComplete.png|left|thumb|Wait until the upload is complete]] Unzip your zipper [[File:RightClick ExpandArchive.png|left|thumb|405x405px|Right click on the zip and choose expand archive]] The progress on the bottom part of the window [[File:ProgressBottomWindow.png|left|thumb|411x411px|The progress can be found on the bottom of the window]] Select everything in the MediaWiki folder and move it outside of the folder by dragging your mouse [[File:SelectEverything.png|left|thumb|379x379px|Select everything in the MediaWiki folder]] Delete the zip file and the original folder by right clicking and choosing delete [[File:DeleteOGfiles.png|left|thumb|Delete the zip file and the original folder]] Now we'll go to UCC and choose your mysql crap (create account if you do not have one [[Using MySQL]]) [[File:GoToUCC.png|left|thumb|Go to UCC]] Create arnodb [[File:CreateDB.png|left|thumb|Create a new MySQL database]] Go to your new wiki page at username.ulyssis.be [[File:GoToWiki.png|left|thumb|412x412px|Go to your wiki at username.ulyssis.be]]Set you language [[File:SetLanguage.png|left|thumb|407x407px|Set your language ]] This is the installation page [[File:InstallPage.png|left|thumb|401x401px|This is the beginning of the installation ]] Configure arnodb [[File:ConfigureDB.png|left|thumb|423x423px|Configure the database in MediaWiki]] Configure wikidb settings [[File:DBSettings.png|left|thumb|449x449px|Database settings in MediaWiki]] Configure wiki settings (making the OG admin) [[File:WikiSettings.png|left|thumb|458x458px|Configure the final MediaWiki settings]] The install page [[File:InstalationPage.png|left|thumb|471x471px|This is the final install page]] Download LocalSettings.php [[File:DownloadLocalSettings.png|left|thumb|480x480px|Download LocalSettings.php]] Upload LocalSettings.php (via Cyberduck again) [[File:UploadLocalSettings.png|left|thumb|Upload LocalSettings.php]] Open new tab and go to username.ulyssis.be [[File:OpenNewTab.png|left|thumb|486x486px|Open a new tab and go to username.ulyssis.be]] Tadaaa 6cb782e6824cb9e82e6857c14d64999c5c00ed14 1704 1703 2022-04-06T06:59:29Z Debber 46 /* Prerequisites */ wikitext text/x-wiki This page will go through a basic setup of MediaWiki. It is based on [[mediawikiwiki:Manual:Installing_MediaWiki|the official MediaWiki installation wikipage]], and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. == Prerequisites== This tutorial assumes that you have [https://cyberduck.io/ Cyberduck] installed. A guide on how to install and use Cyberduck can be found on [[Accessing your files]]. You will also have to download the [https://www.mediawiki.org/wiki/Download MediaWiki installation files]. We reccomend using either the latest version or the long-term support (LTS) version. == Installation == As mentioned in the Prerequisites, we'll use Cyberduck for the installation of MediaWiki. Make sure you are logged in to you ULYSSIS account, and that you see the following screen. [[File:OpenCyberduck.png|left|thumb|400x400px|Open Cyberduck]] In this tutorial, we will install our MediaWiki in the www folder. We can do this by double clicking the folder. [[File:GoToWWW.png|left|thumb|394x394px|Go to the WWW folder]] We are now ready to upload the necessary files for the MediaWiki installation. This can be done by clicking the 'Upload' button at the top of the Cyberduck window. A popup should appear on your screen. [[File:ClickOnUpload.png|left|thumb|Click on the upload button]] Navigate to the folder in which the installation files are stored. Select them and click on 'Choose' on the bottom right of the popup. [[File:SelectMediaWikiZIP.png|left|thumb|Select the MediaWiki zip]] The upload process wil now start automatically. It is possible that you get another popup, be sure to click 'Allow'. Otherwise, the files will not be uploaded. [[File:WindowPopup.png|left|thumb|Click allow]] If the upload has completed, you should get a window which looks like this: [[File:WaitUntilComplete.png|left|thumb|Wait until the upload is complete]] In the main Cyberduck window, you should be able to see the MediaWiki file you just uploaded. To unzip this file, just right click it and choose 'expand archive'. [[File:RightClick ExpandArchive.png|left|thumb|405x405px|Right click on the zip and choose expand archive]] This process might take a while, you can verify the progress by looking at the bottom part of the Cyberduck window. [[File:ProgressBottomWindow.png|left|thumb|411x411px|The progress can be found on the bottom of the window]] Select everything in the new MediaWiki folder and move it outside of the folder. [[File:SelectEverything.png|left|thumb|379x379px|Select everything in the MediaWiki folder]] Delete the zip file and the original folder by right clicking and choosing delete [[File:DeleteOGfiles.png|left|thumb|Delete the zip file and the original folder]] Now we'll go to UCC and create a database for our mediawiki installation. (if this is your first time making a database, we reccomend our documentation on [[Using MySQL]]) [[File:GoToUCC.png|left|thumb|Go to UCC|560x560px]] Choose the 'Add database' option just below your username. This should bring you to a page which looks like this. We reccomend naming your database 'wiki'. [[File:CreateDB.png|left|thumb|Create a new MySQL database|568x568px]] You are now ready to configure your new wiki at username.ulyssis.be . To start, click on the 'set up the wiki' hyperlink. [[File:GoToWiki.png|left|thumb|578x578px|Go to your wiki at username.ulyssis.be]]You will be prompted to set your prefered language. [[File:SetLanguage.png|left|thumb|585x585px|Set your language ]] This is where the real installation begins. We can just click 'continue'. [[File:InstallPage.png|left|thumb|588x588px|This is the beginning of the installation ]] We will first configure the database we just created. This is specific to your personal configuration, an example has been given below. [[File:ConfigureDB.png|left|thumb|592x592px|Configure the database in MediaWiki]] Once the database has been configured, you can just click 'continue'. On the following page, make sure the checkbox is checked and click 'continue' again. [[File:DBSettings.png|left|thumb|600x600px|Database settings in MediaWiki]] We now get promted to choose a wiki name (you can choose this to be whatever you want), we also have to make the administrator account. [[File:WikiSettings.png|left|thumb|601x601px|Configure the final MediaWiki settings]] Once everything has been created, you should land on the following page. You don't have to configure anything on this page. [[File:InstalationPage.png|left|thumb|596x596px|This is the final install page]] When the MediaWiki installation has been confirmed, you will have to download the 'LocalSettings.php' file. This file contains the essential settings for your MediaWiki instance to work properly. [[File:DownloadLocalSettings.png|left|thumb|607x607px|Download LocalSettings.php]] Upload LocalSettings.php via cyberduck to the same folder where you placed the MediaWiki files. [[File:UploadLocalSettings.png|left|thumb|Upload LocalSettings.php]] You can now open a new tab, and go to username.ulyssis.be . You should be able to see your new wiki. [[File:OpenNewTab.png|left|thumb|486x486px|Open a new tab and go to username.ulyssis.be]] For further support, we recccomend the [https://www.mediawiki.org/wiki/Manual:Installation_guide official MediaWiki documentation.] d04ed8b0d1201edfc3b135fdfb1d52ea19fd005e 1709 1704 2022-05-06T07:32:55Z Sydon 48 /* Prerequisites */ typo aangepast wikitext text/x-wiki This page will go through a basic setup of MediaWiki. It is based on [[mediawikiwiki:Manual:Installing_MediaWiki|the official MediaWiki installation wikipage]], and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. == Prerequisites== This tutorial assumes that you have [https://cyberduck.io/ Cyberduck] installed. A guide on how to install and use Cyberduck can be found on [[Accessing your files]]. You will also have to download the [https://www.mediawiki.org/wiki/Download MediaWiki installation files]. We recommend using either the latest version or the long-term support (LTS) version. == Installation == As mentioned in the Prerequisites, we'll use Cyberduck for the installation of MediaWiki. Make sure you are logged in to you ULYSSIS account, and that you see the following screen. [[File:OpenCyberduck.png|left|thumb|400x400px|Open Cyberduck]] In this tutorial, we will install our MediaWiki in the www folder. We can do this by double clicking the folder. [[File:GoToWWW.png|left|thumb|394x394px|Go to the WWW folder]] We are now ready to upload the necessary files for the MediaWiki installation. This can be done by clicking the 'Upload' button at the top of the Cyberduck window. A popup should appear on your screen. [[File:ClickOnUpload.png|left|thumb|Click on the upload button]] Navigate to the folder in which the installation files are stored. Select them and click on 'Choose' on the bottom right of the popup. [[File:SelectMediaWikiZIP.png|left|thumb|Select the MediaWiki zip]] The upload process wil now start automatically. It is possible that you get another popup, be sure to click 'Allow'. Otherwise, the files will not be uploaded. [[File:WindowPopup.png|left|thumb|Click allow]] If the upload has completed, you should get a window which looks like this: [[File:WaitUntilComplete.png|left|thumb|Wait until the upload is complete]] In the main Cyberduck window, you should be able to see the MediaWiki file you just uploaded. To unzip this file, just right click it and choose 'expand archive'. [[File:RightClick ExpandArchive.png|left|thumb|405x405px|Right click on the zip and choose expand archive]] This process might take a while, you can verify the progress by looking at the bottom part of the Cyberduck window. [[File:ProgressBottomWindow.png|left|thumb|411x411px|The progress can be found on the bottom of the window]] Select everything in the new MediaWiki folder and move it outside of the folder. [[File:SelectEverything.png|left|thumb|379x379px|Select everything in the MediaWiki folder]] Delete the zip file and the original folder by right clicking and choosing delete [[File:DeleteOGfiles.png|left|thumb|Delete the zip file and the original folder]] Now we'll go to UCC and create a database for our mediawiki installation. (if this is your first time making a database, we reccomend our documentation on [[Using MySQL]]) [[File:GoToUCC.png|left|thumb|Go to UCC|560x560px]] Choose the 'Add database' option just below your username. This should bring you to a page which looks like this. We reccomend naming your database 'wiki'. [[File:CreateDB.png|left|thumb|Create a new MySQL database|568x568px]] You are now ready to configure your new wiki at username.ulyssis.be . To start, click on the 'set up the wiki' hyperlink. [[File:GoToWiki.png|left|thumb|578x578px|Go to your wiki at username.ulyssis.be]]You will be prompted to set your prefered language. [[File:SetLanguage.png|left|thumb|585x585px|Set your language ]] This is where the real installation begins. We can just click 'continue'. [[File:InstallPage.png|left|thumb|588x588px|This is the beginning of the installation ]] We will first configure the database we just created. This is specific to your personal configuration, an example has been given below. [[File:ConfigureDB.png|left|thumb|592x592px|Configure the database in MediaWiki]] Once the database has been configured, you can just click 'continue'. On the following page, make sure the checkbox is checked and click 'continue' again. [[File:DBSettings.png|left|thumb|600x600px|Database settings in MediaWiki]] We now get promted to choose a wiki name (you can choose this to be whatever you want), we also have to make the administrator account. [[File:WikiSettings.png|left|thumb|601x601px|Configure the final MediaWiki settings]] Once everything has been created, you should land on the following page. You don't have to configure anything on this page. [[File:InstalationPage.png|left|thumb|596x596px|This is the final install page]] When the MediaWiki installation has been confirmed, you will have to download the 'LocalSettings.php' file. This file contains the essential settings for your MediaWiki instance to work properly. [[File:DownloadLocalSettings.png|left|thumb|607x607px|Download LocalSettings.php]] Upload LocalSettings.php via cyberduck to the same folder where you placed the MediaWiki files. [[File:UploadLocalSettings.png|left|thumb|Upload LocalSettings.php]] You can now open a new tab, and go to username.ulyssis.be . You should be able to see your new wiki. [[File:OpenNewTab.png|left|thumb|486x486px|Open a new tab and go to username.ulyssis.be]] For further support, we recccomend the [https://www.mediawiki.org/wiki/Manual:Installation_guide official MediaWiki documentation.] f2d596422809a995a5a2b50ef77cecece624cd98 1710 1709 2022-05-06T07:35:29Z Sydon 48 /* Installation */ wikitext text/x-wiki This page will go through a basic setup of MediaWiki. It is based on [[mediawikiwiki:Manual:Installing_MediaWiki|the official MediaWiki installation wikipage]], and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. == Prerequisites== This tutorial assumes that you have [https://cyberduck.io/ Cyberduck] installed. A guide on how to install and use Cyberduck can be found on [[Accessing your files]]. You will also have to download the [https://www.mediawiki.org/wiki/Download MediaWiki installation files]. We recommend using either the latest version or the long-term support (LTS) version. == Installation == As mentioned in the Prerequisites, we will be using Cyberduck for the installation of MediaWiki. Make sure you are logged in to your ULYSSIS account and that you see the following screen after opening Cyberduck [[File:OpenCyberduck.png|left|thumb|400x400px|Open Cyberduck]] In this tutorial, we will install our MediaWiki in the www folder. We can do this by double clicking the folder. [[File:GoToWWW.png|left|thumb|394x394px|Go to the WWW folder]] We are now ready to upload the necessary files for the MediaWiki installation. This can be done by clicking the 'Upload' button at the top of the Cyberduck window. A popup should appear on your screen. [[File:ClickOnUpload.png|left|thumb|Click on the upload button]] Navigate to the folder in which the installation files are stored. Select them and click on 'Choose' on the bottom right of the popup. [[File:SelectMediaWikiZIP.png|left|thumb|Select the MediaWiki zip]] The upload process wil now start automatically. It is possible that you get another popup, be sure to click 'Allow'. Otherwise, the files will not be uploaded. [[File:WindowPopup.png|left|thumb|Click allow]] If the upload has completed, you should get a window which looks like this: [[File:WaitUntilComplete.png|left|thumb|Wait until the upload is complete]] In the main Cyberduck window, you should be able to see the MediaWiki file you just uploaded. To unzip this file, just right click it and choose 'expand archive'. [[File:RightClick ExpandArchive.png|left|thumb|405x405px|Right click on the zip and choose expand archive]] This process might take a while, you can verify the progress by looking at the bottom part of the Cyberduck window. [[File:ProgressBottomWindow.png|left|thumb|411x411px|The progress can be found on the bottom of the window]] Select everything in the new MediaWiki folder and move it outside of the folder. [[File:SelectEverything.png|left|thumb|379x379px|Select everything in the MediaWiki folder]] Delete the zip file and the original folder by right clicking and choosing delete [[File:DeleteOGfiles.png|left|thumb|Delete the zip file and the original folder]] Now we'll go to UCC and create a database for our mediawiki installation. (if this is your first time making a database, we reccomend our documentation on [[Using MySQL]]) [[File:GoToUCC.png|left|thumb|Go to UCC|560x560px]] Choose the 'Add database' option just below your username. This should bring you to a page which looks like this. We reccomend naming your database 'wiki'. [[File:CreateDB.png|left|thumb|Create a new MySQL database|568x568px]] You are now ready to configure your new wiki at username.ulyssis.be . To start, click on the 'set up the wiki' hyperlink. [[File:GoToWiki.png|left|thumb|578x578px|Go to your wiki at username.ulyssis.be]]You will be prompted to set your prefered language. [[File:SetLanguage.png|left|thumb|585x585px|Set your language ]] This is where the real installation begins. We can just click 'continue'. [[File:InstallPage.png|left|thumb|588x588px|This is the beginning of the installation ]] We will first configure the database we just created. This is specific to your personal configuration, an example has been given below. [[File:ConfigureDB.png|left|thumb|592x592px|Configure the database in MediaWiki]] Once the database has been configured, you can just click 'continue'. On the following page, make sure the checkbox is checked and click 'continue' again. [[File:DBSettings.png|left|thumb|600x600px|Database settings in MediaWiki]] We now get promted to choose a wiki name (you can choose this to be whatever you want), we also have to make the administrator account. [[File:WikiSettings.png|left|thumb|601x601px|Configure the final MediaWiki settings]] Once everything has been created, you should land on the following page. You don't have to configure anything on this page. [[File:InstalationPage.png|left|thumb|596x596px|This is the final install page]] When the MediaWiki installation has been confirmed, you will have to download the 'LocalSettings.php' file. This file contains the essential settings for your MediaWiki instance to work properly. [[File:DownloadLocalSettings.png|left|thumb|607x607px|Download LocalSettings.php]] Upload LocalSettings.php via cyberduck to the same folder where you placed the MediaWiki files. [[File:UploadLocalSettings.png|left|thumb|Upload LocalSettings.php]] You can now open a new tab, and go to username.ulyssis.be . You should be able to see your new wiki. [[File:OpenNewTab.png|left|thumb|486x486px|Open a new tab and go to username.ulyssis.be]] For further support, we recccomend the [https://www.mediawiki.org/wiki/Manual:Installation_guide official MediaWiki documentation.] e2304b68f3f8500a41222821e9b7d36106bab0ad 1711 1710 2022-05-06T07:39:14Z Sydon 48 /* Installation */ wikitext text/x-wiki This page will go through a basic setup of MediaWiki. It is based on [[mediawikiwiki:Manual:Installing_MediaWiki|the official MediaWiki installation wikipage]], and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. == Prerequisites== This tutorial assumes that you have [https://cyberduck.io/ Cyberduck] installed. A guide on how to install and use Cyberduck can be found on [[Accessing your files]]. You will also have to download the [https://www.mediawiki.org/wiki/Download MediaWiki installation files]. We recommend using either the latest version or the long-term support (LTS) version. == Installation == As mentioned in the Prerequisites, we will be using Cyberduck for the installation of MediaWiki. Make sure you are logged in to your ULYSSIS account and that you see the following screen after opening Cyberduck [[File:OpenCyberduck.png|left|thumb|400x400px|Open Cyberduck]] In this tutorial, we will install our MediaWiki in the www folder. We can do this by double clicking the folder. [[File:GoToWWW.png|left|thumb|394x394px|Go to the WWW folder]] We are now ready to upload the necessary files for the MediaWiki installation. This can be done by clicking the 'Upload' button at the top of the Cyberduck window. A pop-up should appear on your screen. [[File:ClickOnUpload.png|left|thumb|Click on the upload button]] Navigate to the folder in which the installation files are stored. Select them and click on 'Choose' on the bottom right of the pop-up. [[File:SelectMediaWikiZIP.png|left|thumb|Select the MediaWiki zip]] The upload process wil now start automatically. Incase you get another pop-up, be sure to click "Allow", otherwise the files will not be uploaded. [[File:WindowPopup.png|left|thumb|Click allow]] After the upload is completed, you should get a window which looks like this: [[File:WaitUntilComplete.png|left|thumb|Wait until the upload is complete]] In the main Cyberduck window, you should be able to see the MediaWiki file you just uploaded. To unzip this file, just right click it and choose 'expand archive'. [[File:RightClick ExpandArchive.png|left|thumb|405x405px|Right click on the zip and choose expand archive]] This process might take a while, you can verify the progress by looking at the bottom part of the Cyberduck window. [[File:ProgressBottomWindow.png|left|thumb|411x411px|The progress can be found on the bottom of the window]] Select everything in the new MediaWiki folder and move it out of the folder. [[File:SelectEverything.png|left|thumb|379x379px|Select everything in the MediaWiki folder]] Delete the zip file and the original folder by right clicking and choosing delete [[File:DeleteOGfiles.png|left|thumb|Delete the zip file and the original folder]] Now we'll go to UCC and create a database for our mediawiki installation. (if this is your first time making a database, we reccomend our documentation on [[Using MySQL]]) [[File:GoToUCC.png|left|thumb|Go to UCC|560x560px]] Choose the 'Add database' option just below your username. This should bring you to a page which looks like this. We reccomend naming your database 'wiki'. [[File:CreateDB.png|left|thumb|Create a new MySQL database|568x568px]] You are now ready to configure your new wiki at username.ulyssis.be . To start, click on the 'set up the wiki' hyperlink. [[File:GoToWiki.png|left|thumb|578x578px|Go to your wiki at username.ulyssis.be]]You will be prompted to set your prefered language. [[File:SetLanguage.png|left|thumb|585x585px|Set your language ]] This is where the real installation begins. We can just click 'continue'. [[File:InstallPage.png|left|thumb|588x588px|This is the beginning of the installation ]] We will first configure the database we just created. This is specific to your personal configuration, an example has been given below. [[File:ConfigureDB.png|left|thumb|592x592px|Configure the database in MediaWiki]] Once the database has been configured, you can just click 'continue'. On the following page, make sure the checkbox is checked and click 'continue' again. [[File:DBSettings.png|left|thumb|600x600px|Database settings in MediaWiki]] We now get promted to choose a wiki name (you can choose this to be whatever you want), we also have to make the administrator account. [[File:WikiSettings.png|left|thumb|601x601px|Configure the final MediaWiki settings]] Once everything has been created, you should land on the following page. You don't have to configure anything on this page. [[File:InstalationPage.png|left|thumb|596x596px|This is the final install page]] When the MediaWiki installation has been confirmed, you will have to download the 'LocalSettings.php' file. This file contains the essential settings for your MediaWiki instance to work properly. [[File:DownloadLocalSettings.png|left|thumb|607x607px|Download LocalSettings.php]] Upload LocalSettings.php via cyberduck to the same folder where you placed the MediaWiki files. [[File:UploadLocalSettings.png|left|thumb|Upload LocalSettings.php]] You can now open a new tab, and go to username.ulyssis.be . You should be able to see your new wiki. [[File:OpenNewTab.png|left|thumb|486x486px|Open a new tab and go to username.ulyssis.be]] For further support, we recccomend the [https://www.mediawiki.org/wiki/Manual:Installation_guide official MediaWiki documentation.] d25c47244cfc5129f411258e6346c9c56021976a 0 10 1705 1284 2022-04-09T21:43:50Z Arnodb 49 /* Generating certificates */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven is you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty consultative bodies (facultaire overlegorganen) recognized by Studentenraad KU Leuven as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. We are not eligible to request SSL/TLS certificates for individuals with a personal account, nor research groups or staff associations. We suggest those latter groups request certificates from KU Leuven ICTS directly or consider Let's Encrypt or another third party service. Before sending us a request, the following steps have to be performed: * Set up the site that needs SSL if that's not already the case * Make sure our nameservers are being used for the involved domain(s), as explained on [[Adding domain names]] * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir -p ~/letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain (the CA file) ├── mydomain.be.crt (the cert file; "public key") └── mydomain.be.key (the key file; "private key") If you already possess the necessary files, renaming and copying them accordingly is sufficient. '''You still have to email us to install your certificate.''' More information in the last section on this page. Otherwise, you can generate or renew your certificates using acme.sh. This is explained in the next section. ==== Generating certificates ==== {{notice|If you use a <code>.htaccess</code> file in the webroot of the domain name, make sure to add the following lines at the top of the file:|<pre><IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule></pre>}} Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll show how to use the acme.sh program to generate certificates on the ULYSSIS servers. '''If you already followed this section to generate certificates, skip to the next section on renewing certificates.''' Firstly, execute the following commands to download the acme.sh script in your home directory and make it executable: curl -o ~/acme.sh https://raw.githubusercontent.com/acmesh-official/acme.sh/master/acme.sh chmod +x ~/acme.sh Next, determine for which domains and subdomains you want to generate a certificate. You will need to generate a single certificate for each domain and subdomain which points to the same folder on your account (in most cases this is <code>www</code> in your home directory). The following example command will generate a certificate for <code>mydomain.be</code> and <code>www.mydomain.be</code> which points to the <code>www</code> folder in the home directory. '''Change the parameters''' as explained below before executing this command! ~/acme.sh --issue --cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt --key-file ~/letsencrypt/mydomain.be/mydomain.be.key --ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain -m "email@mydomain.be" -w ~/www -d mydomain.be -d www.mydomain.be --server letsencrypt The explanation of these many parameters is as follows: * <code>--issue</code> tells acme.sh to generate a new certificate. * <code>--cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt</code> tells acme.sh to store the certificate file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. '''This folder should already exist''', please refer to the previous section if you have not created this folder yet. * <code>--key-file ~/letsencrypt/mydomain.be/mydomain.be.key</code> tells acme.sh to store the key file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>--ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain</code> tells acme.sh to store the CA file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>-m "email@mydomain.be"</code> tells acme.sh the email address associated with the certificate. Let's Encrypt will remind this email address (if provided) when the certificate is close to expiring. * <code>-w ~/www</code> tells acme.sh where the domains in this certificate point to. Make sure to change the <code>www</code> part if the domains point to a different folder in your home directory. * <code>-d mydomain.be</code> and <code>-d www.mydomain.be</code> tell acme.sh that the certificate should protect <code>mydomain.be</code> and <code>www.mydomain.be</code>. The first domain name will be the "main domain", which is important for renewing. You should '''add all domain names''' pointing to the <code>-w</code> folder. * <code>--server letsencrypt</code> tells acme.sh to use https://letsencrypt.org/ as Certificate Authority (CA). After executing this command with the right parameters, your certificate should be generated successfully. When you have to renew the certificate in the future, you should follow the instructions in the next section. '''Don't forget to email us to install your new certificate.''' More information in the last section on this page. ==== Renewing certificates ==== To renew the certificates of <code>mydomain.be</code>, just execute: ~/acme.sh --renew -d mydomain.be For the <code>-d</code> parameter, you have to provide the '''first''' domain name you provided when generating the certificate (in the previous section, this was <code>mydomain.be</code>. If you are not sure which domain name to use, you can execute the command: ~/acme.sh --list This will generate a list of available certificates, which looks a bit like this: Main_Domain KeyLength SAN_Domains CA Created Renew mydomain.be "" www.mydomain.be LetsEncrypt.org ... ... ... ... ... ... ... ... In this example, the main domain is <code>mydomain.be</code>. The renewed certificates will automatically be copied to the files you provided in the command to generate the certificates (see previous section). '''After renewing the certificate, you have to email us to install your certificate.''' More information in the next section. ==== Getting your certificates installed ==== Check whether everything is stored correctly by executing the following command: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once all steps are done and if you are the '''account holder''', '''you can send us an email clearly stating the account name, for which domains we need to add certificates and where the files are stored'''. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL, so make sure you follow this procedure carefully. [[Category:Webserver]] 2cd611b8fadcc29d0757ecc1b9d99fe3598adc6f 1708 1705 2022-04-30T07:25:23Z Wtas 42 Typo fix in intro wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven if you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty consultative bodies (facultaire overlegorganen) recognized by Studentenraad KU Leuven as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. We are not eligible to request SSL/TLS certificates for individuals with a personal account, nor research groups or staff associations. We suggest those latter groups request certificates from KU Leuven ICTS directly or consider Let's Encrypt or another third party service. Before sending us a request, the following steps have to be performed: * Set up the site that needs SSL if that's not already the case * Make sure our nameservers are being used for the involved domain(s), as explained on [[Adding domain names]] * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir -p ~/letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain (the CA file) ├── mydomain.be.crt (the cert file; "public key") └── mydomain.be.key (the key file; "private key") If you already possess the necessary files, renaming and copying them accordingly is sufficient. '''You still have to email us to install your certificate.''' More information in the last section on this page. Otherwise, you can generate or renew your certificates using acme.sh. This is explained in the next section. ==== Generating certificates ==== {{notice|If you use a <code>.htaccess</code> file in the webroot of the domain name, make sure to add the following lines at the top of the file:|<pre><IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule></pre>}} Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll show how to use the acme.sh program to generate certificates on the ULYSSIS servers. '''If you already followed this section to generate certificates, skip to the next section on renewing certificates.''' Firstly, execute the following commands to download the acme.sh script in your home directory and make it executable: curl -o ~/acme.sh https://raw.githubusercontent.com/acmesh-official/acme.sh/master/acme.sh chmod +x ~/acme.sh Next, determine for which domains and subdomains you want to generate a certificate. You will need to generate a single certificate for each domain and subdomain which points to the same folder on your account (in most cases this is <code>www</code> in your home directory). The following example command will generate a certificate for <code>mydomain.be</code> and <code>www.mydomain.be</code> which points to the <code>www</code> folder in the home directory. '''Change the parameters''' as explained below before executing this command! ~/acme.sh --issue --cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt --key-file ~/letsencrypt/mydomain.be/mydomain.be.key --ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain -m "email@mydomain.be" -w ~/www -d mydomain.be -d www.mydomain.be --server letsencrypt The explanation of these many parameters is as follows: * <code>--issue</code> tells acme.sh to generate a new certificate. * <code>--cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt</code> tells acme.sh to store the certificate file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. '''This folder should already exist''', please refer to the previous section if you have not created this folder yet. * <code>--key-file ~/letsencrypt/mydomain.be/mydomain.be.key</code> tells acme.sh to store the key file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>--ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain</code> tells acme.sh to store the CA file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>-m "email@mydomain.be"</code> tells acme.sh the email address associated with the certificate. Let's Encrypt will remind this email address (if provided) when the certificate is close to expiring. * <code>-w ~/www</code> tells acme.sh where the domains in this certificate point to. Make sure to change the <code>www</code> part if the domains point to a different folder in your home directory. * <code>-d mydomain.be</code> and <code>-d www.mydomain.be</code> tell acme.sh that the certificate should protect <code>mydomain.be</code> and <code>www.mydomain.be</code>. The first domain name will be the "main domain", which is important for renewing. You should '''add all domain names''' pointing to the <code>-w</code> folder. * <code>--server letsencrypt</code> tells acme.sh to use https://letsencrypt.org/ as Certificate Authority (CA). After executing this command with the right parameters, your certificate should be generated successfully. When you have to renew the certificate in the future, you should follow the instructions in the next section. '''Don't forget to email us to install your new certificate.''' More information in the last section on this page. ==== Renewing certificates ==== To renew the certificates of <code>mydomain.be</code>, just execute: ~/acme.sh --renew -d mydomain.be For the <code>-d</code> parameter, you have to provide the '''first''' domain name you provided when generating the certificate (in the previous section, this was <code>mydomain.be</code>. If you are not sure which domain name to use, you can execute the command: ~/acme.sh --list This will generate a list of available certificates, which looks a bit like this: Main_Domain KeyLength SAN_Domains CA Created Renew mydomain.be "" www.mydomain.be LetsEncrypt.org ... ... ... ... ... ... ... ... In this example, the main domain is <code>mydomain.be</code>. The renewed certificates will automatically be copied to the files you provided in the command to generate the certificates (see previous section). '''After renewing the certificate, you have to email us to install your certificate.''' More information in the next section. ==== Getting your certificates installed ==== Check whether everything is stored correctly by executing the following command: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once all steps are done and if you are the '''account holder''', '''you can send us an email clearly stating the account name, for which domains we need to add certificates and where the files are stored'''. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL, so make sure you follow this procedure carefully. [[Category:Webserver]] 8946b4eb633dc0da7bc85aa7f87152f200665de0 0 72 1706 809 2022-04-21T12:07:51Z Milanmeu 47 Instructies aangepast aan nieuwe Outlook UI. wikitext text/x-wiki You may want to send e-mail from Outlook.com using your @ulyssis.org address, or another domain name that you use for your account. Outlook.com allows you to do this by configuring a few settings. Because you should only be able to send mails from an e-mail address you actually own, make sure that you configured receiving mails before starting this process. Outlook.com will send a confirmation mail to the provided e-mail address to confirm that you own it. # In Outlook.com, click on your profile image. # Click '''My Microsoft account''' (Dutch: '''Mijn Microsoft-account'''). # Go to the tab '''Your info''' (Dutch: '''Je gegevens'''). # Under '''Account info''' (Dutch: '''Rekeninggegevens''') click on: '''Sign-in preferences''' (Dutch: '''Aanmeldingsvoorkeuren'''). # You will have to log in again to proceed. Click '''Add email''' (Dutch: '''E-mailadres toevoegen'''). # Select '''Add an existing email address as a Microsoft account alias''' (Dutch: '''Een bestaand e-mailadres als een Microsoft-accountalias toevoegen''') and fill in the email address you want to send from. # Click '''Add alias''' (Dutch: '''Alias toevoegen'''). # Confirm your request using the link or code, you just received via an email on the address you provided. You can now send emails in Outlook.com from this address: # In Outlook.com, click '''New message''' (Dutch: '''Nieuw bericht'''). # Click on '''From''' (Dutch: '''Van''') and select the email address. [[Category:Mail]] ede9966f197284c100672622a71e191ae4d8a39f 1733 1706 2022-08-14T23:47:35Z Bert 8 wikitext text/x-wiki {{notice|Adding an alias to Hotmail/Outlook is not advised|Hotmail/Outlook does not use a relevant SMTP server, for example the one of the KU Leuven, to send emails as an alias. This may cause recipients to automatically reject your email or mark it as spam.}} You may want to send e-mail from Outlook.com using your @ulyssis.org address, or another domain name that you use for your account. Outlook.com allows you to do this by configuring a few settings. Because you should only be able to send mails from an e-mail address you actually own, make sure that you configured receiving mails before starting this process. Outlook.com will send a confirmation mail to the provided e-mail address to confirm that you own it. # In Outlook.com, click on your profile image. # Click '''My Microsoft account''' (Dutch: '''Mijn Microsoft-account'''). # Go to the tab '''Your info''' (Dutch: '''Je gegevens'''). # Under '''Account info''' (Dutch: '''Rekeninggegevens''') click on: '''Sign-in preferences''' (Dutch: '''Aanmeldingsvoorkeuren'''). # You will have to log in again to proceed. Click '''Add email''' (Dutch: '''E-mailadres toevoegen'''). # Select '''Add an existing email address as a Microsoft account alias''' (Dutch: '''Een bestaand e-mailadres als een Microsoft-accountalias toevoegen''') and fill in the email address you want to send from. # Click '''Add alias''' (Dutch: '''Alias toevoegen'''). # Confirm your request using the link or code, you just received via an email on the address you provided. You can now send emails in Outlook.com from this address: # In Outlook.com, click '''New message''' (Dutch: '''Nieuw bericht'''). # Click on '''From''' (Dutch: '''Van''') and select the email address. [[Category:Mail]] 7c4a21afbbd1c773c718e0da5cb816e6441b91e0 1734 1733 2022-08-14T23:49:21Z Bert 8 wikitext text/x-wiki {{notice|Adding an alias to Hotmail/Outlook is not advised|Hotmail/Outlook does not use a relevant SMTP server, for example the one of the KU Leuven, to send emails as an alias. This may cause recipients to automatically reject your email or mark it as spam. You can circumvent this issue by using Thunderbird or another email provider. Please refer to [[Using a forwarder as an alias]] for some potential alternatives.}} You may want to send e-mail from Outlook.com using your @ulyssis.org address, or another domain name that you use for your account. Outlook.com allows you to do this by configuring a few settings. Because you should only be able to send mails from an e-mail address you actually own, make sure that you configured receiving mails before starting this process. Outlook.com will send a confirmation mail to the provided e-mail address to confirm that you own it. # In Outlook.com, click on your profile image. # Click '''My Microsoft account''' (Dutch: '''Mijn Microsoft-account'''). # Go to the tab '''Your info''' (Dutch: '''Je gegevens'''). # Under '''Account info''' (Dutch: '''Rekeninggegevens''') click on: '''Sign-in preferences''' (Dutch: '''Aanmeldingsvoorkeuren'''). # You will have to log in again to proceed. Click '''Add email''' (Dutch: '''E-mailadres toevoegen'''). # Select '''Add an existing email address as a Microsoft account alias''' (Dutch: '''Een bestaand e-mailadres als een Microsoft-accountalias toevoegen''') and fill in the email address you want to send from. # Click '''Add alias''' (Dutch: '''Alias toevoegen'''). # Confirm your request using the link or code, you just received via an email on the address you provided. You can now send emails in Outlook.com from this address: # In Outlook.com, click '''New message''' (Dutch: '''Nieuw bericht'''). # Click on '''From''' (Dutch: '''Van''') and select the email address. [[Category:Mail]] 5fb3d44be731c2f488b1341d2a5655dd3d0c94e8 0 221 1712 1672 2022-05-06T08:10:52Z Sydon 48 /* Introduction */ databases what er word gestored weggehaald irrelevant, paar zinnen gefixt. wikitext text/x-wiki ==Introduction== Many of our users use the same popular software to run their website. However, as is common in popular and widespread software, various bugs or errors can occur in the program. These flaws can be exploited by hackers to gain access to websites or databases. Whenever a new update is released for any popular software (e.g., WordPress, MediaWiki, Joomla) hackers will find out which security flaws have been patched, and using this knowledge, they try to find users who haven't updated their software, to gain access to the websites or databases. This is the reason why it is so critical to update the software itself, plugins, themes, or any related software as soon as the updates roll out. To help facilitate this and prevent security breaches, we have created a tool, the Software Version Checker, to help you keep the most commonly used software up-to-date. Currently, this feature is only active if you have an organization or student union account. ==What to do when you receive an e-mail== When you receive an e-mail from the Software Version Checker, it is of utmost importance to update the software mentioned in the e-mail. It is also the best time to check if the other software you use is up-to-date. As mentioned below, our tool does not check all software. You can find more information [[Updating WordPress|here]] on how to automate this for WordPress to save a lot of time and effort. Since updating MediaWiki can be a somewhat daunting process, we have made a more detailed guide available on [[Updating MediaWiki]]. ==Supported Software== Sadly not every piece of software can be supported. Because of this, we have decided to choose the most popular software, since they are more likely to get security breaches. *Drupal (including modules and themes) *Joomla (Plugins are not supported) *MediaWiki (MediaWiki Extensions and Themes are not supported) *phpBB (including plugins and styles) *WordPress (including plugins and themes) ==Functionality of the Software Version Checker== The Software Version Checker fulfills the following functions : *Scan relevant files, detect supported software, and store in database *Check the version and validity of outdated software *Notify accounts that are using outdated software The Software Version Checker does this once every day. ==Ignoring specific software== The Software Version Checker has a feature that allows to specify paths that the Software Version Checker will not search. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. ==Ignoring Organisations/Student Unions== The Software Version Checker also allows our users to ignore specific Organisations or Student Unions entirely. This feature is possible on request, but only after extensive deliberation with ULYSSIS. Enabling this feature also has possible consequences; no more mails about software that is outdated, unless it is enabled on request, and no possible support if the user's account gets hacked. If the account does get hacked it will be suspend immediately. 3418432d55730bda48a00f13ac2493c3a23b81b7 0 248 1713 2022-05-26T23:35:27Z Bert 8 Created page with "Under rare circumstances, it may be necessary to change the DNS records of a domain name that uses the ULYSSIS nameservers, as suggested on [[Adding domain names]]. For exampl..." wikitext text/x-wiki Under rare circumstances, it may be necessary to change the DNS records of a domain name that uses the ULYSSIS nameservers, as suggested on [[Adding domain names]]. For example, you may want to change mail provider, add a verification TXT record, or link a specific subdomain to an external service. Currently, you can't make these changes yourself, but as an account holder you can simply email ulyssis@ulyssis.org with the necessary details: * which domain do you wish to edit records for * for each change, clearly list the record type, whether it's for the main domain or a subdomain, and what the value should be If you are unsure if you've understood the DNS records you need to change correctly or if you don't know which nameservers your domain uses, then feel free to contact us for advice. 9cf0d50b21247570fd1bf9694dbb68dfa90f1b05 0 34 1714 1070 2022-06-07T15:12:54Z Milanmeu 47 Replace with new version wikitext text/x-wiki You may want to send e-mail from Gmail using your @ulyssis.org-address, or another domain name that you use for your account. Gmail allows you to do this, but asks for SMTP info. We don't provide SMTP on our own mail server, but you can use the SMTP servers of the KU Leuven. Because you should only be able to send mails from an email address you actually own, make sure that you configured receiving mails before starting this process. Gmail will send a confirmation mail to the provided email address to confirm that you own it. # In Gmail, click on the gear icon at the top right. # Click '''See all settings''' (Dutch: '''Alle instellingen bekijken'''). # Go to the tab '''Accounts and Import''' (Dutch: '''Accounts en import'''). # Under '''Send mail as:''' (Dutch: '''Mail verzenden als:'''), click on: '''Add another email address''' (Dutch: '''Nog een e-mailadres toevoegen'''). # Fill in the email address you want to send from, and check '''Treat as an alias.''' (Dutch: '''Beschouwen als alias.''') More info: https://support.google.com/a/answer/1710338 # Optionally: Enter a '''Name''', the recipient will see this name instead of or next to your email address. # Click on '''Next step''' (Dutch: '''Volgende stap'''). # Fill in the [https://admin.kuleuven.be/icts/english/services/email/imap-configuratie-en KU Leuven SMTP information] ([https://admin.kuleuven.be/icts/services/email/imap-configuratie Dutch]): #*'''SMTP server''': '''smtps.kuleuven.be''' #* '''Port''': '''465''' #* '''Username''': your KU Leuven intranet userid r or u-number e.g. r0123456 #* '''Password''': your central KU Leuven password #* '''Secured connection using''': '''SSL''' # Click on the '''Add Account''' (Dutch: '''Account toevoegen''') button. # Confirm your request using the link or code, you just received via an email on the address you provided. You can now send emails in Gmail from this address: # In Gmail, click '''Compose''' (Dutch: '''Opstellen'''). # Click on the email address next to '''From''' (Dutch: '''Van'''). # Select the email address you want to send from. [[Category:Mail]] 1179e784667191afe7ed240d2ebee2ba838d1d80 1726 1714 2022-08-14T23:09:50Z Bert 8 wikitext text/x-wiki You may want to send e-mail from Gmail using your @ulyssis.org address, or another domain name that you use for your account. Gmail allows you to do this, but asks for SMTP info. We don't provide SMTP on our own mail server, but you can use the SMTP servers of the KU Leuven. Because you should only be able to send mails from an email address you actually own, make sure that you configured receiving mails before starting this process. Gmail will send a confirmation mail to the provided email address to confirm that you own it. # In Gmail, click on the gear icon at the top right. # Click '''See all settings''' (Dutch: '''Alle instellingen bekijken'''). # Go to the tab '''Accounts and Import''' (Dutch: '''Accounts en import'''). # Under '''Send mail as:''' (Dutch: '''Mail verzenden als:'''), click on: '''Add another email address''' (Dutch: '''Nog een e-mailadres toevoegen'''). # Fill in the email address you want to send from, and check '''Treat as an alias.''' (Dutch: '''Beschouwen als alias.''') More info: https://support.google.com/a/answer/1710338 # Optionally: Enter a '''Name''', the recipient will see this name instead of or next to your email address. # Click on '''Next step''' (Dutch: '''Volgende stap'''). # Fill in the [https://admin.kuleuven.be/icts/english/services/email/imap-configuratie-en KU Leuven SMTP information] ([https://admin.kuleuven.be/icts/services/email/imap-configuratie Dutch]): #*'''SMTP server''': '''smtps.kuleuven.be''' #* '''Port''': '''465''' #* '''Username''': your KU Leuven intranet userid r or u-number e.g. r0123456 #* '''Password''': your central KU Leuven password #* '''Secured connection using''': '''SSL''' # Click on the '''Add Account''' (Dutch: '''Account toevoegen''') button. # Confirm your request using the link or code, you just received via an email on the address you provided. You can now send emails in Gmail from this address: # In Gmail, click '''Compose''' (Dutch: '''Opstellen'''). # Click on the email address next to '''From''' (Dutch: '''Van'''). # Select the email address you want to send from. [[Category:Mail]] 90648e6e886c5cd727aa2ca200db07688735db48 0 29 1715 1534 2022-07-21T18:05:03Z Bert 8 wikitext text/x-wiki To register an account, follow these steps: [[File:UCC Request New Account.png|thumb|right]] * Go to https://ucc.ulyssis.org/accounts and log in using your Central KU Leuven Account. * Select the kind of account you wish to register: ** Most people will want to register a '''regular account''' for '''personal use'''. ** If you are a recognised '''faculty union''' (kring), assembly or '''faculty consultative bodies''' (facultair overlegorgaan) you are entitled to this free account. We verify this using the list of recognised faculty unions (kringen) from LOKO on http://loko.be/verenigingen/ and list of recognised faculty consultative bodies from the Studentenraad KU Leuven on https://www.sturakuleuven.be/onze-werking/facultaire-overlegorganen/ . Recognised organisations are not entitled to a free account (see below). ** If you are a '''recognised organisation''' by LOKO or the KU Leuven itself you are entitled to an organisation account, which has a reduced price. We verify this using the list of associations (vrije verenigingen) recognised by [http://loko.be/verenigingen/ LOKO] and the list of recognised cultural organisations by the [https://admin.kuleuven.be/td/fd/le/culturele-verenigingen-erkend-door-de-cultuurcommissie KU Leuven Culture Committee]. Sports organisations recognised by the University Sports Centre can get in contact with us directly with proof of their recognition, as the USC currently doesn't publish any lists. We do ''not'' recognise the organisations recognised by the [https://admin.kuleuven.be/td/fd/le/politieke-en-andere-verenigingen-erkend-door-het-gebu General Bureau] (GeBu) of the KU Leuven. ** If you are a '''campus council''' or an organisation '''not''' part of '''campus Leuven''', such as the councils and organisations listed on https://www.sturakuleuven.be/onze-werking/campusraden/ , then you are not eligible for any reduced fee accounts, but you are free to register a personal account. If you are a campus council, you can also reach out to us on ulyssis@ulyssis.org to discuss subsidising reduced fee access for the organisations of your campus. * After picking your account type you have to choose which options you want, as well as a username and a language. * Accept the ULYSSIS terms of use and confirm your order. * An email will be sent to your KU Leuven email address to confirm your order alongside a request for payment. * As soon as we have received and processed your payment, your account will be activated and you will receive instructions to set a password. [[Category:Account]] 2d693d68fe6923d5e86ac5efe0b0eafeab2e5f58 1716 1715 2022-07-21T19:09:51Z Bert 8 wikitext text/x-wiki To register an account, follow these steps: * Go to https://ucc.ulyssis.org/accounts and log in using your Central KU Leuven Account. * Select the kind of account you wish to register: ** Most people will want to register a '''regular account''' for '''personal use'''. ** If you are a recognised '''faculty union''' (kring), assembly or '''faculty consultative bodies''' (facultair overlegorgaan) you are entitled to this free account. We verify this using the list of recognised faculty unions (kringen) from LOKO on http://loko.be/verenigingen/ and list of recognised faculty consultative bodies from the Studentenraad KU Leuven on https://www.sturakuleuven.be/onze-werking/facultaire-overlegorganen/ . Recognised organisations are not entitled to a free account (see below). ** If you are a '''recognised organisation''' by LOKO or the KU Leuven itself you are entitled to an organisation account, which has a reduced price. We verify this using the list of associations (vrije verenigingen) recognised by [http://loko.be/verenigingen/ LOKO] and the list of recognised cultural organisations by the [https://admin.kuleuven.be/td/fd/le/culturele-verenigingen-erkend-door-de-cultuurcommissie KU Leuven Culture Committee]. Sports organisations recognised by the University Sports Centre can get in contact with us directly with proof of their recognition, as the USC currently doesn't publish any lists. We do ''not'' recognise the organisations recognised by the [https://admin.kuleuven.be/td/fd/le/politieke-en-andere-verenigingen-erkend-door-het-gebu General Bureau] (GeBu) of the KU Leuven. ** If you are a '''campus council''' or an organisation '''not''' part of '''campus Leuven''', such as the councils and organisations listed on https://www.sturakuleuven.be/onze-werking/campusraden/ , then you are not eligible for any reduced fee accounts, but you are free to register a personal account. If you are a campus council, you can also reach out to us on ulyssis@ulyssis.org to discuss subsidising reduced fee access for the organisations of your campus. * After picking your account type you have to choose which options you want, as well as a username and a language. * Accept the ULYSSIS terms of use and confirm your order. * An email will be sent to your KU Leuven email address to confirm your order alongside a request for payment. * As soon as we have received and processed your payment, your account will be activated and you will receive instructions to set a password. [[Category:Account]] 8705e0c7f4151997e0da7a2aa81d0888b2bf9f0f 1717 1716 2022-07-21T20:31:25Z Bert 8 wikitext text/x-wiki To register an account, follow these steps: * Go to https://ucc.ulyssis.org/accounts and log in using your Central KU Leuven Account. * Select the kind of account you wish to register: ** Most people will want to register a '''regular account''' for '''personal use'''. ** If you are a recognised '''faculty union''' (kring), assembly or '''faculty consultative bodies''' (facultair overlegorgaan) you are entitled to a free account. You can use the following to verify if you are eligible: *** The list of recognised faculty unions (kringen) from LOKO on http://loko.be/verenigingen/. Recognised organisations (vrije verenigingen) are not entitled to a free account, but can get a reduced price account (see below). *** The list of recognised faculty consultative bodies from the Studentenraad KU Leuven on https://www.sturakuleuven.be/onze-werking/facultaire-overlegorganen/. ** If you are a '''recognised organisation''' by LOKO, the KU Leuven or another relevant entity, you may be entitled to an organisation account, which has a reduced price. You can use the following to verify if you are eligible: *** The list of associations (vrije verenigingen) recognised by [http://loko.be/verenigingen/ LOKO]. *** The list of recognised cultural organisations by the [https://admin.kuleuven.be/td/fd/le/culturele-verenigingen-erkend-door-de-cultuurcommissie KU Leuven Culture Committee]. *** If you are a daughter organisation of one or multiple faculty unions (kringen), for example a fakbar. *** Sports organisations recognised by the University Sports Centre can get in contact with us directly with proof of their recognition, as the USC currently doesn't publish any lists. *** KU Leuven research groups. Please email us on ulyssis@ulyssis.org with a link to your faculty/department's list of research groups. *** Organisations recognised by their faculty as an (optional) part of the curriculum and that have a permanent character. For example the [https://iiw.kuleuven.be/studeren/opleidingen/techinvent/ventures-teams teams] of the Postgraduate Tech Innovations in Ventures & Teams at Group T. *** We do ''not'' recognise the organisations recognised by the [https://admin.kuleuven.be/td/fd/le/politieke-en-andere-verenigingen-erkend-door-het-gebu General Bureau] (GeBu) of the KU Leuven. ** If you are a '''campus council''' or an organisation '''not''' part of '''campus Leuven''', such as the councils and organisations listed on https://www.sturakuleuven.be/onze-werking/campusraden/ , then you are not eligible for any reduced fee accounts, but you are free to register a personal account. If you are a campus council, you can also reach out to us on ulyssis@ulyssis.org to discuss subsidising reduced fee access for the organisations of your campus. * After picking your account type you have to choose which options you want, as well as a username and a language. * Accept the ULYSSIS terms of use and confirm your order. * An email will be sent to your KU Leuven email address to confirm your order alongside a request for payment. * As soon as we have received and processed your payment, your account will be activated and you will receive instructions to set a password. [[Category:Account]] d41b2d669bf9416160bac747e5ef6d8364cfe7e2 1718 1717 2022-07-21T20:35:43Z Bert 8 wikitext text/x-wiki To register an account, follow these steps: # Go to https://ucc.ulyssis.org/accounts and log in using your Central KU Leuven Account. # Select the kind of account you wish to register: #* Most people will want to register a '''regular account''' for '''personal use'''. #* If you are a recognised '''faculty union''' (kring), assembly or '''faculty consultative bodies''' (facultair overlegorgaan) you are entitled to a free account. You can use the following to verify if you are eligible: #** The list of recognised faculty unions (kringen) from LOKO on http://loko.be/verenigingen/. Recognised organisations (vrije verenigingen) are not entitled to a free account, but can get a reduced price account (see below). #** The list of recognised faculty consultative bodies from the Studentenraad KU Leuven on https://www.sturakuleuven.be/onze-werking/facultaire-overlegorganen/. #* If you are a '''recognised organisation''' by LOKO, the KU Leuven or another relevant entity, you may be entitled to an organisation account, which has a reduced price. You can use the following to verify if you are eligible: #** The list of associations (vrije verenigingen) recognised by [http://loko.be/verenigingen/ LOKO]. #** The list of recognised cultural organisations by the [https://admin.kuleuven.be/td/fd/le/culturele-verenigingen-erkend-door-de-cultuurcommissie KU Leuven Culture Committee]. #** If you are a daughter organisation of one or multiple faculty unions (kringen), for example a fakbar. #** Sports organisations recognised by the University Sports Centre can get in contact with us directly with proof of their recognition, as the USC currently doesn't publish any lists. #** KU Leuven research groups. Please email us on ulyssis@ulyssis.org with a link to your faculty/department's list of research groups. #** Organisations recognised by their faculty as an (optional) part of the curriculum and that have a permanent character. For example the [https://iiw.kuleuven.be/studeren/opleidingen/techinvent/ventures-teams teams] of the Postgraduate Tech Innovations in Ventures & Teams at Group T. #** We do ''not'' recognise the organisations recognised by the [https://admin.kuleuven.be/td/fd/le/politieke-en-andere-verenigingen-erkend-door-het-gebu General Bureau] (GeBu) of the KU Leuven. #* If you are a '''campus council''' or an organisation '''not''' part of '''campus Leuven''', such as the councils and organisations listed on https://www.sturakuleuven.be/onze-werking/campusraden/ , then you are not eligible for any reduced fee accounts, but you are free to register a personal account. If you are a campus council, you can also reach out to us on ulyssis@ulyssis.org to discuss subsidising reduced fee access for the organisations of your campus. # After picking your account type you have to choose which options you want, as well as a username and a language. # Accept the ULYSSIS terms of use and confirm your order. # An email will be sent to your KU Leuven email address to confirm your order alongside a request for payment. # As soon as we have received and processed your payment, your account will be activated and you will receive instructions to set a password. [[Category:Account]] 1aae02dd36906bdfc55c0714da719f9d9e33a934 1719 1718 2022-07-21T20:49:40Z Bert 8 wikitext text/x-wiki To register an account, follow these steps: # Go to https://ucc.ulyssis.org/accounts and log in using your Central KU Leuven Account. # Select the kind of account you wish to register: #* Most people will want to register a '''regular account''' for '''personal use'''. #* If you are a recognised '''faculty union''' (kring), assembly (overloepelende vereniging) or '''faculty consultative bodies''' (facultair overlegorgaan) you are entitled to a free account. You can use the following to verify if you are eligible: #** The list of recognised faculty unions (kringen) from LOKO on http://loko.be/verenigingen/. Recognised organisations (vrije verenigingen) are not entitled to a free account, but can get a reduced price account (see below). #** The list of recognised assemblies (overkoepelende verenigingen) on the [https://kennisdatabank.loko.be/index.php/Studentenorganisaties_in_Leuven#Overkoepelende_organisaties LOKO knowledge database]. #** The list of recognised faculty consultative bodies from the Studentenraad KU Leuven on https://www.sturakuleuven.be/onze-werking/facultaire-overlegorganen/. #* If you are a '''recognised organisation''' by LOKO, the KU Leuven or another relevant entity, you may be entitled to an organisation account, which has a reduced price. You can use the following to verify if you are eligible: #** The list of associations (vrije verenigingen) recognised by [http://loko.be/verenigingen/ LOKO]. #** The list of recognised cultural organisations by the [https://admin.kuleuven.be/td/fd/le/culturele-verenigingen-erkend-door-de-cultuurcommissie KU Leuven Culture Committee]. #** If you are a daughter organisation of one or multiple faculty unions (kringen), for example a fakbar. #** Sports organisations recognised by the University Sports Centre can get in contact with us directly with proof of their recognition, as the USC currently doesn't publish any lists. #** KU Leuven research groups. Please email us on ulyssis@ulyssis.org with a link to your faculty/department's list of research groups. #** Organisations recognised by their faculty as an (optional) part of the curriculum and that have a permanent character. For example the [https://iiw.kuleuven.be/studeren/opleidingen/techinvent/ventures-teams teams] of the Postgraduate Tech Innovations in Ventures & Teams at Group T. #** We do ''not'' recognise the organisations recognised by the [https://admin.kuleuven.be/td/fd/le/politieke-en-andere-verenigingen-erkend-door-het-gebu General Bureau] (GeBu) of the KU Leuven. #* If you are a '''campus council''' or an organisation '''not''' part of '''campus Leuven''', such as the councils and organisations listed on https://www.sturakuleuven.be/onze-werking/campusraden/ , then you are not eligible for any reduced fee accounts, but you are free to register a personal account. If you are a campus council, you can also reach out to us on ulyssis@ulyssis.org to discuss subsidising reduced fee access for the organisations of your campus. # After picking your account type you have to choose which options you want, as well as a username and a language. # Accept the ULYSSIS terms of use and confirm your order. # An email will be sent to your KU Leuven email address to confirm your order alongside a request for payment. # As soon as we have received and processed your payment, your account will be activated and you will receive instructions to set a password. [[Category:Account]] 83aafb2fad1cbb674463b1ee059f622728591cd1 1720 1719 2022-07-21T21:01:23Z Bert 8 wikitext text/x-wiki To register an account, follow these steps: # Go to https://ucc.ulyssis.org/accounts and log in using your Central KU Leuven Account. # Select the kind of account you wish to register: #* Most people will want to register a '''regular account''' for '''personal use'''. #* If you are a recognised '''faculty union''' (kring), assembly (overloepelende vereniging) or '''faculty consultative bodies''' (facultair overlegorgaan) you are entitled to a free account. You can use the following to verify if you are eligible: #** The list of recognised faculty unions (kringen) from LOKO on http://loko.be/verenigingen/. Recognised organisations (vrije verenigingen) are not entitled to a free account, but can get a reduced price account (see below). #** The list of recognised assemblies (overkoepelende verenigingen) on the [https://kennisdatabank.loko.be/index.php/Studentenorganisaties_in_Leuven#Overkoepelende_organisaties LOKO knowledge database]. #** The list of recognised faculty consultative bodies from the Studentenraad KU Leuven on https://www.sturakuleuven.be/onze-werking/facultaire-overlegorganen/. #* If you are a '''recognised organisation''' by LOKO, the KU Leuven or another relevant entity, you may be entitled to an organisation account, which has a reduced price. You can use the following to verify if you are eligible: #** The list of associations (vrije verenigingen) recognised by [http://loko.be/verenigingen/ LOKO]. #** The list of recognised cultural organisations by the [https://admin.kuleuven.be/td/fd/le/culturele-verenigingen-erkend-door-de-cultuurcommissie KU Leuven Culture Committee]. #** If you are a daughter organisation of one or multiple faculty unions (kringen), for example a fakbar. #** Sports organisations recognised by the University Sports Centre can get in contact with us directly with proof of their recognition, as the USC currently doesn't publish any lists. #** KU Leuven research groups. Please email us on ulyssis@ulyssis.org with a link to your faculty/department's list of research groups. #** Organisations recognised by their faculty as an (optional) part of the curriculum and that have a permanent character. For example the [https://iiw.kuleuven.be/studeren/opleidingen/techinvent/ventures-teams teams] of the Postgraduate Tech Innovations in Ventures & Teams at Group T. #** We do ''not'' recognise the organisations recognised by the [https://admin.kuleuven.be/td/fd/le/politieke-en-andere-verenigingen-erkend-door-het-gebu General Bureau] (GeBu) of the KU Leuven. #** If your organisation is recognised by some other entity not listed here, feel free to send us more details on ulyssis@ulyssis.org and we will review your particular situation. #* If you are a '''campus council''' or an organisation '''not''' part of '''campus Leuven''', such as the councils and organisations listed on https://www.sturakuleuven.be/onze-werking/campusraden/ , then you are not eligible for any reduced fee accounts, but you are free to register a personal account. If you are a campus council, you can also reach out to us on ulyssis@ulyssis.org to discuss subsidising reduced fee access for the organisations of your campus. # After picking your account type you have to choose which options you want, as well as a username and a language. # Accept the ULYSSIS terms of use and confirm your order. # An email will be sent to your KU Leuven email address to confirm your order alongside a request for payment. # As soon as we have received and processed your payment, your account will be activated and you will receive instructions to set a password. [[Category:Account]] 265a21a0020a627519f4724b4f8a8a674a988354 1721 1720 2022-07-21T21:02:17Z Bert 8 wikitext text/x-wiki To register an account, follow these steps: # Go to https://ucc.ulyssis.org/accounts and log in using your Central KU Leuven Account. # Select the kind of account you wish to register: #* Most people will want to register a '''regular account''' for '''personal use'''. #* If you are a recognised '''faculty union''' (kring), assembly (overloepelende vereniging) or '''faculty consultative bodies''' (facultair overlegorgaan) you are entitled to a free account. You can use the following to verify if you are eligible: #** The list of recognised faculty unions (kringen) from LOKO on http://loko.be/verenigingen/. Recognised organisations (vrije verenigingen) are not entitled to a free account, but can get a reduced price account (see below). #** The list of recognised assemblies (overkoepelende verenigingen) on the [https://kennisdatabank.loko.be/index.php/Studentenorganisaties_in_Leuven#Overkoepelende_organisaties LOKO knowledge database]. #** The list of recognised faculty consultative bodies from the Studentenraad KU Leuven on https://www.sturakuleuven.be/onze-werking/facultaire-overlegorganen/. #* If you are a '''recognised organisation''' by LOKO, the KU Leuven or another relevant entity, you may be entitled to an organisation account, which has a reduced price. You can use the following to verify if you are eligible: #** The list of associations (vrije verenigingen) recognised by [http://loko.be/verenigingen/ LOKO]. #** The list of recognised cultural organisations by the [https://admin.kuleuven.be/td/fd/le/culturele-verenigingen-erkend-door-de-cultuurcommissie KU Leuven Culture Committee]. #** If you are a daughter organisation of one or multiple faculty unions (kringen), for example a fakbar. #** Sports organisations recognised by the University Sports Centre can get in contact with us directly with proof of their recognition, as the USC currently doesn't publish any lists. #** KU Leuven research groups. Please email us on [mailto:ulyssis@ulyssis.org] with a link to your faculty/department's list of research groups. #** Organisations recognised by their faculty as an (optional) part of the curriculum and that have a permanent character. For example the [https://iiw.kuleuven.be/studeren/opleidingen/techinvent/ventures-teams teams] of the Postgraduate Tech Innovations in Ventures & Teams at Group T. #** We do ''not'' recognise the organisations recognised by the [https://admin.kuleuven.be/td/fd/le/politieke-en-andere-verenigingen-erkend-door-het-gebu General Bureau] (GeBu) of the KU Leuven. #** If your organisation is recognised by some other entity not listed here, feel free to send us more details on [mailto:ulyssis@ulyssis.org] and we will review your particular situation. #* If you are a '''campus council''' or an organisation '''not''' part of '''campus Leuven''', such as the councils and organisations listed on https://www.sturakuleuven.be/onze-werking/campusraden/ , then you are not eligible for any reduced fee accounts, but you are free to register a personal account. If you are a campus council, you can also reach out to us on [mailto:ulyssis@ulyssis.org] to discuss subsidising reduced fee access for the organisations of your campus. # After picking your account type you have to choose which options you want, as well as a username and a language. # Accept the ULYSSIS terms of use and confirm your order. # An email will be sent to your KU Leuven email address to confirm your order alongside a request for payment. # As soon as we have received and processed your payment, your account will be activated and you will receive instructions to set a password. [[Category:Account]] 5de2017677937c5d9b46294500b0b02ea6737797 1722 1721 2022-07-21T21:02:48Z Bert 8 wikitext text/x-wiki To register an account, follow these steps: # Go to https://ucc.ulyssis.org/accounts and log in using your Central KU Leuven Account. # Select the kind of account you wish to register: #* Most people will want to register a '''regular account''' for '''personal use'''. #* If you are a recognised '''faculty union''' (kring), assembly (overloepelende vereniging) or '''faculty consultative bodies''' (facultair overlegorgaan) you are entitled to a free account. You can use the following to verify if you are eligible: #** The list of recognised faculty unions (kringen) from LOKO on http://loko.be/verenigingen/. Recognised organisations (vrije verenigingen) are not entitled to a free account, but can get a reduced price account (see below). #** The list of recognised assemblies (overkoepelende verenigingen) on the [https://kennisdatabank.loko.be/index.php/Studentenorganisaties_in_Leuven#Overkoepelende_organisaties LOKO knowledge database]. #** The list of recognised faculty consultative bodies from the Studentenraad KU Leuven on https://www.sturakuleuven.be/onze-werking/facultaire-overlegorganen/. #* If you are a '''recognised organisation''' by LOKO, the KU Leuven or another relevant entity, you may be entitled to an organisation account, which has a reduced price. You can use the following to verify if you are eligible: #** The list of associations (vrije verenigingen) recognised by [http://loko.be/verenigingen/ LOKO]. #** The list of recognised cultural organisations by the [https://admin.kuleuven.be/td/fd/le/culturele-verenigingen-erkend-door-de-cultuurcommissie KU Leuven Culture Committee]. #** If you are a daughter organisation of one or multiple faculty unions (kringen), for example a fakbar. #** Sports organisations recognised by the University Sports Centre can get in contact with us directly with proof of their recognition, as the USC currently doesn't publish any lists. #** KU Leuven research groups. Please email us on mailto:ulyssis@ulyssis.org with a link to your faculty/department's list of research groups. #** Organisations recognised by their faculty as an (optional) part of the curriculum and that have a permanent character. For example the [https://iiw.kuleuven.be/studeren/opleidingen/techinvent/ventures-teams teams] of the Postgraduate Tech Innovations in Ventures & Teams at Group T. #** We do ''not'' recognise the organisations recognised by the [https://admin.kuleuven.be/td/fd/le/politieke-en-andere-verenigingen-erkend-door-het-gebu General Bureau] (GeBu) of the KU Leuven. #** If your organisation is recognised by some other entity not listed here, feel free to send us more details on mailto:ulyssis@ulyssis.org and we will review your particular situation. #* If you are a '''campus council''' or an organisation '''not''' part of '''campus Leuven''', such as the councils and organisations listed on https://www.sturakuleuven.be/onze-werking/campusraden/ , then you are not eligible for any reduced fee accounts, but you are free to register a personal account. If you are a campus council, you can also reach out to us on mailto:ulyssis@ulyssis.org to discuss subsidising reduced fee access for the organisations of your campus. # After picking your account type you have to choose which options you want, as well as a username and a language. # Accept the ULYSSIS terms of use and confirm your order. # An email will be sent to your KU Leuven email address to confirm your order alongside a request for payment. # As soon as we have received and processed your payment, your account will be activated and you will receive instructions to set a password. [[Category:Account]] a7fd30180789cffb364c82c64d98d811d5e07234 1723 1722 2022-07-21T21:03:22Z Bert 8 wikitext text/x-wiki To register an account, follow these steps: # Go to https://ucc.ulyssis.org/accounts and log in using your Central KU Leuven Account. # Select the kind of account you wish to register: #* Most people will want to register a '''regular account''' for '''personal use'''. #* If you are a recognised '''faculty union''' (kring), assembly (overloepelende vereniging) or '''faculty consultative bodies''' (facultair overlegorgaan) you are entitled to a free account. You can use the following to verify if you are eligible: #** The list of recognised faculty unions (kringen) from LOKO on http://loko.be/verenigingen/. Recognised organisations (vrije verenigingen) are not entitled to a free account, but can get a reduced price account (see below). #** The list of recognised assemblies (overkoepelende verenigingen) on the [https://kennisdatabank.loko.be/index.php/Studentenorganisaties_in_Leuven#Overkoepelende_organisaties LOKO knowledge database]. #** The list of recognised faculty consultative bodies from the Studentenraad KU Leuven on https://www.sturakuleuven.be/onze-werking/facultaire-overlegorganen/. #* If you are a '''recognised organisation''' by LOKO, the KU Leuven or another relevant entity, you may be entitled to an organisation account, which has a reduced price. You can use the following to verify if you are eligible: #** The list of associations (vrije verenigingen) recognised by [http://loko.be/verenigingen/ LOKO]. #** The list of recognised cultural organisations by the [https://admin.kuleuven.be/td/fd/le/culturele-verenigingen-erkend-door-de-cultuurcommissie KU Leuven Culture Committee]. #** If you are a daughter organisation of one or multiple faculty unions (kringen), for example a fakbar. #** Sports organisations recognised by the University Sports Centre can get in contact with us directly with proof of their recognition, as the USC currently doesn't publish any lists. #** KU Leuven research groups. Please email us on [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org] with a link to your faculty/department's list of research groups. #** Organisations recognised by their faculty as an (optional) part of the curriculum and that have a permanent character. For example the [https://iiw.kuleuven.be/studeren/opleidingen/techinvent/ventures-teams teams] of the Postgraduate Tech Innovations in Ventures & Teams at Group T. #** We do ''not'' recognise the organisations recognised by the [https://admin.kuleuven.be/td/fd/le/politieke-en-andere-verenigingen-erkend-door-het-gebu General Bureau] (GeBu) of the KU Leuven. #** If your organisation is recognised by some other entity not listed here, feel free to send us more details on [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org] and we will review your particular situation. #* If you are a '''campus council''' or an organisation '''not''' part of '''campus Leuven''', such as the councils and organisations listed on https://www.sturakuleuven.be/onze-werking/campusraden/ , then you are not eligible for any reduced fee accounts, but you are free to register a personal account. If you are a campus council, you can also reach out to us on [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org] to discuss subsidising reduced fee access for the organisations of your campus. # After picking your account type you have to choose which options you want, as well as a username and a language. # Accept the ULYSSIS terms of use and confirm your order. # An email will be sent to your KU Leuven email address to confirm your order alongside a request for payment. # As soon as we have received and processed your payment, your account will be activated and you will receive instructions to set a password. [[Category:Account]] 949c0499975e11b663c8d34b37da3363b1a1980d 1724 1723 2022-07-21T22:20:39Z Simon 36 wikitext text/x-wiki To register an account, follow these steps: # Go to https://ucc.ulyssis.org/accounts and log in using your Central KU Leuven Account. # Select the kind of account you wish to register: #* Most people will want to register a '''regular account''' for '''personal use'''. #* If you are a recognised '''faculty union''' (kring), assembly organisation (overkoepelende organisatie), or '''faculty consultative body''' (facultair overlegorgaan) you are entitled to a free account. You can use the following to verify if you are eligible: #** The list of recognised faculty unions (kringen) from LOKO on http://loko.be/verenigingen/. Recognised organisations (vrije verenigingen) are not entitled to a free account, but can get a reduced price account (see below). #** The list of recognised assembly organisations (overkoepelende organisaties) on the [https://kennisdatabank.loko.be/index.php/Studentenorganisaties_in_Leuven#Overkoepelende_organisaties LOKO knowledge database]. #** The list of recognised faculty consultative bodies from the Studentenraad KU Leuven on https://www.sturakuleuven.be/onze-werking/facultaire-overlegorganen/. #* If you are a '''recognised organisation''' by LOKO, the KU Leuven or another relevant entity, you may be entitled to an organisation account, which has a reduced price. You can use the following to verify if you are eligible: #** The list of associations (vrije verenigingen) recognised by [http://loko.be/verenigingen/ LOKO]. #** The list of recognised cultural organisations by the [https://admin.kuleuven.be/td/fd/le/culturele-verenigingen-erkend-door-de-cultuurcommissie KU Leuven Culture Committee]. #** If you are a daughter organisation of one or multiple faculty unions (kringen), for example a fakbar. #** Sports organisations recognised by the University Sports Centre can get in contact with us directly with proof of their recognition, as the USC currently doesn't publish any lists. #** KU Leuven research groups. Please email us on [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org] with a link to your faculty/department's list of research groups. #** Organisations recognised by their faculty as an (optional) part of the curriculum and that have a permanent character. For example the [https://iiw.kuleuven.be/studeren/opleidingen/techinvent/ventures-teams teams] of the Postgraduate Tech Innovations in Ventures & Teams at Group T. #** We do ''not'' recognise the organisations recognised by the [https://admin.kuleuven.be/td/fd/le/politieke-en-andere-verenigingen-erkend-door-het-gebu General Bureau] (GeBu) of the KU Leuven. #** If your organisation is recognised by some other entity not listed here, feel free to send us more details on [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org] and we will review your particular situation. #* If you are a '''campus council''' or an organisation '''not''' part of '''campus Leuven''', such as the councils and organisations listed on https://www.sturakuleuven.be/onze-werking/campusraden/ , then you are not eligible for any reduced fee accounts, but you are free to register a personal account. If you are a campus council, you can also reach out to us on [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org] to discuss subsidising reduced fee access for the organisations of your campus. # After picking your account type you have to choose which options you want, as well as a username and a language. # Accept the ULYSSIS terms of use and confirm your order. # An email will be sent to your KU Leuven email address to confirm your order alongside a request for payment. # As soon as we have received and processed your payment, your account will be activated and you will receive instructions to set a password. [[Category:Account]] 543107f780af86be9551f0535e039dc10c65068b 0 77 1725 1524 2022-08-14T23:09:45Z Bert 8 wikitext text/x-wiki You may want to send e-mail from Thunderbird using your @ulyssis.org address, or another domain name that you use for your account. Thunderbird allows you to do this, but to configure this properly, you should not use your provider's SMTP server. They will add an extra header stating the original e-mail address the e-mail is sent from. Some e-mail clients show this information, which might be unwanted. The KU Leuven also provides an SMTP server which you can use as a student. It accepts e-mail originating from any e-mail adress, and can therefore be used for this purpose. It should be noted that this is an '''authenticated''' server, so any potential abuse can be tracked back to you. You should '''not''' use this for any malicious purpose. == Adding the KU Leuven SMTP server in Thunderbird == If you already have set up your KU Leuven e-mail in Thunderbird, you can skip this step and proceed to [[#Configure an identity for your e-mail account|Configure an identity for your e-mail account]] below. Go to your '''Account Settings''' (Edit > Account Settings or Tools > Account Settings, depending on your operating system). At the bottom of the left sidebar, you will find an entry named '''Outgoing Server (SMTP)'''. Click this to access your SMTP settings. In your SMTP settings, you should see a list of existing SMTP servers. We want to add a new entry, so click the '''Add...''' button. In the screen that pops up, fill in the settings of the KU Leuven SMTP server, using the example screenshot below based on the [https://admin.kuleuven.be/icts/english/services/email/imap-configuratie-en official ICTS documentation]. Replace the displayed user name with your own KULid (m/r/s/u number). You will have to fill in the corresponding password on first use. [[File:Thunderbird-SMTPS.png]] == Configure an identity for your e-mail account == Back in the '''Account Settings''' screen, click on your e-mail address (not on any of its children). In the screen that opens, there will be a button '''Manage Identities...''' at the bottom. Click it. In the new screen, there will be one existing identity already: the default identity corresponding with your normal e-mail address. We want to add a new identity, so click the '''Add...''' button. In the screen that pops up, fill in the name and e-mail address you wish to use. At the bottom, make sure you choose the SMTP server of your KULid. This is shown in the image below. [[File:Thunderbird-Identity.png]] If you're adding an identity for a group alias, you may also want to automatically send a copy of any replies or emails you're sending to the alias itself to make sure all others are aware of it. To do that, enable the BCC checkbox under the '''Copies & Folders''' tab. It should automatically contain the alias. == Sending your first e-mail == When you compose a new e-mail, you can change the sender in the "From" field to the identity you just configured. If everything was installed correctly, Thunderbird will show you a pop-up to enter your KU Leuven password when you try to send the e-mail. In this pop-up, you can choose to save this password for later use. [[Category:Mail]] c7d6caf166cc51c335dbc3d8e604d3196fdf2a09 0 249 1727 2022-08-14T23:11:08Z Bert 8 Created page with "By default you can already use your @ulyssis.org email address to send emails using our webmail, but you may also want to send email from another domain name that you use for..." wikitext text/x-wiki By default you can already use your @ulyssis.org email address to send emails using our webmail, but you may also want to send email from another domain name that you use for your account. You can simply configure this using the steps below. # Login into the [https://webmail.ulyssis.org webinterface] using your ulyssis account and passsword # Go to '''Settings''' (dutch: '''Instellingen''') in the top right # Go to '''Identities''' (dutch: '''Identiteiten''') # Click on the plus sign in the bottom left # Fill the alias you want to use in in the '''Email''' (dutch: '''E-mail''') field and the name you want to be displayed in front of the address in the '''Display Name''' (dutch: '''Weergavenaam''') field. All the other fields are optional. # Click on '''Save''' (dutch: '''Opslaan''') You can now select the alias when creating an email in the webinterface. [[Category:Mail]] 0e4b31d7d678dfcd2dd980120029b44d4adfc826 1731 1727 2022-08-14T23:25:49Z Bert 8 wikitext text/x-wiki By default you can already use your @ulyssis.org email address to send emails using our webmail, but you may also want to send email from another domain name that you use for your account. You can simply configure this using the steps below. # Login into the [https://webmail.ulyssis.org webinterface] using your ULYSSIS account name and passsword # Go to '''Settings''' (dutch: '''Instellingen''') in the top right # Go to '''Identities''' (dutch: '''Identiteiten''') # Click on the plus sign in the bottom left # Fill the alias you want to use in in the '''Email''' (dutch: '''E-mail''') field and the name you want to be displayed in front of the address in the '''Display Name''' (dutch: '''Weergavenaam''') field. All the other fields are optional. # Click on '''Save''' (dutch: '''Opslaan''') You can now select the alias when composing an email in the webinterface. [[Category:Mail]] 5151a8752c42146feb67592cb249cd26892c4259 0 80 1728 726 2022-08-14T23:16:51Z Bert 8 wikitext text/x-wiki If you have your own domain, it's very easy to use [[Forwarders]] to forward email from addresses under your own domain to other email addresses at external providers or your ULYSSIS mailbox. While you can always reply with the address of that external provider or the @ulyssis.org address of your mailbox, it's often preferred to also use the address of your own domain when replying to messages or starting conversations. In that case you will want to configure an alias for your forwarder. While you are free to use whatever provider, email application or webmail application you prefer, we have step-by-step manuals available for some specific case. You can find them listed here: * [[Add an alias in ULYSSIS webmail]] * [[Add an alias in Thunderbird]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]]) [[Category:Mail]] a1a590fc2dc667e6ffd5f39ec61ab5b304a0a36e 1729 1728 2022-08-14T23:16:59Z Bert 8 wikitext text/x-wiki If you have your own domain, it's very easy to use [[Forwarders]] to forward email from addresses under your own domain to other email addresses at external providers or your ULYSSIS mailbox. While you can always reply with the address of that external provider or the @ulyssis.org address of your mailbox, it's often preferred to also use the address of your own domain when replying to messages or starting conversations. In that case you will want to configure an alias for your forwarder. While you are free to use whatever provider, email application or webmail application you prefer, we have step-by-step manuals available for some specific case. You can find them listed here: * [[Add an alias in ULYSSIS webmail]] * [[Add an alias in Thunderbird]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] [[Category:Mail]] 7a7e5cc5ba0ee566839d12bcb8947abfba411bee 0 3 1730 1667 2022-08-14T23:18:13Z Bert 8 /* Mail */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Reducing disk usage|Help, my account uses too much disk space]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Making Backups]] * [[Secure file permissions]] * [[Reducing disk usage]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2020]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Sending email from websites]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL/TLS|Getting SSL/TLS (HTTPS security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Claiming a port]] * [[ULYSSIS security measures]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Mailbox in Thunderbird]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Add_an_alias_in_ULYSSIS_webmail]] * [[Fetch your KU Leuven email into another email address]] * [[Spam]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up WordPress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] * [[Updating WordPress]] * [[Updating MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] * [[Using PHPPgAdmin]] * [[Using Adminer]] * [[Making Backups]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[Exporting your KU Leuven class schedule and calendar]] </div> <div style="clear:both;"></div> </div> __NOTOC__ afd672ad3f76a29ee25905937bf20426f2b7a63a 1732 1730 2022-08-14T23:31:25Z Bert 8 /* Mail */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Reducing disk usage|Help, my account uses too much disk space]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Making Backups]] * [[Secure file permissions]] * [[Reducing disk usage]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2020]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Sending email from websites]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL/TLS|Getting SSL/TLS (HTTPS security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Claiming a port]] * [[ULYSSIS security measures]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Mailbox in Thunderbird]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Add an alias in ULYSSIS webmail]] * [[Fetch your KU Leuven email into another email address]] * [[Spam]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up WordPress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] * [[Updating WordPress]] * [[Updating MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] * [[Using PHPPgAdmin]] * [[Using Adminer]] * [[Making Backups]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[Exporting your KU Leuven class schedule and calendar]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 099e3a7c01fe4a29d8a4b57f91f3ac23fe6e27f0 1752 1732 2022-09-16T20:23:25Z Bert 8 /* Webserver */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Reducing disk usage|Help, my account uses too much disk space]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Making Backups]] * [[Secure file permissions]] * [[Reducing disk usage]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2022]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Sending email from websites]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL/TLS|Getting SSL/TLS (HTTPS security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Claiming a port]] * [[ULYSSIS security measures]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Mailbox in Thunderbird]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Add an alias in ULYSSIS webmail]] * [[Fetch your KU Leuven email into another email address]] * [[Spam]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up WordPress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] * [[Updating WordPress]] * [[Updating MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] * [[Using PHPPgAdmin]] * [[Using Adminer]] * [[Making Backups]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[Exporting your KU Leuven class schedule and calendar]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 5683871f4fdae242e0ce4afe1ac1c8c8fcf7520c 6 250 1735 2022-08-15T14:38:41Z Erico 50 wikitext text/x-wiki config.php dropdown cyberduck 250eac02751d16110f50e12e61663989708dc7c7 6 251 1736 2022-08-15T14:40:21Z Erico 50 wikitext text/x-wiki config.php permissions cyberduck ca5f0abc8570701a0aaaec7fb09ca3b0e4f832b7 1737 1736 2022-08-15T14:44:06Z Erico 50 Erico uploaded a new version of [[File:Config-php-permissions.png]] wikitext text/x-wiki config.php permissions cyberduck ca5f0abc8570701a0aaaec7fb09ca3b0e4f832b7 6 252 1738 2022-08-15T14:47:34Z Erico 50 wikitext text/x-wiki uploads dropdown cyberduck 2a9ed3b85528b8d803b71e897691e2554c218904 6 253 1739 2022-08-15T14:48:10Z Erico 50 wikitext text/x-wiki uploads permissions cyberduck c3dbb18ca4bd8c5373f5fdd558fc2721f17f60b7 1741 1739 2022-08-15T14:51:15Z Erico 50 Erico uploaded a new version of [[File:Uploads-permissions.png]] wikitext text/x-wiki uploads permissions cyberduck c3dbb18ca4bd8c5373f5fdd558fc2721f17f60b7 0 104 1740 1194 2022-08-15T14:49:26Z Erico 50 updating to use cyberduck wikitext text/x-wiki PHP code is run with PHP-FPM as your ULYSSIS user. This means you can tighten up you website's security by denying other users the permission to read your PHP files. However, due to the way the Apache webserver works, it must be able to determine the existence of your PHP files. Non-PHP files in your www directory must remain readable by other users, because Apache reads these as it's own user. === Recommended permissions === * www directory (and other directories from where websites are served), including subdirectories: <code>0705/drwxr-xr-x</code> * Static website files (css, images, html, ...): <code>0604/-rw-r--r--</code> * Configuration files containing secrets/passwords: <code>0600/-rw-------</code> * Other directories and files that are not part of a website: <code>0600/-rw-------</code> or <code>0700/-rwx------</code> === Securing database login info === Suppose you have a file called <code>config.php</code>, containing login information for your database. To secure this information, you can make it readable and writeable by only you, and nobody else using <code>chmod 600 config.php</code>. In Cyberduck, you can do this by right-clicking on the config file, clicking on "Info", clicking on the "Permissions" tab, and changing the permissions according to the following screenshots: [[File:Config-php-dropdown.png]] [[File:Config-php-permissions.png]] === Securing uploads directory === Also, if there are directories that you made writeable by others, e.g. an uploads folder, this is no longer necessary. If this directory is called <code>uploads</code>, you can remove write rights for others with <code>chmod go-w uploads</code>. In Cyberduck, you can do this by right-clicking on the config file, clicking on "Info", clicking on the "Permissions" tab, and changing the permissions according to the following screenshots: [[File:Uploads-dropdown.png]] [[File:Uploads-permissions.png]] [[Category:Files]] [[Category:Security & anti-spam]] 5d50624349edeae39a401633e8a0f5a700a941ca 0 254 1742 2022-08-17T15:36:05Z Thomasd 40 Created page with "This page lists the changes to the webservers of ULYSSIS in the summer of 2022, and how you can prepare for it. If any of these instructions are not clear to you, or if you ha..." wikitext text/x-wiki This page lists the changes to the webservers of ULYSSIS in the summer of 2022, and how you can prepare for it. If any of these instructions are not clear to you, or if you have some more questions about the changes, '''don't hesitate to e-mail us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]'''. == When are the changes planned? == todo == What will change? == We will upgrade the Ubuntu release on our servers from 20.04 LTS to 22.04 LTS. This will include newer version of many services. An overview of the most important version changes can be found below. For other services/packages, you can always use the [https://packages.ubuntu.com/ Ubuntu Package Search]. The distribution name for Ubuntu 22.04 LTS is "jammy". * PHP will be updated from 7.4 to 8.1 * PostgreSQL will be updated from 12 to 14 * MariaDB (MySQL) will be updated from 10.3.22 to 10.6.7 * Python will be updated from 3.8 to 3.10 Note that any existing Python virtual environments in use will need to be recreated in order to function properly. b5a2a7435a6d700183a3c4fc20303a80b0b3663b 1750 1742 2022-09-05T23:34:31Z Thomasd 40 wikitext text/x-wiki This page lists the changes to the webservers of ULYSSIS in the summer of 2022, and how you can prepare for it. If any of these instructions are not clear to you, or if you have some more questions about the changes, '''don't hesitate to e-mail us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]'''. == When are the changes planned? == These changes are planned in the weekend of 17 and 18 September. == What will change? == We will upgrade the Ubuntu release on our servers from 20.04 LTS to 22.04 LTS. This will include newer version of many services. An overview of the most important version changes can be found below. For other services/packages, you can always use the [https://packages.ubuntu.com/ Ubuntu Package Search]. The distribution name for Ubuntu 22.04 LTS is "jammy". * PHP will be updated from 7.4 to 8.1. If you host your own PHP website, you might want to check out these guides: ** [https://www.php.net/manual/en/migration80.php Migrating from PHP 7.4.x to PHP 8.0.x] ** [https://www.php.net/manual/en/migration81.php Migrating from PHP 8.0.x to PHP 8.1.x] * PostgreSQL will be updated from 12 to 14 * MariaDB (MySQL) will be updated from 10.3.22 to 10.6.7 * Python will be updated from 3.8 to 3.10 Note that any existing Python virtual environments in use will need to be recreated in order to function properly. 4929e85601e0a4e12836d31825be98ea464282ed 1751 1750 2022-09-05T23:35:29Z Thomasd 40 wikitext text/x-wiki This page lists the changes to the webservers of ULYSSIS in the summer of 2022, and how you can prepare for it. If any of these instructions are not clear to you, or if you have some more questions about the changes, '''don't hesitate to e-mail us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]'''. == When are the changes planned? == These changes are planned in the weekend of 17 and 18 September. == What will change? == We will upgrade the Ubuntu release on our servers from 20.04 LTS to 22.04 LTS. This will include newer version of many services. An overview of the most important version changes can be found below. For other services/packages, you can always use the [https://packages.ubuntu.com/ Ubuntu Package Search]. The distribution name for Ubuntu 22.04 LTS is "jammy". * PHP will be updated from 7.4 to 8.1 * PostgreSQL will be updated from 12 to 14 * MariaDB (MySQL) will be updated from 10.3.22 to 10.6.7 * Python will be updated from 3.8 to 3.10 If you host your own PHP website, you might want to check out these guides: * [https://www.php.net/manual/en/migration80.php Migrating from PHP 7.4.x to PHP 8.0.x] * [https://www.php.net/manual/en/migration81.php Migrating from PHP 8.0.x to PHP 8.1.x] Note that any existing Python virtual environments in use will need to be recreated in order to function properly. 8950ce2d09dd2e40248e5e3fee2415c0fd5aef40 0 255 1743 2022-08-30T13:49:35Z Bert 8 Created page with "ULYSSIS is a non-profit student organisation with usually between 15 and 20 members. These members, most are students but some might have recently transitioned to a job or PhD..." wikitext text/x-wiki ULYSSIS is a non-profit student organisation with usually between 15 and 20 members. These members, most are students but some might have recently transitioned to a job or PhD, maintain our server hardware, make sure all the systems of our hosting run, answer support tickets, check security, organise events such as the [https://ctf.ulyssis.org ULYSSIS CTF] and [https://opensourcejobfair.be Open Source Job Fair], co-organise the [http://24urenloop.be 24 hour run], organise several [https://ulyssis.org/category/workshops/ workshops] a year, give technical advice and support to LOKO, and develop internal an external software tools such as [https://stemt.org Stemt.org]. As you can imagine, it's often already too large a task to do so many different things with such a small group of members. Even after automating as many of the tasks we have to do as possible, our team finds it challenging to take on long term projects such as replacing dated components of our hosting infrastructure, because we spend so much time answering support tickets. As you can imagine, hosting around 50 organisations and over 150 websites for students, staff and organisations at KU Leuven, means that it would be highly unrealistic if our members had to frequently intervene in existing websites or create complete new ones. We understand that it's a difficult task to create a new website and that maintenance can at times be challenging too. We also understand that your situation is very unique to your organisation or circumstances. We think however that it would be unfair if we would help some and not others. We therefore make lots of documentation available on this website, we give advice and help to look for solutions in support tickets, and we attempt to steer people towards easier maintenance. Specifically, we are convinced that WordPress offers the most user friendly way to create a website while retaining as much creative freedom as possible. Our manual [[Setting up WordPress]] details how the install WordPress in a few easy steps and includes screenshots to show you what to do. Installing is a one time thing, so once your website exists you will never need to do it again. What you will have to do is update WordPress and any themes and plugins you may use. Luckily, this can all be achieved by the press of a button. On our documentation page about [[Updating WordPress]] we explain how you can enable automatic updates for all components of your WordPress website. That way, you will usually never have to do any maintenance at all. For advice on how to build or maintain your website, you can of course always contact [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. 4cfb24230ecc3bc6740e5cd2622c687bada2b550 1744 1743 2022-08-30T13:50:14Z Bert 8 wikitext text/x-wiki ULYSSIS is a non-profit student organisation with usually between 15 and 20 members. These members, most are students but some might have recently transitioned to a job or PhD, maintain our server hardware, make sure all the systems of our hosting run, answer support tickets, check security, organise events such as the [https://ctf.ulyssis.org ULYSSIS CTF] and [https://opensourcejobfair.be Open Source Job Fair], co-organise the [http://24urenloop.be 24 hour run], organise several [https://ulyssis.org/category/workshops/ workshops] a year, give technical advice and support to LOKO, and develop internal an external software tools such as [https://stemt.org Stemt.org]. As you can imagine, it's often already too large a task to do so many different things with such a small group of members. Even after automating as many of the tasks we have to do as possible, our team finds it challenging to take on long term projects such as replacing dated components of our hosting infrastructure, because we spend so much time answering support tickets. As you can imagine, hosting around 50 organisations and over 150 websites for students, staff and organisations at KU Leuven, means that it would be highly unrealistic if our members had to frequently intervene in existing websites or create complete new ones. We understand that it's a difficult task to create a new website and that maintenance can at times be challenging too. We also understand that your situation is very unique to your organisation or circumstances. We think however that it would be unfair if we would help some and not others. We therefore make lots of documentation available on this website, we give advice and help to look for solutions in support tickets, and we attempt to steer people towards easier maintenance. Specifically, we are convinced that WordPress offers the most user friendly way to create a website while retaining as much creative freedom as possible. Our manual [[Setting up WordPress]] details how the install WordPress in a few easy steps and includes screenshots to show you what to do. Installing is a one time thing, so once your website exists you will never need to do it again. What you will have to do is update WordPress and any themes and plugins you may use. Luckily, this can all be achieved by the press of a button. On our documentation page about [[Updating WordPress]] we explain how you can enable automatic updates for all components of your WordPress website. That way, you will usually never have to do any maintenance at all. For advice on how to build or maintain your website, you can of course always contact [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org] with specific questions or situations. 6d34398a01bed5340c242d2c77cc077b6cce0120 1745 1744 2022-08-30T14:05:25Z Bert 8 wikitext text/x-wiki ULYSSIS is a non-profit student organisation with usually between 15 and 20 members. These members, most are students but some might have recently transitioned to a job or PhD, maintain our server hardware, make sure all the systems of our hosting run, answer support tickets, check security, organise events such as the [https://ctf.ulyssis.org ULYSSIS CTF] and [https://opensourcejobfair.be Open Source Job Fair], co-organise the [http://24urenloop.be 24 hour run], organise several [https://ulyssis.org/category/workshops/ workshops] a year, give technical advice and support to LOKO, and develop internal an external software tools such as [https://stemt.org Stemt.org]. As you can imagine, it's often already too large a task to do so many different things with such a small group of members. Even after automating as many of our tasks as possible, our team finds it challenging to take on long term projects such as replacing dated components of our hosting infrastructure, because we spend so much time answering support tickets. As you can imagine, hosting around 50 organisations and over 150 websites for students, staff and organisations at KU Leuven, means that it would be highly unrealistic if our members had to frequently intervene in existing websites or create complete new ones. We understand that it's a difficult task to create a new website and that maintenance can at times be challenging too. We also understand that your situation is very unique to your organisation or circumstances. We think however that it would be unfair if we would help some and not others. We therefore make lots of documentation available on this website, we give advice and help to look for solutions in support tickets, and we attempt to steer people towards easier maintenance. Specifically, we are convinced that WordPress offers the most user friendly way to create a website while retaining as much creative freedom as possible. Our manual [[Setting up WordPress]] details how the install WordPress in a few easy steps and includes screenshots to show you what to do. Installing is a one time thing, so once your website exists you will never need to do it again. What you will have to do is update WordPress and any themes and plugins you may use. Luckily, this can all be achieved by the press of a button. On our documentation page about [[Updating WordPress]] we explain how you can enable automatic updates for all components of your WordPress website. That way, you will usually never have to do any maintenance at all. For advice on how to build or maintain your website, you can of course always contact [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org] with specific questions or situations. 390c41aa97c97f9768e6d92eabc91cb388589b07 1746 1745 2022-08-30T14:06:54Z Bert 8 wikitext text/x-wiki ULYSSIS is a non-profit student organisation with usually between 15 and 20 members. These members, most are students but some might have recently transitioned to a job or PhD, maintain our server hardware, make sure all the systems of our hosting run, answer support tickets, check security, organise events such as the [https://ctf.ulyssis.org ULYSSIS CTF] and [https://opensourcejobfair.be Open Source Job Fair], co-organise the [http://24urenloop.be 24 hour run], organise several [https://ulyssis.org/category/workshops/ workshops] a year, give technical advice and support to LOKO, and develop internal an external software tools such as [https://stemt.org Stemt.org]. As you can imagine, it's often already too large a task to do so many different things with such a small group of members. Even after automating as many of our tasks as possible, our team finds it challenging to take on long term projects such as replacing dated components of our hosting infrastructure, because we spend so much time answering support tickets. As you can imagine, hosting around 50 organisations and over 150 websites for students, staff and organisations at KU Leuven, means that it would be highly unrealistic if our members had to frequently intervene in existing websites or create complete new ones. We understand that it's a difficult task to create a new website and that maintenance can at times be challenging too. We also understand that your situation is very unique to your organisation or circumstances. We think however that it would be unfair if we would help some and not others. We therefore make lots of documentation available on this website, we give advice and help to look for solutions in support tickets, and we attempt to steer people towards easier maintenance. Specifically, we are convinced that WordPress offers the most user friendly way to create a website while retaining as much creative freedom as possible. Our manual page [[Setting up WordPress]] details how the install WordPress in a few easy steps and includes screenshots to show you what to do. Installing is a one time thing, so once your website exists you will never need to do it again. What you will have to do is update WordPress and any themes and plugins you may use. Luckily, this can all be achieved by the press of a button. On our documentation page about [[Updating WordPress]] we explain how you can enable automatic updates for all components of your WordPress website. That way, you will usually never have to do any maintenance at all. For advice on how to build or maintain your website, you can of course always contact [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org] with specific questions or situations. 40c4cb1bd90029390ca0e61e8ba2025c6d565856 1747 1746 2022-08-30T14:07:14Z Bert 8 wikitext text/x-wiki ULYSSIS is a non-profit student organisation with usually between 15 and 20 members. These members, most are students but some might have recently transitioned to a job or PhD, maintain our server hardware, make sure all the systems of our hosting run, answer support tickets, check security, organise events such as the [https://ctf.ulyssis.org ULYSSIS CTF] and [https://opensourcejobfair.be Open Source Job Fair], co-organise the [http://24urenloop.be 24 hour run], organise several [https://ulyssis.org/category/workshops/ workshops] a year, give technical advice and support to LOKO, and develop internal an external software tools such as [https://stemt.org Stemt.org]. As you can imagine, it's often already too large a task to do so many different things with such a small group of members. Even after automating as many of our tasks as possible, our team finds it challenging to take on long term projects such as replacing dated components of our hosting infrastructure, because we spend so much time answering support tickets. As you can imagine, hosting around 50 organisations and over 150 websites for students, staff and organisations at KU Leuven, means that it would be highly unrealistic if our members had to frequently intervene in existing websites or create complete new ones. We understand that it's a difficult task to create a new website and that maintenance can at times be challenging too. We also understand that your situation is very unique to your organisation or circumstances. We think however that it would be unfair if we would help some and not others. We therefore make lots of documentation available on this website, we give advice and help to look for solutions in support tickets, and we attempt to steer people towards easier maintenance. Specifically, we are convinced that WordPress offers the most user friendly way to create a website while retaining as much creative freedom as possible. Our manual page [[Setting up WordPress]] details how to install WordPress in a few easy steps and includes screenshots to show you what to do. Installing is a one time thing, so once your website exists you will never need to do it again. What you will have to do is update WordPress and any themes and plugins you may use. Luckily, this can all be achieved by the press of a button. On our documentation page about [[Updating WordPress]] we explain how you can enable automatic updates for all components of your WordPress website. That way, you will usually never have to do any maintenance at all. For advice on how to build or maintain your website, you can of course always contact [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org] with specific questions or situations. 4d9bdae4b56b3b73d40e27fc9c6e02c2135a9311 1748 1747 2022-08-30T14:07:47Z Bert 8 wikitext text/x-wiki ULYSSIS is a non-profit student organisation with usually between 15 and 20 members. These members, most are students but some might have recently transitioned to a job or PhD, maintain our server hardware, make sure all the systems of our hosting run, answer support tickets, check security, organise events such as the [https://ctf.ulyssis.org ULYSSIS CTF] and [https://opensourcejobfair.be Open Source Job Fair], co-organise the [http://24urenloop.be 24 hour run], organise several [https://ulyssis.org/category/workshops/ workshops] a year, give technical advice and support to LOKO, and develop internal an external software tools such as [https://stemt.org Stemt.org]. As you can imagine, it's often already too large a task to do so many different things with such a small group of members. Even after automating as many of our tasks as possible, our team finds it challenging to take on long term projects such as replacing dated components of our hosting infrastructure, because we spend so much time answering support tickets. As you can imagine, hosting around 50 organisations and over 150 websites for students, staff and organisations at KU Leuven, means that it would be highly unrealistic if our members had to frequently intervene in existing websites or create complete new ones. We understand that it's a difficult task to create a new website and that maintenance can at times be challenging too. We also understand that your situation is very unique to your organisation or circumstances. We think however that it would be unfair if we would help some and not others. We therefore make lots of documentation available on this website, we give advice and help to look for solutions in support tickets, and we attempt to steer people towards easier maintenance. Specifically, we are convinced that WordPress offers the most user friendly way to create a website while retaining as much creative freedom as possible. Our manual page [[Setting up WordPress]] details how to install WordPress in a few easy steps and includes screenshots to show you what to do. Installing is a one time thing, so once your website exists you will never need to do it again. What you will have to do more frequently is update WordPress and any themes and plugins you may use. Luckily, this can all be achieved by the press of a button. On our documentation page about [[Updating WordPress]] we explain how you can enable automatic updates for all components of your WordPress website. That way, you will usually never have to do any maintenance at all. For advice on how to build or maintain your website, you can of course always contact [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org] with specific questions or situations. 9ae442744a4a762a7a85af250576e1afd11cc0d7 0 73 1749 1242 2022-08-30T15:22:32Z Simon 36 wikitext text/x-wiki We often get the question at our LaTeX workshop how to properly install the kulemt package. For this reason, we have decided to provide a proper guideline. You can acquire the kulemt package by downloading "kulemt-tds.zip" from https://eng.kuleuven.be/docs/kulemt. == One-time use == Most people will only use this package once, for their master thesis. In this case, you can just put the necessary files in the same folder as your LaTeX project. The easiest way to accomplish this, is to unzip the downloaded file and in the unzipped folder, navigate to the directory "tex/latex/kulemt". Here, copy the following files to the same directory as your LaTeX project: kulemt.cfg, kulemt.cls, kulemtx.sty, logokul.eps and logokuleng.eps. == User-wide installation == If you need to use the kulemt package more than a few times, copying these five files can become a little bit of a hassle. It is also possible to install this package in a central location where LaTeX can find it autonomously. When using TeXLive, as we recommend, this involves a bit more work. First, you should find where to install the packages for your user. This is called the TEXMFHOME. The default location of this folder is: * For Windows: the folder "texmf" in your %USERPROFILE% (C:\Users\YourUsername for Windows Vista and up). * For Linux: "~/texmf" * For OS X/macOS: "~/Library/texmf" It is possible that this folder needs to be created first. From the extracted kulemt-tds.zip, copy the entire directory "tex" to this location (note: the directory itself, not only its contents). If this does not work, or if you want to check the directory first, please refer to the section [[#Finding the TEXMFHOME]] at the bottom of this document. For a more technical overview, you can follow the general guidelines provided by the department: ftp://ftp.esat.kuleuven.be/latex/kulemt/README.html. == Using the kulemt package == A complete reference for using the kulemt package can be found at ftp://ftp.esat.kuleuven.be/latex/kulemt/kulemt.pdf. A minimal working example is provided below (inspired by the above manual). <nowiki> \documentclass[master=eelt,masteroption=ei]{kulemt} \setup{title={The best master thesis ever}, author={First Author\and Second Author}, promotor={Prof.\,dr.\,ir.\ Knows Better}, assessor={Ir.\,Kn. Owsmuch\and K. Nowsrest}, assistant={Ir.\ An~Assistent \and A.~Friend}} \begin{document} \mainmatter Test \end{document}</nowiki> Please note that for some other masters, some other options might be necessary, such as: <nowiki> \setup{ translatedtitle={My title in English}, % in case of a Dutch master udc=621.3, % This is the udc number for the faculty of engineering science shortabstract={A short summary of the thesis}, }</nowiki> == Finding the TEXMFHOME == In case the default location for the TEXMFHOME as stated above does not work, you can find the correct directory through command-line. In Linux and macOS, look for an app called "Terminal". In Windows, search for "cmd" using the start menu. The program has a black, square logo. To find out the central location of installed packages, run the following command: kpsewhich -var-value=TEXMFHOME An example output would be: C:/Users/ULYSSIS/texmf If you have found this folder, copy the entire "tex" directory from the extracted kulemt-tds.zip to this location, as stated before. Create the folder if needed. == Troubleshooting == The kulemt package requires the memoir package. Make sure you have this package. We recommend installing the texlive-full package on Ubuntu. When you use the installer from [https://files.ulyssis.org/ our file server] for Windows or OS X/macOS, you will automatically have the entire LaTeX suite. [[Category:Tutorials]] 571d64412d071d9f5fef7bebf28cbb4f246679f2 0 12 1753 874 2022-09-29T14:30:29Z Erico 50 Changes zoals uitgelegd op wikipagina documentatie herschrijven, nog wat meer nodig bij ssh wikitext text/x-wiki == Creating a database == You can create one or more PostgreSQL databases in [https://ucc.ulyssis.org UCC]. The first database you create will have the same name as your username. Subsequent databases will be prefixed with "''username''_". == Managing your database == * The easiest way to manage your database is using [https://phppgadmin.ulyssis.org phpPgAdmin]. * You can also access it via the [[Accessing shell servers over SSH|command line]] with: psql -h pgsql.ulyssis.org === Creating a PostgreSQL user === To use PostgreSQL on you ULYSSIS account, you first need to create a PostgreSQL user on [https://ucc,ulyssis,org UCC]. In the PostgreSQL section of the panel, you will be suggested to click a link to create a user. Then fill in the password for the database user. It is highly recommended that this password differs from the password you use for your account. Finally, click ''Create user'' and you are ready to go. === Creating a PostgreSQL database === After having created a PostgreSQL user, you can click ''Add database'' in [https://ucc.ulyssis.org UCC] and enter the name for your new database. It will automatically will be prefixed by your username. === Deleting a PostgreSQL database === If you no longer need a database, you can easily remove it by clicking on ''PostgreSQL'' in [https://ucc.ulyssis.org UCC] and then pressing on ''Remove database'' next to the database you would like to delete. After confirming, the database and all its tables and other content will be gone. For security reasons, you can't remove databases using an SQL query like DROP DATABASE, but have to go through UCC. == Using PostgreSQL for your website or application == You can connect to the database with the following details: * Host: <code>pgsql.ulyssis.org</code> * Login: your ULYSSIS username * Password: the PostgreSQL password you chose in UCC * Database: the database you created in UCC For example, if my username is foobar, I made a database called website and I were to create a PHP website I would use something like:<syntaxhighlight lang="php"> $connection = pg_connect("host=pgsql.ulyssis.org user=foo password=password db=foo"); </syntaxhighlight>or <syntaxhighlight lang="php"> $pdo = new PDO('pgsql:host=pgsql.ulyssis.org;dbname=foo', 'foo', 'password'); </syntaxhighlight> === Accessing PostgreSQL with PHPMyAdmin or Adminer === Using your username and password you can easily manage your PostgreSQL databases, tables and records on https://phpmyadmin.ulyssis.org and https://adminer.ulyssis.org. Documentation is also available to aid in [[using PHPMyAdmin]] and [[using Adminer]]. ===Accessing PostgreSQL from outside of our network=== To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH-tunnel. On Linux, Mac OSX and other Unix-like Operating Systems it is easily possible to use the following command to create a tunnel to a local port (in this case 5400): ssh username@ssh2.ulyssis.org -L 5400:pgsql.ulyssis.org:5432 -N While this command is running, you can connect to the PostgreSQL server with host 'localhost' and port '5400', To terminate the port forwarding, press ctrl-C in the terminal. You can use "ssh -f username@ssh2.ulyssis.org -L 5400:pgsql.ulyssis.org:5432 -N": the f-argument will put the command in the background. == PostGIS == If necessary for an application or website you wish to use on ULYSSIS, we can always enable PostGIS for the specific database you wish to use it on. Contact us at ulyssis@ulyssis.org and let us know you would like to get PostGIS enabled and on which specific database. [[Category:Databases]] 9fa25cfb8a50b129f6b78638feea619af7ad719e 1755 1753 2022-09-30T08:03:36Z Erico 50 wikitext text/x-wiki == Creating a database == You can create one or more PostgreSQL databases in [https://ucc.ulyssis.org UCC]. The first database you create will have the same name as your username. Subsequent databases will be prefixed with "''username''_". == Managing your database == * The easiest way to manage your database is using [https://phppgadmin.ulyssis.org phpPgAdmin]. * You can also access it via the [[Accessing shell servers over SSH|command line]] with: psql -h pgsql.ulyssis.org === Creating a PostgreSQL user === To use PostgreSQL on you ULYSSIS account, you first need to create a PostgreSQL user on [https://ucc,ulyssis,org UCC]. In the PostgreSQL section of the panel, you will be suggested to click a link to create a user. Then fill in the password for the database user. It is highly recommended that this password differs from the password you use for your account. Finally, click ''Create user'' and you are ready to go. === Creating a PostgreSQL database === After having created a PostgreSQL user, you can click ''Add database'' in [https://ucc.ulyssis.org UCC] and enter the name for your new database. It will automatically will be prefixed by your username. === Deleting a PostgreSQL database === If you no longer need a database, you can easily remove it by clicking on ''PostgreSQL'' in [https://ucc.ulyssis.org UCC] and then pressing on ''Remove database'' next to the database you would like to delete. After confirming, the database and all its tables and other content will be gone. For security reasons, you can't remove databases using an SQL query like DROP DATABASE, but have to go through UCC. == Using PostgreSQL for your website or application == You can connect to the database with the following details: * Host: <code>pgsql.ulyssis.org</code> * Login: your ULYSSIS username * Password: the PostgreSQL password you chose in UCC * Database: the database you created in UCC For example, if my username is foobar, I made a database called website and I were to create a PHP website I would use something like:<syntaxhighlight lang="php"> $connection = pg_connect("host=pgsql.ulyssis.org user=foo password=password db=foo"); </syntaxhighlight>or <syntaxhighlight lang="php"> $pdo = new PDO('pgsql:host=pgsql.ulyssis.org;dbname=foo', 'foo', 'password'); </syntaxhighlight> === Accessing PostgreSQL with PHPMyAdmin or Adminer === Using your username and password you can easily manage your PostgreSQL databases, tables and records on https://phppgadmin.ulyssis.org and https://adminer.ulyssis.org. Documentation is also available to aid in [[Using PHPPgAdmin|using PHPMyAdmin]] and [[using Adminer]]. ===Accessing PostgreSQL from outside of our network=== To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH-tunnel. SSH-tunneling makes an encrypted connection between 2 devices, which we will use to map a port on the database server onto a local port on your device, so it behaves and can be used like a local port. On Linux, Mac OSX and other Unix-like Operating Systems it is easily possible to use the following command to create a tunnel to a local port (in this case 5400): ssh username@ssh2.ulyssis.org -L 5400:pgsql.ulyssis.org:5432 -N While this command is running, you can connect to the PostgreSQL server with host 'localhost' and port '5400', To terminate the port forwarding, press ctrl-C in the terminal. If you prefer the command to be run in the background, you can add <code>-f</code> to your command. To close this background process, you can use pgrep to acquire the pid of the process: pgrep --list-full ssh | grep psgql.ulyssis.org 12657 ssh -f username@ssh2.ulyssis.org -L 5400:pgsql.ulyssis.org:5432 -N Then we can then kill the process using kill with the pid we acquired: kill 12657 == PostGIS == If necessary for an application or website you wish to use on ULYSSIS, we can always enable PostGIS for the specific database you wish to use it on. Contact us at ulyssis@ulyssis.org and let us know you would like to get PostGIS enabled and on which specific database. [[Category:Databases]] 199fe9d9d96c8e09c2f9a1879938e4032c7c3f05 1756 1755 2022-09-30T08:05:22Z Erico 50 replace PHPMyAdmin with PHPPgAdmin wikitext text/x-wiki == Creating a database == You can create one or more PostgreSQL databases in [https://ucc.ulyssis.org UCC]. The first database you create will have the same name as your username. Subsequent databases will be prefixed with "''username''_". == Managing your database == * The easiest way to manage your database is using [https://phppgadmin.ulyssis.org phpPgAdmin]. * You can also access it via the [[Accessing shell servers over SSH|command line]] with: psql -h pgsql.ulyssis.org === Creating a PostgreSQL user === To use PostgreSQL on you ULYSSIS account, you first need to create a PostgreSQL user on [https://ucc,ulyssis,org UCC]. In the PostgreSQL section of the panel, you will be suggested to click a link to create a user. Then fill in the password for the database user. It is highly recommended that this password differs from the password you use for your account. Finally, click ''Create user'' and you are ready to go. === Creating a PostgreSQL database === After having created a PostgreSQL user, you can click ''Add database'' in [https://ucc.ulyssis.org UCC] and enter the name for your new database. It will automatically will be prefixed by your username. === Deleting a PostgreSQL database === If you no longer need a database, you can easily remove it by clicking on ''PostgreSQL'' in [https://ucc.ulyssis.org UCC] and then pressing on ''Remove database'' next to the database you would like to delete. After confirming, the database and all its tables and other content will be gone. For security reasons, you can't remove databases using an SQL query like DROP DATABASE, but have to go through UCC. == Using PostgreSQL for your website or application == You can connect to the database with the following details: * Host: <code>pgsql.ulyssis.org</code> * Login: your ULYSSIS username * Password: the PostgreSQL password you chose in UCC * Database: the database you created in UCC For example, if my username is foobar, I made a database called website and I were to create a PHP website I would use something like:<syntaxhighlight lang="php"> $connection = pg_connect("host=pgsql.ulyssis.org user=foo password=password db=foo"); </syntaxhighlight>or <syntaxhighlight lang="php"> $pdo = new PDO('pgsql:host=pgsql.ulyssis.org;dbname=foo', 'foo', 'password'); </syntaxhighlight> === Accessing PostgreSQL with PHPPgAdmin or Adminer === Using your username and password you can easily manage your PostgreSQL databases, tables and records on https://phppgadmin.ulyssis.org and https://adminer.ulyssis.org. Documentation is also available to aid in [[Using PHPPgAdmin|using PHPMyAdmin]] and [[using Adminer]]. ===Accessing PostgreSQL from outside of our network=== To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH-tunnel. SSH-tunneling makes an encrypted connection between 2 devices, which we will use to map a port on the database server onto a local port on your device, so it behaves and can be used like a local port. On Linux, Mac OSX and other Unix-like Operating Systems it is easily possible to use the following command to create a tunnel to a local port (in this case 5400): ssh username@ssh2.ulyssis.org -L 5400:pgsql.ulyssis.org:5432 -N While this command is running, you can connect to the PostgreSQL server with host 'localhost' and port '5400', To terminate the port forwarding, press ctrl-C in the terminal. If you prefer the command to be run in the background, you can add <code>-f</code> to your command. To close this background process, you can use pgrep to acquire the pid of the process: pgrep --list-full ssh | grep psgql.ulyssis.org 12657 ssh -f username@ssh2.ulyssis.org -L 5400:pgsql.ulyssis.org:5432 -N Then we can then kill the process using kill with the pid we acquired: kill 12657 == PostGIS == If necessary for an application or website you wish to use on ULYSSIS, we can always enable PostGIS for the specific database you wish to use it on. Contact us at ulyssis@ulyssis.org and let us know you would like to get PostGIS enabled and on which specific database. [[Category:Databases]] bb1a0d5307c36f55534a87506404b88488bc7d85 1757 1756 2022-09-30T08:05:59Z Erico 50 replace PHPMyAdmin with PHPPgAdmin wikitext text/x-wiki == Creating a database == You can create one or more PostgreSQL databases in [https://ucc.ulyssis.org UCC]. The first database you create will have the same name as your username. Subsequent databases will be prefixed with "''username''_". == Managing your database == * The easiest way to manage your database is using [https://phppgadmin.ulyssis.org phpPgAdmin]. * You can also access it via the [[Accessing shell servers over SSH|command line]] with: psql -h pgsql.ulyssis.org === Creating a PostgreSQL user === To use PostgreSQL on you ULYSSIS account, you first need to create a PostgreSQL user on [https://ucc,ulyssis,org UCC]. In the PostgreSQL section of the panel, you will be suggested to click a link to create a user. Then fill in the password for the database user. It is highly recommended that this password differs from the password you use for your account. Finally, click ''Create user'' and you are ready to go. === Creating a PostgreSQL database === After having created a PostgreSQL user, you can click ''Add database'' in [https://ucc.ulyssis.org UCC] and enter the name for your new database. It will automatically will be prefixed by your username. === Deleting a PostgreSQL database === If you no longer need a database, you can easily remove it by clicking on ''PostgreSQL'' in [https://ucc.ulyssis.org UCC] and then pressing on ''Remove database'' next to the database you would like to delete. After confirming, the database and all its tables and other content will be gone. For security reasons, you can't remove databases using an SQL query like DROP DATABASE, but have to go through UCC. == Using PostgreSQL for your website or application == You can connect to the database with the following details: * Host: <code>pgsql.ulyssis.org</code> * Login: your ULYSSIS username * Password: the PostgreSQL password you chose in UCC * Database: the database you created in UCC For example, if my username is foobar, I made a database called website and I were to create a PHP website I would use something like:<syntaxhighlight lang="php"> $connection = pg_connect("host=pgsql.ulyssis.org user=foo password=password db=foo"); </syntaxhighlight>or <syntaxhighlight lang="php"> $pdo = new PDO('pgsql:host=pgsql.ulyssis.org;dbname=foo', 'foo', 'password'); </syntaxhighlight> === Accessing PostgreSQL with PHPPgAdmin or Adminer === Using your username and password you can easily manage your PostgreSQL databases, tables and records on https://phppgadmin.ulyssis.org and https://adminer.ulyssis.org. Documentation is also available to aid in [[using PHPPgAdmin]] and [[using Adminer]]. ===Accessing PostgreSQL from outside of our network=== To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH-tunnel. SSH-tunneling makes an encrypted connection between 2 devices, which we will use to map a port on the database server onto a local port on your device, so it behaves and can be used like a local port. On Linux, Mac OSX and other Unix-like Operating Systems it is easily possible to use the following command to create a tunnel to a local port (in this case 5400): ssh username@ssh2.ulyssis.org -L 5400:pgsql.ulyssis.org:5432 -N While this command is running, you can connect to the PostgreSQL server with host 'localhost' and port '5400', To terminate the port forwarding, press ctrl-C in the terminal. If you prefer the command to be run in the background, you can add <code>-f</code> to your command. To close this background process, you can use pgrep to acquire the pid of the process: pgrep --list-full ssh | grep psgql.ulyssis.org 12657 ssh -f username@ssh2.ulyssis.org -L 5400:pgsql.ulyssis.org:5432 -N Then we can then kill the process using kill with the pid we acquired: kill 12657 == PostGIS == If necessary for an application or website you wish to use on ULYSSIS, we can always enable PostGIS for the specific database you wish to use it on. Contact us at ulyssis@ulyssis.org and let us know you would like to get PostGIS enabled and on which specific database. [[Category:Databases]] 69522ee57948b7ca8820aa085bbde15264ecb7af 1758 1757 2022-09-30T08:09:26Z Erico 50 typos wikitext text/x-wiki == Creating a database == You can create one or more PostgreSQL databases in [https://ucc.ulyssis.org UCC]. The first database you create will have the same name as your username. Subsequent databases will be prefixed with "''username''_". == Managing your database == * The easiest way to manage your database is using [https://phppgadmin.ulyssis.org phpPgAdmin]. * You can also access it via the [[Accessing shell servers over SSH|command line]] with: psql -h pgsql.ulyssis.org === Creating a PostgreSQL user === To use PostgreSQL on you ULYSSIS account, you first need to create a PostgreSQL user on [https://ucc,ulyssis,org UCC]. In the PostgreSQL section of the panel, you will be suggested to click a link to create a user. Then fill in the password for the database user. It is highly recommended that this password differs from the password you use for your account. Finally, click ''Create user'' and you are ready to go. === Creating a PostgreSQL database === After having created a PostgreSQL user, you can click ''Add database'' in [https://ucc.ulyssis.org UCC] and enter the name for your new database. It will automatically will be prefixed by your username. === Deleting a PostgreSQL database === If you no longer need a database, you can easily remove it by clicking on ''PostgreSQL'' in [https://ucc.ulyssis.org UCC] and then pressing on ''Remove database'' next to the database you would like to delete. After confirming, the database and all its tables and other content will be gone. For security reasons, you can't remove databases using an SQL query like DROP DATABASE, but have to go through UCC. == Using PostgreSQL for your website or application == You can connect to the database with the following details: * Host: <code>pgsql.ulyssis.org</code> * Login: your ULYSSIS username * Password: the PostgreSQL password you chose in UCC * Database: the database you created in UCC For example, if my username is foobar, I made a database called website and I were to create a PHP website I would use something like:<syntaxhighlight lang="php"> $connection = pg_connect("host=pgsql.ulyssis.org user=foo password=password db=foo"); </syntaxhighlight>or <syntaxhighlight lang="php"> $pdo = new PDO('pgsql:host=pgsql.ulyssis.org;dbname=foo', 'foo', 'password'); </syntaxhighlight> === Accessing PostgreSQL with PHPPgAdmin or Adminer === Using your username and password you can easily manage your PostgreSQL databases, tables and records on https://phppgadmin.ulyssis.org and https://adminer.ulyssis.org. Documentation is also available to aid in [[using PHPPgAdmin]] and [[using Adminer]]. ===Accessing PostgreSQL from outside of our network=== To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH-tunnel. SSH-tunneling makes an encrypted connection between 2 devices, which we will use to map a port on the database server onto a local port on your device, so it behaves and can be used like a local port. On Linux, Mac OSX and other Unix-like Operating Systems it is easily possible to use the following command to create a tunnel to a local port (in this case 5400): ssh username@ssh2.ulyssis.org -L 5400:pgsql.ulyssis.org:5432 -N While this command is running, you can connect to the PostgreSQL server with host 'localhost' and port '5400', To terminate the port forwarding, press ctrl-C in the terminal. If you prefer the command to be run in the background, you can add <code>-f</code> to your command. To close this background process, you can use pgrep to acquire the pid of the process: pgrep --list-full ssh | grep pgsql.ulyssis.org 12657 ssh -f username@ssh2.ulyssis.org -L 5400:pgsql.ulyssis.org:5432 -N We can then kill the process using kill with the pid we acquired: kill 12657 == PostGIS == If necessary for an application or website you wish to use on ULYSSIS, we can always enable PostGIS for the specific database you wish to use it on. Contact us at ulyssis@ulyssis.org and let us know you would like to get PostGIS enabled and on which specific database. [[Category:Databases]] dc633ca4f5389e590172b95fb6ed79f2483aac56 0 6 1754 1201 2022-09-29T14:31:01Z Erico 50 Accessing MySQL aangepast zoals uitgelegd in wikipagina documentatie herschrijven, nog wat meer nodig bij ssh wikitext text/x-wiki MySQL is one of the most popular databases for websites. It's used by most CMSes and other common web software, and many programming languages have support for it. ULYSSIS specifically uses MariaDB, which is a fork of MySQL with similar features and (almost) identical SQL syntax, but offers better performance and has less corporate interference in the development process. == Managing MySQL == All common management tasks can be performed through our control panel [https://ucc.ulyssis.org UCC], under the MySQL section. ===Creating a MySQL user=== To use MySQL on your ULYSSIS account, you first need to create a MySQL user on [https://ucc.ulyssis.org UCC]. In the MySQL section of the panel, you will be suggested to click a link to create a user. Then fill in a password for the database user. It is highly recommended that this password differs from the password you use for your account. Finally, click ''Create user'' and you are ready to go. ===Creating a MySQL database=== After having created a MySQL user, you can click ''Add database'' in [https://ucc.ulyssis.org UCC] and enter the name for your new database. It will automatically be prefixed by your username. ===Deleting a MySQL database=== If you no longer need a database, you can easily remove it by clicking on ''MySQL'' in [https://ucc.ulyssis.org UCC] and then pressing on ''Remove database'' next to the database you would like to delete. After confirming, the database and all its tables and other contents will be gone. For security reasons, you can't remove databases using an SQL query like DROP DATABASE, but have to go through UCC. == Accessing MySQL == Our MySQL and PostgreSQL databases run on a separate database server, this means you may need to enter a specific host, together with the correct credentials, to access your database within a website or application. You may also wish to use a common tool such as PHPMyAdmin or access a database remotely. Details on how to do that are available in the sections below. ===Using MySQL for your website or application=== you can connect to the database with the following details: Host: mysql.ulyssis.org Username: your account's username Password: the password you chose when you made the MySQL user Database: the database name you chose, prefixed by your username For example, if my username is foobar, I made a database called website and I were to create a PHP website I would use something like: <syntaxhighlight lang="php">$db = new mysqli('mysql.ulyssis.org', 'foobar', 'correct horse battery staple', 'foobar_website');</syntaxhighlight> or <syntaxhighlight lang="php">$db = new PDO('mysql:host=mysql.ulyssis.org;dbname=foobar_website', 'foobar', 'correct horse battery staple');</syntaxhighlight> ===Accessing MySQL with PHPMyAdmin or Adminer=== Using your username and password you can easily manage your MySQL databases, tables and records on https://phpmyadmin.ulyssis.org and https://adminer.ulyssis.org. Documentation is also available to aid in [[using PHPMyAdmin]] and [[using Adminer]]. ===Accessing MySQL from outside of our network=== To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH tunnel. In many MySQL management tools this is already supported. On Linux, Mac OSX and other Unix-like Operating Systems it is also easily possible to use the following command to create a tunnel to a local port (in this case 3300) ssh username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N While this command is running, you can connect to the MySQL server with host 'localhost' and port '3300'. To terminate the port forwarding, press ctrl-C in the terminal. You can use "ssh -f username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N": the f-argument will put the command in the background. ==== MySQL Workbench ==== While [https://www.mysql.com/products/workbench/ MySQL Workbench] might not fully support our MySQL database, all commonly used operations work perfectly. You can connect to our database using MySQL Workbench by creating a connection as follows ([username] should be replaced by your username, of course): [[File:MySQL_Workbench_SSH.png]] [[Category:Databases]] 4a01b4ab0140e80bdf33f8aebe93dd510f5abbbd 1759 1754 2022-09-30T08:14:38Z Erico 50 expanded SSH explanation wikitext text/x-wiki MySQL is one of the most popular databases for websites. It's used by most CMSes and other common web software, and many programming languages have support for it. ULYSSIS specifically uses MariaDB, which is a fork of MySQL with similar features and (almost) identical SQL syntax, but offers better performance and has less corporate interference in the development process. == Managing MySQL == All common management tasks can be performed through our control panel [https://ucc.ulyssis.org UCC], under the MySQL section. ===Creating a MySQL user=== To use MySQL on your ULYSSIS account, you first need to create a MySQL user on [https://ucc.ulyssis.org UCC]. In the MySQL section of the panel, you will be suggested to click a link to create a user. Then fill in a password for the database user. It is highly recommended that this password differs from the password you use for your account. Finally, click ''Create user'' and you are ready to go. ===Creating a MySQL database=== After having created a MySQL user, you can click ''Add database'' in [https://ucc.ulyssis.org UCC] and enter the name for your new database. It will automatically be prefixed by your username. ===Deleting a MySQL database=== If you no longer need a database, you can easily remove it by clicking on ''MySQL'' in [https://ucc.ulyssis.org UCC] and then pressing on ''Remove database'' next to the database you would like to delete. After confirming, the database and all its tables and other contents will be gone. For security reasons, you can't remove databases using an SQL query like DROP DATABASE, but have to go through UCC. == Accessing MySQL == Our MySQL and PostgreSQL databases run on a separate database server, this means you may need to enter a specific host, together with the correct credentials, to access your database within a website or application. You may also wish to use a common tool such as PHPMyAdmin or access a database remotely. Details on how to do that are available in the sections below. ===Using MySQL for your website or application=== you can connect to the database with the following details: Host: mysql.ulyssis.org Username: your account's username Password: the password you chose when you made the MySQL user Database: the database name you chose, prefixed by your username For example, if my username is foobar, I made a database called website and I were to create a PHP website I would use something like: <syntaxhighlight lang="php">$db = new mysqli('mysql.ulyssis.org', 'foobar', 'correct horse battery staple', 'foobar_website');</syntaxhighlight> or <syntaxhighlight lang="php">$db = new PDO('mysql:host=mysql.ulyssis.org;dbname=foobar_website', 'foobar', 'correct horse battery staple');</syntaxhighlight> ===Accessing MySQL with PHPMyAdmin or Adminer=== Using your username and password you can easily manage your MySQL databases, tables and records on https://phpmyadmin.ulyssis.org and https://adminer.ulyssis.org. Documentation is also available to aid in [[using PHPMyAdmin]] and [[using Adminer]]. ===Accessing MySQL from outside of our network=== To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH tunnel. In many MySQL management tools this is already supported. On Linux, Mac OSX and other Unix-like Operating Systems it is also easily possible to use the following command to create a tunnel to a local port (in this case 3300) ssh username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N While this command is running, you can connect to the MySQL server with host 'localhost' and port '3300'. To terminate the port forwarding, press ctrl-C in the terminal. If you prefer the command to be run in the background, you can add <code>-f</code> to your command. To close this background process, you can use pgrep to acquire the pid of the process: pgrep --list-full ssh | grep pgsql.ulyssis.org 12657 ssh -f username@ssh2.ulyssis.org -L 5400:pgsql.ulyssis.org:5432 -N We can then kill the process using kill with the pid we acquired: kill 12657 ====MySQL Workbench==== While [https://www.mysql.com/products/workbench/ MySQL Workbench] might not fully support our MySQL database, all commonly used operations work perfectly. You can connect to our database using MySQL Workbench by creating a connection as follows ([username] should be replaced by your username, of course): [[File:MySQL_Workbench_SSH.png]] [[Category:Databases]] 4360628d8ea7882b59c9f237ab8ad69b6706b5c7 1760 1759 2022-10-01T12:34:28Z Erico 50 pgsql replaced with mysql in pgrep command wikitext text/x-wiki MySQL is one of the most popular databases for websites. It's used by most CMSes and other common web software, and many programming languages have support for it. ULYSSIS specifically uses MariaDB, which is a fork of MySQL with similar features and (almost) identical SQL syntax, but offers better performance and has less corporate interference in the development process. == Managing MySQL == All common management tasks can be performed through our control panel [https://ucc.ulyssis.org UCC], under the MySQL section. ===Creating a MySQL user=== To use MySQL on your ULYSSIS account, you first need to create a MySQL user on [https://ucc.ulyssis.org UCC]. In the MySQL section of the panel, you will be suggested to click a link to create a user. Then fill in a password for the database user. It is highly recommended that this password differs from the password you use for your account. Finally, click ''Create user'' and you are ready to go. ===Creating a MySQL database=== After having created a MySQL user, you can click ''Add database'' in [https://ucc.ulyssis.org UCC] and enter the name for your new database. It will automatically be prefixed by your username. ===Deleting a MySQL database=== If you no longer need a database, you can easily remove it by clicking on ''MySQL'' in [https://ucc.ulyssis.org UCC] and then pressing on ''Remove database'' next to the database you would like to delete. After confirming, the database and all its tables and other contents will be gone. For security reasons, you can't remove databases using an SQL query like DROP DATABASE, but have to go through UCC. == Accessing MySQL == Our MySQL and PostgreSQL databases run on a separate database server, this means you may need to enter a specific host, together with the correct credentials, to access your database within a website or application. You may also wish to use a common tool such as PHPMyAdmin or access a database remotely. Details on how to do that are available in the sections below. ===Using MySQL for your website or application=== you can connect to the database with the following details: Host: mysql.ulyssis.org Username: your account's username Password: the password you chose when you made the MySQL user Database: the database name you chose, prefixed by your username For example, if my username is foobar, I made a database called website and I were to create a PHP website I would use something like: <syntaxhighlight lang="php">$db = new mysqli('mysql.ulyssis.org', 'foobar', 'correct horse battery staple', 'foobar_website');</syntaxhighlight> or <syntaxhighlight lang="php">$db = new PDO('mysql:host=mysql.ulyssis.org;dbname=foobar_website', 'foobar', 'correct horse battery staple');</syntaxhighlight> ===Accessing MySQL with PHPMyAdmin or Adminer=== Using your username and password you can easily manage your MySQL databases, tables and records on https://phpmyadmin.ulyssis.org and https://adminer.ulyssis.org. Documentation is also available to aid in [[using PHPMyAdmin]] and [[using Adminer]]. ===Accessing MySQL from outside of our network=== To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH tunnel. In many MySQL management tools this is already supported. On Linux, Mac OSX and other Unix-like Operating Systems it is also easily possible to use the following command to create a tunnel to a local port (in this case 3300) ssh username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N While this command is running, you can connect to the MySQL server with host 'localhost' and port '3300'. To terminate the port forwarding, press ctrl-C in the terminal. If you prefer the command to be run in the background, you can add <code>-f</code> to your command. To close this background process, you can use pgrep to acquire the pid of the process: pgrep --list-full ssh | grep mysql.ulyssis.org 12657 ssh -f username@ssh2.ulyssis.org -L 5400:mysql.ulyssis.org:5432 -N We can then kill the process using kill with the pid we acquired: kill 12657 ====MySQL Workbench==== While [https://www.mysql.com/products/workbench/ MySQL Workbench] might not fully support our MySQL database, all commonly used operations work perfectly. You can connect to our database using MySQL Workbench by creating a connection as follows ([username] should be replaced by your username, of course): [[File:MySQL_Workbench_SSH.png]] [[Category:Databases]] 21ed280f4d1c3ef47bf8145baca553cb72befbeb 1761 1760 2022-10-01T13:28:49Z Erico 50 remove SQL workbench wikitext text/x-wiki MySQL is one of the most popular databases for websites. It's used by most CMSes and other common web software, and many programming languages have support for it. ULYSSIS specifically uses MariaDB, which is a fork of MySQL with similar features and (almost) identical SQL syntax, but offers better performance and has less corporate interference in the development process. == Managing MySQL == All common management tasks can be performed through our control panel [https://ucc.ulyssis.org UCC], under the MySQL section. ===Creating a MySQL user=== To use MySQL on your ULYSSIS account, you first need to create a MySQL user on [https://ucc.ulyssis.org UCC]. In the MySQL section of the panel, you will be suggested to click a link to create a user. Then fill in a password for the database user. It is highly recommended that this password differs from the password you use for your account. Finally, click ''Create user'' and you are ready to go. ===Creating a MySQL database=== After having created a MySQL user, you can click ''Add database'' in [https://ucc.ulyssis.org UCC] and enter the name for your new database. It will automatically be prefixed by your username. ===Deleting a MySQL database=== If you no longer need a database, you can easily remove it by clicking on ''MySQL'' in [https://ucc.ulyssis.org UCC] and then pressing on ''Remove database'' next to the database you would like to delete. After confirming, the database and all its tables and other contents will be gone. For security reasons, you can't remove databases using an SQL query like DROP DATABASE, but have to go through UCC. == Accessing MySQL == Our MySQL and PostgreSQL databases run on a separate database server, this means you may need to enter a specific host, together with the correct credentials, to access your database within a website or application. You may also wish to use a common tool such as PHPMyAdmin or access a database remotely. Details on how to do that are available in the sections below. ===Using MySQL for your website or application=== you can connect to the database with the following details: Host: mysql.ulyssis.org Username: your account's username Password: the password you chose when you made the MySQL user Database: the database name you chose, prefixed by your username For example, if my username is foobar, I made a database called website and I were to create a PHP website I would use something like: <syntaxhighlight lang="php">$db = new mysqli('mysql.ulyssis.org', 'foobar', 'correct horse battery staple', 'foobar_website');</syntaxhighlight> or <syntaxhighlight lang="php">$db = new PDO('mysql:host=mysql.ulyssis.org;dbname=foobar_website', 'foobar', 'correct horse battery staple');</syntaxhighlight> ===Accessing MySQL with PHPMyAdmin or Adminer=== Using your username and password you can easily manage your MySQL databases, tables and records on https://phpmyadmin.ulyssis.org and https://adminer.ulyssis.org. Documentation is also available to aid in [[using PHPMyAdmin]] and [[using Adminer]]. ===Accessing MySQL from outside of our network=== To prevent unnecessary load on our database server by hackers and bots it is only available inside of our network. If you wish to access it externally the easiest way is to use an SSH tunnel. In many MySQL management tools this is already supported. On Linux, Mac OSX and other Unix-like Operating Systems it is also easily possible to use the following command to create a tunnel to a local port (in this case 3300) ssh username@ssh2.ulyssis.org -L 3300:mysql.ulyssis.org:3306 -N While this command is running, you can connect to the MySQL server with host 'localhost' and port '3300'. To terminate the port forwarding, press ctrl-C in the terminal. If you prefer the command to be run in the background, you can add <code>-f</code> to your command. To close this background process, you can use pgrep to acquire the pid of the process: pgrep --list-full ssh | grep mysql.ulyssis.org 12657 ssh -f username@ssh2.ulyssis.org -L 5400:mysql.ulyssis.org:5432 -N We can then kill the process using kill with the pid we acquired: kill 12657 [[Category:Databases]] f306026e302e1768a995af4b9e1c4bac4178c26c 0 33 1762 1106 2022-10-08T23:24:03Z Bert 8 /* How to request */ wikitext text/x-wiki Shibboleth is the software powering the Central KU Leuven Login. It's a piece of software used by many universities to supply identification and access management. ULYSSIS works together with ICTS to supply limited access to Shibboleth. We are however only able to supply Shibboleth to those approved by ICTS. In practice all faculty unions will be granted access if they can prove they have the technical ability to use Shibboleth in a safe and privacy friendly way. For other organisations it can be more difficult to get access, therefore it is best to write an extensive explenation of what you plan to do with Shibboleth, why your organisation requires it, what your organisation does, and other relevant information. We will then contact ICTS with your request. == How to request == To request Shibboleth access, you first need to make sure the domain you wish to use Shibboleth on has valid SSL certificates. Lately ICTS has been pushing that all traffic to the website is already over HTTPS before Shibboleth is issued. For more info you can check [[Getting SSL]] If you have SSL set up you need to send an email to request Shibboleth to ulyssis@ulyssis.org. The email must contain the following info: * What domain you wish to use Shibboleth on (this must be a single domain, so keep subdomains and www in mind) * What you will be using Shibboleth for and in general what your application will do. This explanation is required by ICTS. If you fail to convince them they will not grant your domain access. * What attributes you wish to use and what you will do with them (and whether you will store them). You can find the list of attributes on https://admin.kuleuven.be/icts/services/aai/attributes * Preconfigure .htaccess in the root folder of the (sub)domain you are requesting Shibboleth for. This is required for ULYSSIS to be able to export the required Shibboleth Metadata. ** ULYSSIS may view your .htaccess file to investigate any problems. * If you are not a recognised faculty union you will need to include an extra motivation why you require Shibboleth (as noted above) If your application is complete and correct we will file a formal request. We will of course notify you of ICTS' response. == Deploying Shibboleth == After you have been granted access you can soon start using Shibboleth. The first step is to add the following lines to your .htaccess ShibDisable Off AuthType Shibboleth require shibboleth ShibRequireSession off We disable certain features of Shibboleth here because it will otherwise interfere with any other HTTP-auth options you might be using. Now that you have added this information to .htaccess you are able to serve requests to Shibboleth.sso, if your request is well-formed the sso will handle communication with the IdP (identity provider) of the KU Leuven. A login link follows the following syntax: https://[YOUR_HOSTNAME]/Shibboleth.sso/WAYF/kuleuven?target=[URLENCODED_RETURN_URL] And logout links: https://[YOUR_HOSTNAME]/Shibboleth.sso/Logout?return=[URLENCODED_DISPLAY_URL] It is important to note that on logout the user will stay on the KU Leuven's IdP-page and your link will only be displayed. The user will NOT be redirected (even though this is the normale behaviour according to the Shibboleth documentation). As soon as a user is logged in, their attributes will be available to your application. Attributes are certain properties that an account may have and that supply further information about them. Some examples are: first name, last name, mail, student id. All of these will be available as environment variables. In PHP these are part of $_SERVER. Keep in mind that Apache might prefix the names of these variables with REDIRECT_ multiple times (for example when mod_rewrite is used). For an overview of all attributes you can check out http://shib.kuleuven.be/secure/allAttributes More general information on the KU Leuvens implementation can be found on http://shib.kuleuven.be/. [[Category:Webserver]] c7e89a754bc765599bc046d038022858caed2c62 6 256 1763 2022-11-11T17:07:26Z Johnny 51 wikitext text/x-wiki Where to find Agenda Sync in KU Loket 9dfe7b026ffc4092528028db60350d67c98e69bf 6 257 1764 2022-11-11T17:24:22Z Johnny 51 wikitext text/x-wiki How to turn on Agenda Synchronisation 14dad260093f99f87ea98afcae62a4983d267501 6 258 1765 2022-11-11T17:36:51Z Johnny 51 wikitext text/x-wiki Where to find calender within Outlook 5cc57f5845c446f6d7a21b920e71d91056bf8157 6 259 1766 2022-11-11T17:40:17Z Johnny 51 wikitext text/x-wiki Synchronisation status 27433a2a4072f0890bf8442c062eb679cc496bb8 6 260 1767 2022-11-11T17:49:32Z Johnny 51 wikitext text/x-wiki How to share agenda 1f72c3dab57fe2721bc07135aa94c1c147758140 6 261 1768 2022-11-11T18:00:34Z Johnny 51 wikitext text/x-wiki Where to find iCal link through Outlook share-mail 9d362bcc1b3f9fa50d8d7d59a3200cfd3dc7851f 0 78 1769 1477 2022-11-11T18:05:11Z Johnny 51 /* Synchronizing your KU Leuven calendar */ wikitext text/x-wiki This guide will explain how your KU Leuven calendar, which you can see on Toledo, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Thunderbird, Outlook, Windows Calendar, etc.), following the steps below. = Synchronizing your KU Leuven calendar = [[File:Agenda Sync.png|thumb|234x234px|Image 1 - Where to find Agenda Sync]] Your first step will be to visit KU Loket via Toledo or by visiting [http://kuloket.be kuloket.be] . Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture in image 1. Now you will get an overview of your different agendas. Here you will need to select which one you wish to export. Next you will be presented a window with settings. The settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed further here. [[File:Agenda Synchronisation on.png|thumb|323x323px|Image 2 - Synchronisation status]] The only necessairy step here is to make sure our '''synchronisation is on'''. We can check this at the top of the page. If the synchronisation is off, simply select restart sync at the top right. It's possible you will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. It should look as shown in image 2. [[File:Agenda in Outlook.png|thumb|175x175px|Image 3 - Calendar in Outlook (web version)]] The following step will be to '''visit your personal student email'''. This can be done via Toledo or by visiting [https://owa.student.kuleuven.be owa.student.kuleuven.be]. This should bring you to your personal KU Leuven mailbox. On the left side of the page, you should see several icons (Mail, Calendar, People). Here you will need to '''select''' '''<nowiki/>'Calendar'''' (Image 3), which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are put on Toledo by your professors, should also be shown here now). If the calendar is still completely empty, make sure they're selected within 'My Calendars' on the left of your calendar overview. If it doesn't show up in this list, check if your agenda settings in KU Loket are set correctly according to image 2 and that you are looking at time period where classes are scheduled (not a holiday period). [[File:Select Agenda.png|thumb|196x196px|Image 4 - Sharing your agenda]] Continuing in the top right corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a dropdown where you can select which agenda you would like to share (Image 4) (In this case we want to select UURROOSTER). Next you'll be shown a 'Sharing and permissions' window. In here simply enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'Can view all details' is selected from the dropdown menu (this should be done by default). Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email. In this email you want to click the blue box with '''<nowiki/>'Accept and view calendar''''. [[File:ICalLink.png|thumb|261x261px|Image 5 - iCal link in Outlook sharing-mail]] At the top of this window you'll find a link ending on .ics, (Image 5) this is your iCal link. You'll want to copy this so you'll be able to import the agenda into your personal calendar. Importing the iCal link to your chosen personal agenda can vary widely depending on which personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 Almost all calendar services support importing iCal. If your chosen calendar service is not listed here, you can try searching the internet on how to import iCal for your service. [[Category:Tutorials]] 055fa58fdb81e680cb9f41803557bc731c3092e2 1770 1769 2022-11-11T18:05:30Z Johnny 51 /* Synchronizing your KU Leuven calendar */ wikitext text/x-wiki This guide will explain how your KU Leuven calendar, which you can see on Toledo, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Thunderbird, Outlook, Windows Calendar, etc.), following the steps below. = Synchronizing your KU Leuven calendar = [[File:Agenda Sync.png|thumb|234x234px|Image 1 - Where to find Agenda Sync]] Your first step will be to visit KU Loket via Toledo or by visiting [http://kuloket.be kuloket.be] . Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture in image 1. Now you will get an overview of your different agendas. Here you will need to select which one you wish to export. Next you will be presented a window with settings. The settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed further here. [[File:Agenda Synchronisation on.png|thumb|290x290px|Image 2 - Synchronisation status]] The only necessairy step here is to make sure our '''synchronisation is on'''. We can check this at the top of the page. If the synchronisation is off, simply select restart sync at the top right. It's possible you will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. It should look as shown in image 2. [[File:Agenda in Outlook.png|thumb|175x175px|Image 3 - Calendar in Outlook (web version)]] The following step will be to '''visit your personal student email'''. This can be done via Toledo or by visiting [https://owa.student.kuleuven.be owa.student.kuleuven.be]. This should bring you to your personal KU Leuven mailbox. On the left side of the page, you should see several icons (Mail, Calendar, People). Here you will need to '''select''' '''<nowiki/>'Calendar'''' (Image 3), which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are put on Toledo by your professors, should also be shown here now). If the calendar is still completely empty, make sure they're selected within 'My Calendars' on the left of your calendar overview. If it doesn't show up in this list, check if your agenda settings in KU Loket are set correctly according to image 2 and that you are looking at time period where classes are scheduled (not a holiday period). [[File:Select Agenda.png|thumb|196x196px|Image 4 - Sharing your agenda]] Continuing in the top right corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a dropdown where you can select which agenda you would like to share (Image 4) (In this case we want to select UURROOSTER). Next you'll be shown a 'Sharing and permissions' window. In here simply enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'Can view all details' is selected from the dropdown menu (this should be done by default). Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email. In this email you want to click the blue box with '''<nowiki/>'Accept and view calendar''''. [[File:ICalLink.png|thumb|261x261px|Image 5 - iCal link in Outlook sharing-mail]] At the top of this window you'll find a link ending on .ics, (Image 5) this is your iCal link. You'll want to copy this so you'll be able to import the agenda into your personal calendar. Importing the iCal link to your chosen personal agenda can vary widely depending on which personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 Almost all calendar services support importing iCal. If your chosen calendar service is not listed here, you can try searching the internet on how to import iCal for your service. [[Category:Tutorials]] 583eec85b2166e14b1323d7fc7c3db7276aa0c7e 1771 1770 2022-11-11T18:06:14Z Johnny 51 wikitext text/x-wiki This guide will explain how your KU Leuven calendar, which you can see on Toledo, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Thunderbird, Outlook, Windows Calendar, etc.), following the steps below. = Synchronizing your KU Leuven calendar = [[File:Agenda Sync.png|thumb|234x234px|Image 1 - Where to find Agenda Sync]] Your first step will be to visit KU Loket via Toledo or by visiting [http://kuloket.be kuloket.be] . Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture in image 1. Now you will get an overview of your different agendas. Here you will need to select which one you wish to export. Next you will be presented a window with settings. The settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed further here. [[File:Agenda Synchronisation on.png|thumb|240x240px|Image 2 - Synchronisation status]] The only necessairy step here is to make sure our '''synchronisation is on'''. We can check this at the top of the page. If the synchronisation is off, simply select restart sync at the top right. It's possible you will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. It should look as shown in image 2. [[File:Agenda in Outlook.png|thumb|153x153px|Image 3 - Calendar in Outlook (web version)]] The following step will be to '''visit your personal student email'''. This can be done via Toledo or by visiting [https://owa.student.kuleuven.be owa.student.kuleuven.be]. This should bring you to your personal KU Leuven mailbox. On the left side of the page, you should see several icons (Mail, Calendar, People). Here you will need to '''select''' '''<nowiki/>'Calendar'''' (Image 3), which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are put on Toledo by your professors, should also be shown here now). If the calendar is still completely empty, make sure they're selected within 'My Calendars' on the left of your calendar overview. If it doesn't show up in this list, check if your agenda settings in KU Loket are set correctly according to image 2 and that you are looking at time period where classes are scheduled (not a holiday period). [[File:Select Agenda.png|thumb|196x196px|Image 4 - Sharing your agenda]] Continuing in the top right corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a dropdown where you can select which agenda you would like to share (Image 4) (In this case we want to select UURROOSTER). Next you'll be shown a 'Sharing and permissions' window. In here simply enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'Can view all details' is selected from the dropdown menu (this should be done by default). Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email. In this email you want to click the blue box with '''<nowiki/>'Accept and view calendar''''. [[File:ICalLink.png|thumb|261x261px|Image 5 - iCal link in Outlook sharing-mail]] At the top of this window you'll find a link ending on .ics, (Image 5) this is your iCal link. You'll want to copy this so you'll be able to import the agenda into your personal calendar. Importing the iCal link to your chosen personal agenda can vary widely depending on which personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 Almost all calendar services support importing iCal. If your chosen calendar service is not listed here, you can try searching the internet on how to import iCal for your service. [[Category:Tutorials]] 8f5c713ecac480b51c6758134195d6103d5590f3 1772 1771 2022-11-11T19:53:38Z Johnny 51 /* Synchronizing your KU Leuven calendar */ wikitext text/x-wiki This guide will explain how your KU Leuven calendar, which you can see on Toledo, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Thunderbird, Outlook, Windows Calendar, etc.), following the steps below. = Synchronizing your KU Leuven calendar = [[File:Agenda Sync.png|thumb|234x234px|Image 1 - Where to find Agenda Sync]] Your first step will be to visit KU Loket via Toledo or by visiting [http://kuloket.be kuloket.be] . Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture in image 1. Now you will get an overview of your different agendas. Here you will need to select which one you wish to export. Next you will be presented a window with settings. The settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed further here. [[File:Agenda Synchronisation on.png|thumb|240x240px|Image 2 - Synchronisation status]] The only necessairy step here is to make sure our '''synchronisation is on'''. We can check this at the top of the page. If the synchronisation is off, simply select restart sync at the top right. It's possible you will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. It should look as shown in image 2. [[File:Agenda in Outlook.png|thumb|194x194px|Image 3 - Calendar in Outlook (web version)|alt=|left]] The following step will be to '''visit your personal student email'''. This can be done via Toledo or by visiting [https://owa.student.kuleuven.be owa.student.kuleuven.be]. This should bring you to your personal KU Leuven mailbox. On the left side of the page, you should see several icons (Mail, Calendar, People). Here you will need to '''select''' '''<nowiki/>'Calendar'''' (Image 3), which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are put on Toledo by your professors, should also be shown here now). If the calendar is still completely empty, make sure they're selected within 'My Calendars' on the left of your calendar overview. If it doesn't show up in this list, check if your agenda settings in KU Loket are set correctly according to image 2 and that you are looking at time period where classes are scheduled (not a holiday period). [[File:Select Agenda.png|thumb|196x196px|Image 4 - Sharing your agenda]] Continuing in the top right corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a dropdown where you can select which agenda you would like to share (Image 4) (In this case we want to select UURROOSTER). Next you'll be shown a 'Sharing and permissions' window. In here simply enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'Can view all details' is selected from the dropdown menu (this should be done by default). Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email. In this email you want to click the blue box with '''<nowiki/>'Accept and view calendar''''. [[File:ICalLink.png|thumb|261x261px|Image 5 - iCal link in Outlook sharing-mail]] At the top of this window you'll find a link ending on .ics, (Image 5) this is your iCal link. You'll want to copy this so you'll be able to import the agenda into your personal calendar. Importing the iCal link to your chosen personal agenda can vary widely depending on which personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 Almost all calendar services support importing iCal. If your chosen calendar service is not listed here, you can try searching the internet on how to import iCal for your service. [[Category:Tutorials]] 0ad26e69556c6cefba87c2371a40e8f5d9e4742b 1773 1772 2022-11-11T19:54:27Z Johnny 51 /* Synchronizing your KU Leuven calendar */ wikitext text/x-wiki This guide will explain how your KU Leuven calendar, which you can see on Toledo, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Thunderbird, Outlook, Windows Calendar, etc.), following the steps below. = Synchronizing your KU Leuven calendar = [[File:Agenda Sync.png|thumb|234x234px|Image 1 - Where to find Agenda Sync]] Your first step will be to visit KU Loket via Toledo or by visiting [http://kuloket.be kuloket.be] . Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture in image 1. Now you will get an overview of your different agendas. Here you will need to select which one you wish to export. Next you will be presented a window with settings. The settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed further here. [[File:Agenda Synchronisation on.png|thumb|240x240px|Image 2 - Synchronisation status|alt=|left]] The only necessairy step here is to make sure our '''synchronisation is on'''. We can check this at the top of the page. If the synchronisation is off, simply select restart sync at the top right. It's possible you will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. It should look as shown in image 2. [[File:Agenda in Outlook.png|thumb|194x194px|Image 3 - Calendar in Outlook (web version)|alt=]] The following step will be to '''visit your personal student email'''. This can be done via Toledo or by visiting [https://owa.student.kuleuven.be owa.student.kuleuven.be]. This should bring you to your personal KU Leuven mailbox. On the left side of the page, you should see several icons (Mail, Calendar, People). Here you will need to '''select''' '''<nowiki/>'Calendar'''' (Image 3), which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are put on Toledo by your professors, should also be shown here now). If the calendar is still completely empty, make sure they're selected within 'My Calendars' on the left of your calendar overview. If it doesn't show up in this list, check if your agenda settings in KU Loket are set correctly according to image 2 and that you are looking at time period where classes are scheduled (not a holiday period). [[File:Select Agenda.png|thumb|196x196px|Image 4 - Sharing your agenda]] Continuing in the top right corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a dropdown where you can select which agenda you would like to share (Image 4) (In this case we want to select UURROOSTER). Next you'll be shown a 'Sharing and permissions' window. In here simply enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'Can view all details' is selected from the dropdown menu (this should be done by default). Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email. In this email you want to click the blue box with '''<nowiki/>'Accept and view calendar''''. [[File:ICalLink.png|thumb|261x261px|Image 5 - iCal link in Outlook sharing-mail]] At the top of this window you'll find a link ending on .ics, (Image 5) this is your iCal link. You'll want to copy this so you'll be able to import the agenda into your personal calendar. Importing the iCal link to your chosen personal agenda can vary widely depending on which personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 Almost all calendar services support importing iCal. If your chosen calendar service is not listed here, you can try searching the internet on how to import iCal for your service. [[Category:Tutorials]] 97df2655d4274fc3e97d2488eb2d7329a756d625 1774 1773 2022-11-11T19:55:27Z Johnny 51 /* Synchronizing your KU Leuven calendar */ wikitext text/x-wiki This guide will explain how your KU Leuven calendar, which you can see on Toledo, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Thunderbird, Outlook, Windows Calendar, etc.), following the steps below. = Synchronizing your KU Leuven calendar = [[File:Agenda Sync.png|thumb|234x234px|Image 1 - Where to find Agenda Sync]] Your first step will be to visit KU Loket via Toledo or by visiting [http://kuloket.be kuloket.be] . Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture in image 1. Now you will get an overview of your different agendas. Here you will need to select which one you wish to export. Next you will be presented a window with settings. The settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed further here. [[File:Agenda Synchronisation on.png|thumb|375x375px|Image 2 - Synchronisation status|alt=]] The only necessairy step here is to make sure our '''synchronisation is on'''. We can check this at the top of the page. If the synchronisation is off, simply select restart sync at the top right. It's possible you will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. It should look as shown in image 2. [[File:Agenda in Outlook.png|thumb|217x217px|Image 3 - Calendar in Outlook (web version)|alt=]] The following step will be to '''visit your personal student email'''. This can be done via Toledo or by visiting [https://owa.student.kuleuven.be owa.student.kuleuven.be]. This should bring you to your personal KU Leuven mailbox. On the left side of the page, you should see several icons (Mail, Calendar, People). Here you will need to '''select''' '''<nowiki/>'Calendar'''' (Image 3), which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are put on Toledo by your professors, should also be shown here now). If the calendar is still completely empty, make sure they're selected within 'My Calendars' on the left of your calendar overview. If it doesn't show up in this list, check if your agenda settings in KU Loket are set correctly according to image 2 and that you are looking at time period where classes are scheduled (not a holiday period). [[File:Select Agenda.png|thumb|196x196px|Image 4 - Sharing your agenda]] Continuing in the top right corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a dropdown where you can select which agenda you would like to share (Image 4) (In this case we want to select UURROOSTER). Next you'll be shown a 'Sharing and permissions' window. In here simply enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'Can view all details' is selected from the dropdown menu (this should be done by default). Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email. In this email you want to click the blue box with '''<nowiki/>'Accept and view calendar''''. [[File:ICalLink.png|thumb|261x261px|Image 5 - iCal link in Outlook sharing-mail]] At the top of this window you'll find a link ending on .ics, (Image 5) this is your iCal link. You'll want to copy this so you'll be able to import the agenda into your personal calendar. Importing the iCal link to your chosen personal agenda can vary widely depending on which personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 Almost all calendar services support importing iCal. If your chosen calendar service is not listed here, you can try searching the internet on how to import iCal for your service. [[Category:Tutorials]] 38171e79186ec198c7db248e7275eb0dfb23af30 1775 1774 2022-11-11T19:55:52Z Johnny 51 /* Synchronizing your KU Leuven calendar */ wikitext text/x-wiki This guide will explain how your KU Leuven calendar, which you can see on Toledo, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Thunderbird, Outlook, Windows Calendar, etc.), following the steps below. = Synchronizing your KU Leuven calendar = [[File:Agenda Sync.png|thumb|234x234px|Image 1 - Where to find Agenda Sync]] Your first step will be to visit KU Loket via Toledo or by visiting [http://kuloket.be kuloket.be] . Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture in image 1. Now you will get an overview of your different agendas. Here you will need to select which one you wish to export. Next you will be presented a window with settings. The settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed further here. [[File:Agenda Synchronisation on.png|thumb|375x375px|Image 2 - Synchronisation status|alt=]] The only necessairy step here is to make sure our '''synchronisation is on'''. We can check this at the top of the page. If the synchronisation is off, simply select restart sync at the top right. It's possible you will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. It should look as shown in image 2. [[File:Agenda in Outlook.png|thumb|217x217px|Image 3 - Calendar in Outlook (web version)|alt=]] The following step will be to '''visit your personal student email'''. This can be done via Toledo or by visiting [https://owa.student.kuleuven.be owa.student.kuleuven.be]. This should bring you to your personal KU Leuven mailbox. On the left side of the page, you should see several icons (Mail, Calendar, People). Here you will need to '''select''' '''<nowiki/>'Calendar'''' (Image 3), which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are put on Toledo by your professors, should also be shown here now). If the calendar is still completely empty, make sure they're selected within 'My Calendars' on the left of your calendar overview. If it doesn't show up in this list, check if your agenda settings in KU Loket are set correctly according to image 2 and that you are looking at time period where classes are scheduled (not a holiday period). [[File:Select Agenda.png|thumb|196x196px|Image 4 - Sharing your agenda]] Continuing in the top right corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a dropdown where you can select which agenda you would like to share (Image 4) (In this case we want to select UURROOSTER). Next you'll be shown a 'Sharing and permissions' window. In here simply enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'Can view all details' is selected from the dropdown menu (this should be done by default). Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email. In this email you want to click the blue box with '''<nowiki/>'Accept and view calendar''''. [[File:ICalLink.png|thumb|261x261px|Image 5 - iCal link in Outlook sharing-mail]] At the top of this window you'll find a link ending on .ics, (Image 5) this is your iCal link. You'll want to copy this so you'll be able to import the agenda into your personal calendar. Importing the iCal link to your chosen personal agenda can vary widely depending on which personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 Almost all calendar services support importing iCal. If your chosen calendar service is not listed here, you can try searching the internet on how to import iCal for your service. [[Category:Tutorials]] 3706f8b07934692fb2fbc894e65e32d702cd77c4 1776 1775 2022-11-11T19:56:27Z Johnny 51 /* Synchronizing your KU Leuven calendar */ wikitext text/x-wiki This guide will explain how your KU Leuven calendar, which you can see on Toledo, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Thunderbird, Outlook, Windows Calendar, etc.), following the steps below. = Synchronizing your KU Leuven calendar = [[File:Agenda Sync.png|thumb|234x234px|Image 1 - Where to find Agenda Sync]] Your first step will be to visit KU Loket via Toledo or by visiting [http://kuloket.be kuloket.be] . Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture in image 1. Now you will get an overview of your different agendas. Here you will need to select which one you wish to export. Next you will be presented a window with settings. The settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed further here. [[File:Agenda Synchronisation on.png|thumb|368x368px|Image 2 - Synchronisation status|alt=]] The only necessairy step here is to make sure our '''synchronisation is on'''. We can check this at the top of the page. If the synchronisation is off, simply select restart sync at the top right. It's possible you will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. It should look as shown in image 2. [[File:Agenda in Outlook.png|thumb|188x188px|Image 3 - Calendar in Outlook (web version)|alt=]] The following step will be to '''visit your personal student email'''. This can be done via Toledo or by visiting [https://owa.student.kuleuven.be owa.student.kuleuven.be]. This should bring you to your personal KU Leuven mailbox. On the left side of the page, you should see several icons (Mail, Calendar, People). Here you will need to '''select''' '''<nowiki/>'Calendar'''' (Image 3), which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are put on Toledo by your professors, should also be shown here now). If the calendar is still completely empty, make sure they're selected within 'My Calendars' on the left of your calendar overview. If it doesn't show up in this list, check if your agenda settings in KU Loket are set correctly according to image 2 and that you are looking at time period where classes are scheduled (not a holiday period). [[File:Select Agenda.png|thumb|196x196px|Image 4 - Sharing your agenda]] Continuing in the top right corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a dropdown where you can select which agenda you would like to share (Image 4) (In this case we want to select UURROOSTER). Next you'll be shown a 'Sharing and permissions' window. In here simply enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'Can view all details' is selected from the dropdown menu (this should be done by default). Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email. In this email you want to click the blue box with '''<nowiki/>'Accept and view calendar''''. [[File:ICalLink.png|thumb|261x261px|Image 5 - iCal link in Outlook sharing-mail]] At the top of this window you'll find a link ending on .ics, (Image 5) this is your iCal link. You'll want to copy this so you'll be able to import the agenda into your personal calendar. Importing the iCal link to your chosen personal agenda can vary widely depending on which personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 Almost all calendar services support importing iCal. If your chosen calendar service is not listed here, you can try searching the internet on how to import iCal for your service. [[Category:Tutorials]] 9eb75ba6e71be6644e12eaa263f4ad081768687f 1777 1776 2022-11-11T19:56:42Z Johnny 51 /* Synchronizing your KU Leuven calendar */ wikitext text/x-wiki This guide will explain how your KU Leuven calendar, which you can see on Toledo, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Thunderbird, Outlook, Windows Calendar, etc.), following the steps below. = Synchronizing your KU Leuven calendar = [[File:Agenda Sync.png|thumb|234x234px|Image 1 - Where to find Agenda Sync]] Your first step will be to visit KU Loket via Toledo or by visiting [http://kuloket.be kuloket.be] . Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture in image 1. Now you will get an overview of your different agendas. Here you will need to select which one you wish to export. Next you will be presented a window with settings. The settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed further here. [[File:Agenda Synchronisation on.png|thumb|368x368px|Image 2 - Synchronisation status|alt=]] The only necessairy step here is to make sure our '''synchronisation is on'''. We can check this at the top of the page. If the synchronisation is off, simply select restart sync at the top right. It's possible you will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. It should look as shown in image 2. [[File:Agenda in Outlook.png|thumb|188x188px|Image 3 - Calendar in Outlook (web version)|alt=]] The following step will be to '''visit your personal student email'''. This can be done via Toledo or by visiting [https://owa.student.kuleuven.be owa.student.kuleuven.be]. This should bring you to your personal KU Leuven mailbox. On the left side of the page, you should see several icons (Mail, Calendar, People). Here you will need to '''select''' '''<nowiki/>'Calendar'''' (Image 3), which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are put on Toledo by your professors, should also be shown here now). If the calendar is still completely empty, make sure they're selected within 'My Calendars' on the left of your calendar overview. If it doesn't show up in this list, check if your agenda settings in KU Loket are set correctly according to image 2 and that you are looking at time period where classes are scheduled (not a holiday period). [[File:Select Agenda.png|thumb|196x196px|Image 4 - Sharing your agenda]] Continuing in the top right corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a dropdown where you can select which agenda you would like to share (Image 4) (In this case we want to select UURROOSTER). Next you'll be shown a 'Sharing and permissions' window. In here simply enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'Can view all details' is selected from the dropdown menu (this should be done by default). Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email. In this email you want to click the blue box with '''<nowiki/>'Accept and view calendar''''. [[File:ICalLink.png|thumb|261x261px|Image 5 - iCal link in Outlook sharing-mail]] At the top of this window you'll find a link ending on .ics, (Image 5) this is your iCal link. You'll want to copy this so you'll be able to import the agenda into your personal calendar. Importing the iCal link to your chosen personal agenda can vary widely depending on which personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 Almost all calendar services support importing iCal. If your chosen calendar service is not listed here, you can try searching the internet on how to import iCal for your service. [[Category:Tutorials]] dffa3e61b1453e319ce834f210edeb06243183a5 1778 1777 2022-11-11T19:58:14Z Johnny 51 /* Synchronizing your KU Leuven calendar */ wikitext text/x-wiki This guide will explain how your KU Leuven calendar, which you can see on Toledo, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Thunderbird, Outlook, Windows Calendar, etc.), following the steps below. = Synchronizing your KU Leuven calendar = [[File:Agenda Sync.png|thumb|234x234px|Image 1 - Where to find Agenda Sync]] Your first step will be to visit KU Loket via Toledo or by visiting [http://kuloket.be kuloket.be] . Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture in image 1. Now you will get an overview of your different agendas. Here you will need to select which one you wish to export. Next you will be presented a window with settings. The settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed further here. [[File:Agenda Synchronisation on.png|thumb|368x368px|Image 2 - Synchronisation status|alt=]] The only necessairy step here is to make sure our '''synchronisation is on'''. We can check this at the top of the page. If the synchronisation is off, simply select restart sync at the top right. It's possible you will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. It should look as shown in image 2. [[File:Agenda in Outlook.png|thumb|296x296px]] The following step will be to '''visit your personal student email'''. This can be done via Toledo or by visiting [https://owa.student.kuleuven.be owa.student.kuleuven.be]. This should bring you to your personal KU Leuven mailbox. On the left side of the page, you should see several icons (Mail, Calendar, People). Here you will need to '''select''' '''<nowiki/>'Calendar'''' (Image 3), which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are put on Toledo by your professors, should also be shown here now). If the calendar is still completely empty, make sure they're selected within 'My Calendars' on the left of your calendar overview. If it doesn't show up in this list, check if your agenda settings in KU Loket are set correctly according to image 2 and that you are looking at time period where classes are scheduled (not a holiday period). [[File:Select Agenda.png|thumb|240x240px|Image 4 - Sharing your agenda]] Continuing in the top right corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a dropdown where you can select which agenda you would like to share (Image 4) (In this case we want to select UURROOSTER). Next you'll be shown a 'Sharing and permissions' window. In here simply enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'Can view all details' is selected from the dropdown menu (this should be done by default). Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email. In this email you want to click the blue box with '''<nowiki/>'Accept and view calendar''''. [[File:ICalLink.png|thumb|261x261px|Image 5 - iCal link in Outlook sharing-mail]] At the top of this window you'll find a link ending on .ics, (Image 5) this is your iCal link. You'll want to copy this so you'll be able to import the agenda into your personal calendar. Importing the iCal link to your chosen personal agenda can vary widely depending on which personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 Almost all calendar services support importing iCal. If your chosen calendar service is not listed here, you can try searching the internet on how to import iCal for your service. [[Category:Tutorials]] 075e170a29a70b9ddd74c1cf55492bead284514b 1779 1778 2022-11-11T19:59:13Z Johnny 51 /* Synchronizing your KU Leuven calendar */ wikitext text/x-wiki This guide will explain how your KU Leuven calendar, which you can see on Toledo, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Thunderbird, Outlook, Windows Calendar, etc.), following the steps below. = Synchronizing your KU Leuven calendar = [[File:Agenda Sync.png|thumb|235x235px|Image 1 - Where to find Agenda Sync]] Your first step will be to visit KU Loket via Toledo or by visiting [http://kuloket.be kuloket.be] . Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture in image 1. Now you will get an overview of your different agendas. Here you will need to select which one you wish to export. Next you will be presented a window with settings. The settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed further here. [[File:Agenda Synchronisation on.png|thumb|304x304px|Image 2 - Synchronisation status|alt=]] The only necessairy step here is to make sure our '''synchronisation is on'''. We can check this at the top of the page. If the synchronisation is off, simply select restart sync at the top right. It's possible you will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. It should look as shown in image 2. [[File:Agenda in Outlook.png|thumb|249x249px]] The following step will be to '''visit your personal student email'''. This can be done via Toledo or by visiting [https://owa.student.kuleuven.be owa.student.kuleuven.be]. This should bring you to your personal KU Leuven mailbox. On the left side of the page, you should see several icons (Mail, Calendar, People). Here you will need to '''select''' '''<nowiki/>'Calendar'''' (Image 3), which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are put on Toledo by your professors, should also be shown here now). If the calendar is still completely empty, make sure they're selected within 'My Calendars' on the left of your calendar overview. If it doesn't show up in this list, check if your agenda settings in KU Loket are set correctly according to image 2 and that you are looking at time period where classes are scheduled (not a holiday period). '''<nowiki/>'''[[File:Select Agenda.png|thumb|240x240px|Image 4 - Sharing your agenda]] Continuing in the top right corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a dropdown where you can select which agenda you would like to share (Image 4) (In this case we want to select UURROOSTER). Next you'll be shown a 'Sharing and permissions' window. In here simply enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'Can view all details' is selected from the dropdown menu (this should be done by default). Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email. In this email you want to click the blue box with '''<nowiki/>'Accept and view calendar''''. [[File:ICalLink.png|thumb|261x261px|Image 5 - iCal link in Outlook sharing-mail]] At the top of this window you'll find a link ending on .ics, (Image 5) this is your iCal link. You'll want to copy this so you'll be able to import the agenda into your personal calendar. Importing the iCal link to your chosen personal agenda can vary widely depending on which personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 Almost all calendar services support importing iCal. If your chosen calendar service is not listed here, you can try searching the internet on how to import iCal for your service. [[Category:Tutorials]] dc26eee4a0b93ffff98a86f6ab96e98eff322dd4 1780 1779 2022-11-11T19:59:47Z Johnny 51 /* Synchronizing your KU Leuven calendar */ wikitext text/x-wiki This guide will explain how your KU Leuven calendar, which you can see on Toledo, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Thunderbird, Outlook, Windows Calendar, etc.), following the steps below. = Synchronizing your KU Leuven calendar = [[File:Agenda Sync.png|thumb|235x235px|Image 1 - Where to find Agenda Sync]] Your first step will be to visit KU Loket via Toledo or by visiting [http://kuloket.be kuloket.be] . Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture in image 1. Now you will get an overview of your different agendas. Here you will need to select which one you wish to export. Next you will be presented a window with settings. The settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed further here. [[File:Agenda Synchronisation on.png|thumb|304x304px|Image 2 - Synchronisation status|alt=]] The only necessairy step here is to make sure our '''synchronisation is on'''. We can check this at the top of the page. If the synchronisation is off, simply select restart sync at the top right. It's possible you will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. It should look as shown in image 2. [[File:Agenda in Outlook.png|thumb|209x209px|Image 3 - Calendar in Outlook]] The following step will be to '''visit your personal student email'''. This can be done via Toledo or by visiting [https://owa.student.kuleuven.be owa.student.kuleuven.be]. This should bring you to your personal KU Leuven mailbox. On the left side of the page, you should see several icons (Mail, Calendar, People). Here you will need to '''select''' '''<nowiki/>'Calendar'''' (Image 3), which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are put on Toledo by your professors, should also be shown here now). If the calendar is still completely empty, make sure they're selected within 'My Calendars' on the left of your calendar overview. If it doesn't show up in this list, check if your agenda settings in KU Loket are set correctly according to image 2 and that you are looking at time period where classes are scheduled (not a holiday period). '''<nowiki/>'''[[File:Select Agenda.png|thumb|240x240px|Image 4 - Sharing your agenda]] Continuing in the top right corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a dropdown where you can select which agenda you would like to share (Image 4) (In this case we want to select UURROOSTER). Next you'll be shown a 'Sharing and permissions' window. In here simply enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'Can view all details' is selected from the dropdown menu (this should be done by default). Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email. In this email you want to click the blue box with '''<nowiki/>'Accept and view calendar''''. [[File:ICalLink.png|thumb|261x261px|Image 5 - iCal link in Outlook sharing-mail]] At the top of this window you'll find a link ending on .ics, (Image 5) this is your iCal link. You'll want to copy this so you'll be able to import the agenda into your personal calendar. Importing the iCal link to your chosen personal agenda can vary widely depending on which personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 Almost all calendar services support importing iCal. If your chosen calendar service is not listed here, you can try searching the internet on how to import iCal for your service. [[Category:Tutorials]] caf1aed083b03f92c562277300d5df7f5c5400cc 1781 1780 2022-11-11T20:00:01Z Johnny 51 /* Synchronizing your KU Leuven calendar */ wikitext text/x-wiki This guide will explain how your KU Leuven calendar, which you can see on Toledo, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Thunderbird, Outlook, Windows Calendar, etc.), following the steps below. = Synchronizing your KU Leuven calendar = [[File:Agenda Sync.png|thumb|235x235px|Image 1 - Where to find Agenda Sync]] Your first step will be to visit KU Loket via Toledo or by visiting [http://kuloket.be kuloket.be] . Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture in image 1. Now you will get an overview of your different agendas. Here you will need to select which one you wish to export. Next you will be presented a window with settings. The settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed further here. [[File:Agenda Synchronisation on.png|thumb|268x268px|Image 2 - Synchronisation status|alt=]] The only necessairy step here is to make sure our '''synchronisation is on'''. We can check this at the top of the page. If the synchronisation is off, simply select restart sync at the top right. It's possible you will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. It should look as shown in image 2. [[File:Agenda in Outlook.png|thumb|209x209px|Image 3 - Calendar in Outlook]] The following step will be to '''visit your personal student email'''. This can be done via Toledo or by visiting [https://owa.student.kuleuven.be owa.student.kuleuven.be]. This should bring you to your personal KU Leuven mailbox. On the left side of the page, you should see several icons (Mail, Calendar, People). Here you will need to '''select''' '''<nowiki/>'Calendar'''' (Image 3), which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are put on Toledo by your professors, should also be shown here now). If the calendar is still completely empty, make sure they're selected within 'My Calendars' on the left of your calendar overview. If it doesn't show up in this list, check if your agenda settings in KU Loket are set correctly according to image 2 and that you are looking at time period where classes are scheduled (not a holiday period). '''<nowiki/>'''[[File:Select Agenda.png|thumb|240x240px|Image 4 - Sharing your agenda]] Continuing in the top right corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a dropdown where you can select which agenda you would like to share (Image 4) (In this case we want to select UURROOSTER). Next you'll be shown a 'Sharing and permissions' window. In here simply enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'Can view all details' is selected from the dropdown menu (this should be done by default). Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email. In this email you want to click the blue box with '''<nowiki/>'Accept and view calendar''''. [[File:ICalLink.png|thumb|261x261px|Image 5 - iCal link in Outlook sharing-mail]] At the top of this window you'll find a link ending on .ics, (Image 5) this is your iCal link. You'll want to copy this so you'll be able to import the agenda into your personal calendar. Importing the iCal link to your chosen personal agenda can vary widely depending on which personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 Almost all calendar services support importing iCal. If your chosen calendar service is not listed here, you can try searching the internet on how to import iCal for your service. [[Category:Tutorials]] ae9dc069d33364de1dfcb801e9c0b9a5c0bafc07 1782 1781 2022-11-11T20:01:22Z Johnny 51 /* Synchronizing your KU Leuven calendar */ wikitext text/x-wiki This guide will explain how your KU Leuven calendar, which you can see on Toledo, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Thunderbird, Outlook, Windows Calendar, etc.), following the steps below. = Synchronizing your KU Leuven calendar = [[File:Agenda Sync.png|thumb|235x235px|Image 1 - Where to find Agenda Sync]] Your first step will be to visit KU Loket via Toledo or by visiting [http://kuloket.be kuloket.be] . Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture in image 1. Now you will get an overview of your different agendas. Here you will need to select which one you wish to export. Next you will be presented a window with settings. The settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed further here. [[File:Agenda Synchronisation on.png|thumb|268x268px|Image 2 - Synchronisation status|alt=]] The only necessairy step here is to make sure our '''synchronisation is on'''. We can check this at the top of the page. If the synchronisation is off, simply select restart sync at the top right. It's possible you will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. It should look as shown in image 2. [[File:Agenda in Outlook.png|thumb|209x209px|Image 3 - Calendar in Outlook]] The following step will be to '''visit your personal student email'''. This can be done via Toledo or by visiting [https://owa.student.kuleuven.be owa.student.kuleuven.be]. This should bring you to your personal KU Leuven mailbox. On the left side of the page, you should see several icons (Mail, Calendar, People). Here you will need to '''select''' '''<nowiki/>'Calendar'''' (Image 3), which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are put on Toledo by your professors, should also be shown here now). If the calendar is still completely empty, make sure they're selected within 'My Calendars' on the left of your calendar overview. If it doesn't show up in this list, check if your agenda settings in KU Loket are set correctly according to image 2 and that you are looking at time period where classes are scheduled (not a holiday period). '''<nowiki/>''' '''<nowiki/>'''[[File:Select Agenda.png|thumb|240x240px|Image 4 - Sharing your agenda]] Continuing in the top right corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a dropdown where you can select which agenda you would like to share (Image 4) (In this case we want to select UURROOSTER). Next you'll be shown a 'Sharing and permissions' window. In here simply enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'Can view all details' is selected from the dropdown menu (this should be done by default). Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email. In this email you want to click the blue box with '''<nowiki/>'Accept and view calendar''''. [[File:ICalLink.png|thumb|261x261px|Image 5 - iCal link in Outlook sharing-mail]] At the top of this window you'll find a link ending on .ics, (Image 5) this is your iCal link. You'll want to copy this so you'll be able to import the agenda into your personal calendar. Importing the iCal link to your chosen personal agenda can vary widely depending on which personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 Almost all calendar services support importing iCal. If your chosen calendar service is not listed here, you can try searching the internet on how to import iCal for your service. [[Category:Tutorials]] 31d2b16a6070a246558363d5a4cbe7dc6623d799 1783 1782 2022-11-11T20:03:32Z Johnny 51 /* Synchronizing your KU Leuven calendar */ wikitext text/x-wiki This guide will explain how your KU Leuven calendar, which you can see on Toledo, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Thunderbird, Outlook, Windows Calendar, etc.), following the steps below. = Synchronizing your KU Leuven calendar = [[File:Agenda Sync.png|thumb|235x235px|Image 1 - Where to find Agenda Sync]] Your first step will be to visit KU Loket via Toledo or by visiting [http://kuloket.be kuloket.be] . Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture in image 1. Now you will get an overview of your different agendas. Here you will need to select which one you wish to export. Next you will be presented a window with settings. The settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed further here. [[File:Agenda Synchronisation on.png|thumb|268x268px|Image 2 - Synchronisation status|alt=]] The only necessairy step here is to make sure our '''synchronisation is on'''. We can check this at the top of the page. If the synchronisation is off, simply select restart sync at the top right. It's possible you will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. It should look as shown in image 2. [[File:Agenda in Outlook.png|thumb|209x209px|Image 3 - Calendar in Outlook]] The following step will be to '''visit your personal student email'''. This can be done via Toledo or by visiting [https://owa.student.kuleuven.be owa.student.kuleuven.be]. This should bring you to your personal KU Leuven mailbox. On the left side of the page, you should see several icons (Mail, Calendar, People). Here you will need to '''select''' '''<nowiki/>'Calendar'''' (Image 3), which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are put on Toledo by your professors, should also be shown here now). If the calendar is still completely empty, make sure they're selected within 'My Calendars' on the left of your calendar overview. If it doesn't show up in this list, check if your agenda settings in KU Loket are set correctly according to image 2 and that you are looking at time period where classes are scheduled (not a holiday period). '''<nowiki/>''' '''<nowiki/>'''[[File:Select Agenda.png|thumb|216x216px|Image 4 - Sharing your agenda]] Continuing in the top right corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a dropdown where you can select which agenda you would like to share (Image 4) (In this case we want to select UURROOSTER). Next you'll be shown a 'Sharing and permissions' window. In here simply enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'Can view all details' is selected from the dropdown menu (this should be done by default). Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email. In this email you want to click the blue box with '''<nowiki/>'Accept and view calendar''''. [[File:ICalLink.png|thumb|261x261px|Image 5 - iCal link in Outlook sharing-mail]] At the top of this window you'll find a link ending on .ics, (Image 5) this is your iCal link. You'll want to copy this so you'll be able to import the agenda into your personal calendar. Importing the iCal link to your chosen personal agenda can vary widely depending on which personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 Almost all calendar services support importing iCal. If your chosen calendar service is not listed here, you can try searching the internet on how to import iCal for your service. [[Category:Tutorials]] 93fac6e58f14e2511a54d41fd9b6815be894c6a5 1784 1783 2022-11-11T20:04:15Z Johnny 51 /* Synchronizing your KU Leuven calendar */ wikitext text/x-wiki This guide will explain how your KU Leuven calendar, which you can see on Toledo, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Thunderbird, Outlook, Windows Calendar, etc.), following the steps below. = Synchronizing your KU Leuven calendar = [[File:Agenda Sync.png|thumb|235x235px|Image 1 - Where to find Agenda Sync]] Your first step will be to visit KU Loket via Toledo or by visiting [http://kuloket.be kuloket.be] . Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture in image 1. Now you will get an overview of your different agendas. Here you will need to select which one you wish to export. Next you will be presented a window with settings. The settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed further here. [[File:Agenda Synchronisation on.png|thumb|268x268px|Image 2 - Synchronisation status|alt=]] The only necessairy step here is to make sure our '''synchronisation is on'''. We can check this at the top of the page. If the synchronisation is off, simply select restart sync at the top right. It's possible you will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. It should look as shown in image 2. [[File:Agenda in Outlook.png|thumb|209x209px|Image 3 - Calendar]] The following step will be to '''visit your personal student email'''. This can be done via Toledo or by visiting [https://owa.student.kuleuven.be owa.student.kuleuven.be]. This should bring you to your personal KU Leuven mailbox. On the left side of the page, you should see several icons (Mail, Calendar, People). Here you will need to '''select''' '''<nowiki/>'Calendar'''' (Image 3), which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are put on Toledo by your professors, should also be shown here now). If the calendar is still completely empty, make sure they're selected within 'My Calendars' on the left of your calendar overview. If it doesn't show up in this list, check if your agenda settings in KU Loket are set correctly according to image 2 and that you are looking at time period where classes are scheduled (not a holiday period). '''<nowiki/>''' '''<nowiki/>'''[[File:Select Agenda.png|thumb|216x216px|Image 4 - Sharing your agenda]] Continuing in the top right corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a dropdown where you can select which agenda you would like to share (Image 4) (In this case we want to select UURROOSTER). Next you'll be shown a 'Sharing and permissions' window. In here simply enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'Can view all details' is selected from the dropdown menu (this should be done by default). Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email. In this email you want to click the blue box with '''<nowiki/>'Accept and view calendar''''. [[File:ICalLink.png|thumb|261x261px|Image 5 - iCal link in Outlook sharing-mail]] At the top of this window you'll find a link ending on .ics, (Image 5) this is your iCal link. You'll want to copy this so you'll be able to import the agenda into your personal calendar. Importing the iCal link to your chosen personal agenda can vary widely depending on which personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 Almost all calendar services support importing iCal. If your chosen calendar service is not listed here, you can try searching the internet on how to import iCal for your service. [[Category:Tutorials]] 6743be0608686b2667210d54e0ff412d2091af1f 1785 1784 2022-11-11T20:08:33Z Johnny 51 /* Synchronizing your KU Leuven calendar */ wikitext text/x-wiki This guide will explain how your KU Leuven calendar, which you can see on Toledo, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Thunderbird, Outlook, Windows Calendar, etc.), following the steps below. = Synchronizing your KU Leuven calendar = [[File:Agenda Sync.png|thumb|235x235px|Image 1 - Where to find Agenda Sync]] Your first step will be to visit KU Loket via Toledo or by visiting [http://kuloket.be kuloket.be] . Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture in image 1. Now you will get an overview of your different agendas. Here you will need to select which one you wish to export. Next you will be presented a window with settings. The settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed further here. [[File:Agenda Synchronisation on.png|thumb|268x268px|Image 2 - Synchronisation status|alt=]] The only necessairy step here is to make sure our '''synchronisation is on'''. We can check this at the top of the page. If the synchronisation is off, simply select restart sync at the top right. It's possible you will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. It should look as shown in image 2. [[File:Agenda in Outlook.png|thumb|209x209px|Image 3 - Calendar]] The following step will be to '''visit your personal student email'''. This can be done via Toledo or by visiting [https://owa.student.kuleuven.be owa.student.kuleuven.be]. This should bring you to your personal KU Leuven mailbox. On the left side of the page, you should see several icons (Mail, Calendar, People). Here you will need to '''select''' '''<nowiki/>'Calendar'''' (Image 3), which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are put on Toledo by your professors, should also be shown here now). If the calendar is still completely empty, make sure they're selected within 'My Calendars' on the left of your calendar overview. If it doesn't show up in this list, check if your agenda settings in KU Loket are set correctly according to image 2 and that you are looking at time period where classes are scheduled (not a holiday period). '''<nowiki/>''' '''<nowiki/>''' '''<nowiki/>'''[[File:Select Agenda.png|thumb|216x216px|Image 4 - Sharing your agenda]] Continuing in the top right corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a dropdown where you can select which agenda you would like to share (Image 4) (In this case we want to select UURROOSTER). Next you'll be shown a 'Sharing and permissions' window. In here simply enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'Can view all details' is selected from the dropdown menu (this should be done by default). Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email. In this email you want to click the blue box with '''<nowiki/>'Accept and view calendar''''. [[File:ICalLink.png|thumb|261x261px|Image 5 - iCal link in Outlook sharing-mail]] At the top of this window you'll find a link ending on .ics, (Image 5) this is your iCal link. You'll want to copy this so you'll be able to import the agenda into your personal calendar. Importing the iCal link to your chosen personal agenda can vary widely depending on which personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 Almost all calendar services support importing iCal. If your chosen calendar service is not listed here, you can try searching the internet on how to import iCal for your service. [[Category:Tutorials]] a6fd5843f11a669e52afd0a47b29eda1aeb491c7 1786 1785 2022-11-11T20:08:43Z Johnny 51 /* Synchronizing your KU Leuven calendar */ wikitext text/x-wiki This guide will explain how your KU Leuven calendar, which you can see on Toledo, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Thunderbird, Outlook, Windows Calendar, etc.), following the steps below. = Synchronizing your KU Leuven calendar = [[File:Agenda Sync.png|thumb|235x235px|Image 1 - Where to find Agenda Sync]] Your first step will be to visit KU Loket via Toledo or by visiting [http://kuloket.be kuloket.be] . Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture in image 1. Now you will get an overview of your different agendas. Here you will need to select which one you wish to export. Next you will be presented a window with settings. The settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed further here. [[File:Agenda Synchronisation on.png|thumb|268x268px|Image 2 - Synchronisation status|alt=]] The only necessairy step here is to make sure our '''synchronisation is on'''. We can check this at the top of the page. If the synchronisation is off, simply select restart sync at the top right. It's possible you will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. It should look as shown in image 2. [[File:Agenda in Outlook.png|thumb|209x209px|Image 3 - Calendar]] The following step will be to '''visit your personal student email'''. This can be done via Toledo or by visiting [https://owa.student.kuleuven.be owa.student.kuleuven.be]. This should bring you to your personal KU Leuven mailbox. On the left side of the page, you should see several icons (Mail, Calendar, People). Here you will need to '''select''' '''<nowiki/>'Calendar'''' (Image 3), which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are put on Toledo by your professors, should also be shown here now). If the calendar is still completely empty, make sure they're selected within 'My Calendars' on the left of your calendar overview. If it doesn't show up in this list, check if your agenda settings in KU Loket are set correctly according to image 2 and that you are looking at time period where classes are scheduled (not a holiday period). '''<nowiki/>''' '''<nowiki/>''' '''<nowiki/>''' '''<nowiki/>'''[[File:Select Agenda.png|thumb|216x216px|Image 4 - Sharing your agenda]] Continuing in the top right corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a dropdown where you can select which agenda you would like to share (Image 4) (In this case we want to select UURROOSTER). Next you'll be shown a 'Sharing and permissions' window. In here simply enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'Can view all details' is selected from the dropdown menu (this should be done by default). Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email. In this email you want to click the blue box with '''<nowiki/>'Accept and view calendar''''. [[File:ICalLink.png|thumb|261x261px|Image 5 - iCal link in Outlook sharing-mail]] At the top of this window you'll find a link ending on .ics, (Image 5) this is your iCal link. You'll want to copy this so you'll be able to import the agenda into your personal calendar. Importing the iCal link to your chosen personal agenda can vary widely depending on which personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 Almost all calendar services support importing iCal. If your chosen calendar service is not listed here, you can try searching the internet on how to import iCal for your service. [[Category:Tutorials]] 2d2fbc5068e61f47feb6982f83b199417fbaded1 1787 1786 2022-11-11T20:09:00Z Johnny 51 /* Synchronizing your KU Leuven calendar */ wikitext text/x-wiki This guide will explain how your KU Leuven calendar, which you can see on Toledo, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Thunderbird, Outlook, Windows Calendar, etc.), following the steps below. = Synchronizing your KU Leuven calendar = [[File:Agenda Sync.png|thumb|235x235px|Image 1 - Where to find Agenda Sync]] Your first step will be to visit KU Loket via Toledo or by visiting [http://kuloket.be kuloket.be] . Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture in image 1. Now you will get an overview of your different agendas. Here you will need to select which one you wish to export. Next you will be presented a window with settings. The settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed further here. [[File:Agenda Synchronisation on.png|thumb|268x268px|Image 2 - Synchronisation status|alt=]] The only necessairy step here is to make sure our '''synchronisation is on'''. We can check this at the top of the page. If the synchronisation is off, simply select restart sync at the top right. It's possible you will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. It should look as shown in image 2. [[File:Agenda in Outlook.png|thumb|209x209px|Image 3 - Calendar]] The following step will be to '''visit your personal student email'''. This can be done via Toledo or by visiting [https://owa.student.kuleuven.be owa.student.kuleuven.be]. This should bring you to your personal KU Leuven mailbox. On the left side of the page, you should see several icons (Mail, Calendar, People). Here you will need to '''select''' '''<nowiki/>'Calendar'''' (Image 3), which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are put on Toledo by your professors, should also be shown here now). If the calendar is still completely empty, make sure they're selected within 'My Calendars' on the left of your calendar overview. If it doesn't show up in this list, check if your agenda settings in KU Loket are set correctly according to image 2 and that you are looking at time period where classes are scheduled (not a holiday period). '''<nowiki/>''' '''<nowiki/>''' '''<nowiki/>''' '''<nowiki/>''' '''<nowiki/>'''[[File:Select Agenda.png|thumb|216x216px|Image 4 - Sharing your agenda]] Continuing in the top right corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a dropdown where you can select which agenda you would like to share (Image 4) (In this case we want to select UURROOSTER). Next you'll be shown a 'Sharing and permissions' window. In here simply enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'Can view all details' is selected from the dropdown menu (this should be done by default). Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email. In this email you want to click the blue box with '''<nowiki/>'Accept and view calendar''''. [[File:ICalLink.png|thumb|261x261px|Image 5 - iCal link in Outlook sharing-mail]] At the top of this window you'll find a link ending on .ics, (Image 5) this is your iCal link. You'll want to copy this so you'll be able to import the agenda into your personal calendar. Importing the iCal link to your chosen personal agenda can vary widely depending on which personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 Almost all calendar services support importing iCal. If your chosen calendar service is not listed here, you can try searching the internet on how to import iCal for your service. [[Category:Tutorials]] 7411df0e11aec46d18f250831fbb86f94ac341ed 1788 1787 2022-11-11T20:09:26Z Johnny 51 /* Synchronizing your KU Leuven calendar */ wikitext text/x-wiki This guide will explain how your KU Leuven calendar, which you can see on Toledo, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Thunderbird, Outlook, Windows Calendar, etc.), following the steps below. = Synchronizing your KU Leuven calendar = [[File:Agenda Sync.png|thumb|235x235px|Image 1 - Where to find Agenda Sync]] Your first step will be to visit KU Loket via Toledo or by visiting [http://kuloket.be kuloket.be] . Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture in image 1. Now you will get an overview of your different agendas. Here you will need to select which one you wish to export. Next you will be presented a window with settings. The settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed further here. [[File:Agenda Synchronisation on.png|thumb|268x268px|Image 2 - Synchronisation status|alt=]] The only necessairy step here is to make sure our '''synchronisation is on'''. We can check this at the top of the page. If the synchronisation is off, simply select restart sync at the top right. It's possible you will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. It should look as shown in image 2. [[File:Agenda in Outlook.png|thumb|209x209px|Image 3 - Calendar]] The following step will be to '''visit your personal student email'''. This can be done via Toledo or by visiting [https://owa.student.kuleuven.be owa.student.kuleuven.be]. This should bring you to your personal KU Leuven mailbox. On the left side of the page, you should see several icons (Mail, Calendar, People). Here you will need to '''select''' '''<nowiki/>'Calendar'''' (Image 3), which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are put on Toledo by your professors, should also be shown here now). If the calendar is still completely empty, make sure they're selected within 'My Calendars' on the left of your calendar overview. If it doesn't show up in this list, check if your agenda settings in KU Loket are set correctly according to image 2 and that you are looking at time period where classes are scheduled (not a holiday period). '''<nowiki/>''' '''<nowiki/>'''[[File:Select Agenda.png|thumb|216x216px|Image 4 - Sharing your agenda]] Continuing in the top right corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a dropdown where you can select which agenda you would like to share (Image 4) (In this case we want to select UURROOSTER). Next you'll be shown a 'Sharing and permissions' window. In here simply enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'Can view all details' is selected from the dropdown menu (this should be done by default). Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email. In this email you want to click the blue box with '''<nowiki/>'Accept and view calendar''''. [[File:ICalLink.png|thumb|261x261px|Image 5 - iCal link in Outlook sharing-mail]] At the top of this window you'll find a link ending on .ics, (Image 5) this is your iCal link. You'll want to copy this so you'll be able to import the agenda into your personal calendar. Importing the iCal link to your chosen personal agenda can vary widely depending on which personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 Almost all calendar services support importing iCal. If your chosen calendar service is not listed here, you can try searching the internet on how to import iCal for your service. [[Category:Tutorials]] 9d59ef163a60e35cd6e4e3d14ce283987357de96 1789 1788 2022-11-11T20:09:38Z Johnny 51 /* Synchronizing your KU Leuven calendar */ wikitext text/x-wiki This guide will explain how your KU Leuven calendar, which you can see on Toledo, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Thunderbird, Outlook, Windows Calendar, etc.), following the steps below. = Synchronizing your KU Leuven calendar = [[File:Agenda Sync.png|thumb|235x235px|Image 1 - Where to find Agenda Sync]] Your first step will be to visit KU Loket via Toledo or by visiting [http://kuloket.be kuloket.be] . Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture in image 1. Now you will get an overview of your different agendas. Here you will need to select which one you wish to export. Next you will be presented a window with settings. The settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed further here. [[File:Agenda Synchronisation on.png|thumb|268x268px|Image 2 - Synchronisation status|alt=]] The only necessairy step here is to make sure our '''synchronisation is on'''. We can check this at the top of the page. If the synchronisation is off, simply select restart sync at the top right. It's possible you will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. It should look as shown in image 2. [[File:Agenda in Outlook.png|thumb|209x209px|Image 3 - Calendar]] The following step will be to '''visit your personal student email'''. This can be done via Toledo or by visiting [https://owa.student.kuleuven.be owa.student.kuleuven.be]. This should bring you to your personal KU Leuven mailbox. On the left side of the page, you should see several icons (Mail, Calendar, People). Here you will need to '''select''' '''<nowiki/>'Calendar'''' (Image 3), which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are put on Toledo by your professors, should also be shown here now). If the calendar is still completely empty, make sure they're selected within 'My Calendars' on the left of your calendar overview. If it doesn't show up in this list, check if your agenda settings in KU Loket are set correctly according to image 2 and that you are looking at time period where classes are scheduled (not a holiday period). '''<nowiki/>''' '''<nowiki/>'''[[File:Select Agenda.png|thumb|216x216px|Image 4 - Sharing your agenda]] Continuing in the top right corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a dropdown where you can select which agenda you would like to share (Image 4) (In this case we want to select UURROOSTER). Next you'll be shown a 'Sharing and permissions' window. In here simply enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'Can view all details' is selected from the dropdown menu (this should be done by default). Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email. In this email you want to click the blue box with '''<nowiki/>'Accept and view calendar''''. [[File:ICalLink.png|thumb|261x261px|Image 5 - iCal link in Outlook sharing-mail]] At the top of this window you'll find a link ending on .ics, (Image 5) this is your iCal link. You'll want to copy this so you'll be able to import the agenda into your personal calendar. Importing the iCal link to your chosen personal agenda can vary widely depending on which personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 Almost all calendar services support importing iCal. If your chosen calendar service is not listed here, you can try searching the internet on how to import iCal for your service. [[Category:Tutorials]] 7237442868bebc14fa139724b5813914af875c60 1790 1789 2022-11-11T20:10:04Z Johnny 51 /* Synchronizing your KU Leuven calendar */ wikitext text/x-wiki This guide will explain how your KU Leuven calendar, which you can see on Toledo, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Thunderbird, Outlook, Windows Calendar, etc.), following the steps below. = Synchronizing your KU Leuven calendar = [[File:Agenda Sync.png|thumb|235x235px|Image 1 - Where to find Agenda Sync]] Your first step will be to visit KU Loket via Toledo or by visiting [http://kuloket.be kuloket.be] . Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture in image 1. Now you will get an overview of your different agendas. Here you will need to select which one you wish to export. Next you will be presented a window with settings. The settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed further here. [[File:Agenda Synchronisation on.png|thumb|268x268px|Image 2 - Synchronisation status|alt=]] The only necessairy step here is to make sure our '''synchronisation is on'''. We can check this at the top of the page. If the synchronisation is off, simply select restart sync at the top right. It's possible you will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. It should look as shown in image 2. [[File:Agenda in Outlook.png|thumb|209x209px|Image 3 - Calendar]] The following step will be to '''visit your personal student email'''. This can be done via Toledo or by visiting [https://owa.student.kuleuven.be owa.student.kuleuven.be]. This should bring you to your personal KU Leuven mailbox. On the left side of the page, you should see several icons (Mail, Calendar, People). Here you will need to '''select''' '''<nowiki/>'Calendar'''' (Image 3), which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are put on Toledo by your professors, should also be shown here now). If the calendar is still completely empty, make sure they're selected within 'My Calendars' on the left of your calendar overview. If it doesn't show up in this list, check if your agenda settings in KU Loket are set correctly according to image 2 and that you are looking at time period where classes are scheduled (not a holiday period). '''<nowiki/>''' '''<nowiki/>'''[[File:Select Agenda.png|thumb|216x216px|Image 4 - Sharing your agenda]] Continuing in the top right corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a dropdown where you can select which agenda you would like to share (Image 4) (In this case we want to select UURROOSTER). Next you'll be shown a 'Sharing and permissions' window. In here simply enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'Can view all details' is selected from the dropdown menu (this should be done by default). Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email. In this email you want to click the blue box with '''<nowiki/>'Accept and view calendar''''. [[File:ICalLink.png|thumb|261x261px|Image 5 - iCal link in Outlook sharing-mail]] At the top of this window you'll find a link ending on .ics, (Image 5) this is your iCal link. You'll want to copy this so you'll be able to import the agenda into your personal calendar. Importing the iCal link to your chosen personal agenda can vary widely depending on which personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 Almost all calendar services support importing iCal. If your chosen calendar service is not listed here, you can try searching the internet on how to import iCal for your service. [[Category:Tutorials]] b84562a11d63c1ad9e77f882819da1f5fac98646 0 44 1791 864 2023-02-15T21:57:07Z Vincenttc 21 Outdated informatie over file permissions weggehaald wikitext text/x-wiki = Location of your files = All the files you want to provide via the web browser must reside in a directory named "www" in your homefolder. Within that folder you can organise your data in sub directories. For more information about accessing your files is available [https://docs.ulyssis.org/Accessing_your_files here]. = Accessing your website = Your webspace is accessible on following url's (with username your username): * http://username.studentenweb.org * http://username.ulyssis.be If you have a domainname like yourname.be, you can link it with our webserver. For more information on this subject, see the [https://docs.ulyssis.org/Adding_domain_names domainnames documentation]. = Troubleshooting = I keep getting an "HTTP Error 403: permission denied" when accessing my website. Check that all permissions on the files and folders relevant to your website are set properly. See [[Secure file permissions]] for more information. [[Category:Webserver]] acb0332ac7e5dc91182808bbfe3ba7244140ac96 0 103 1792 1072 2023-02-22T22:30:00Z Ziik 53 Add composer install guide wikitext text/x-wiki While most webhosting providers give you access to a few or even just one programming language and a set amount of libraries, ULYSSIS prefers to offer more flexibility. We hope to give our users the chance to experiment with different languages, libraries and tools. There are of course limits to what is realistic for us to install. More on that below. == Using a programming language, library or tool that is not installed == If the package that you would like us to install is available in the software repository of our current operating system, then that is usually not a problem. We currently use Ubuntu on all our servers, specifically, we upgrade to the latest LTS every summer vacation following the release of a new one. You can verify which version we are running by executing "cat /etc/lsb-release" on one of our shellservers. After you have verified what version we are running, you can refer to https://packages.ubuntu.com/ to check whether your package is available in that version of Ubuntu. If it is, then you can contact us by email on ulyssis@ulyssis.org which package or packages you would like to have installed, and what you will be using it for. You will most likely get a positive response. If your package is not in the repository, you will have to go for a [[Installing packages#Manual installation|Manual installation]]. == Using a newer/different version == As you can read in the section concerning the installation of new packages, we only offer the version available in the repository of the version of Ubuntu that we are running. In most cases, this means you will have to wait for a version upgrade with the next LTS release, or go for a [[Installing packages#Manual installation|Manual installation]]. However, there are some exceptions. Sometimes multiple version will be available in the repository, such as with Python 2 and 3, or Perl 5 and 6. In such cases, you can refer to the section above for instructions on how to request an installation. == Manual installation == If you want to install a piece of software that is not available in the repository or you wish to install another version, you can always install it manually onto your account. It is important to keep in mind that ULYSSIS will not support manually installed software, and that you are fully responsible for the security of this software. You are free to ask us questions, but we will most probably not help you. If you do require a manual installation of specific software, we expect you to be capable of maintaining it as well. The way you install your software differs depending on the software. You could be using tools such as pip, gem or npm to install to a directory in your home folder, you could be using a virtual environment, or you could be compiling your own binary. We suggest you look at the documentation of the software you're using very thoroughly, and make sure you are comfortable with what you are doing and aware of your responsibilities. After installing your software locally onto your account, you will probably want to add an alias in your dotfiles (for example .profile or .bashrc) to make using your manually installed version easier. In case you are using your piece of software for a web service, you will want to make sure you edit your fastcgi script or any other involved scripts to use your binary by changing the path or hardcoding the location. ===Node.js=== We do not offer Node.js by default because we can't give you the most recent release. But you can use nvm ([https://github.com/creationix/nvm Node Version Manager]) which installs the required version for you. The installation should be straightforward and a guide can be found [https://github.com/nvm-sh/nvm#installing-and-updating here]. ===Composer=== We do not provide a global installation of Composer to our users because of different version requirements set by different applications which are not compatible with our setup. If you want to run Composer, you can do a manual install of it. First off, access our shell servers over SSH. You can refer to [[Accessing shell servers over SSH|this page]] if you're unsure of how to do so. Once you're logged in, follow these steps to install Composer to the current directory: # Download the installer script: type <code>php -r "copy('https://getcomposer.org/installer', 'composer-setup.php');"</code> in the command line and press Enter. # Run the installer script: type <code>php composer-setup.php</code> and press Enter. # Composer is now installed. You can remove the installer by typing <code>rm composer-setup.php</code> and pressing Enter. You can now run Composer by typing <code>php composer.phar</code> in the directory where you installed it and pressing Enter. [[Category:Shell]] e76605a71c6cb2b7ea5724d97652362cb8c51b6d 1793 1792 2023-02-23T12:14:03Z Ziik 53 Rework Composer wikitext text/x-wiki While most webhosting providers give you access to a few or even just one programming language and a set amount of libraries, ULYSSIS prefers to offer more flexibility. We hope to give our users the chance to experiment with different languages, libraries and tools. There are of course limits to what is realistic for us to install. More on that below. == Using a programming language, library or tool that is not installed == If the package that you would like us to install is available in the software repository of our current operating system, then that is usually not a problem. We currently use Ubuntu on all our servers, specifically, we upgrade to the latest LTS every summer vacation following the release of a new one. You can verify which version we are running by executing "cat /etc/lsb-release" on one of our shellservers. After you have verified what version we are running, you can refer to https://packages.ubuntu.com/ to check whether your package is available in that version of Ubuntu. If it is, then you can contact us by email on ulyssis@ulyssis.org which package or packages you would like to have installed, and what you will be using it for. You will most likely get a positive response. If your package is not in the repository, you will have to go for a [[Installing packages#Manual installation|Manual installation]]. == Using a newer/different version == As you can read in the section concerning the installation of new packages, we only offer the version available in the repository of the version of Ubuntu that we are running. In most cases, this means you will have to wait for a version upgrade with the next LTS release, or go for a [[Installing packages#Manual installation|Manual installation]]. However, there are some exceptions. Sometimes multiple version will be available in the repository, such as with Python 2 and 3, or Perl 5 and 6. In such cases, you can refer to the section above for instructions on how to request an installation. == Manual installation == If you want to install a piece of software that is not available in the repository or you wish to install another version, you can always install it manually onto your account. It is important to keep in mind that ULYSSIS will not support manually installed software, and that you are fully responsible for the security of this software. You are free to ask us questions, but we will most probably not help you. If you do require a manual installation of specific software, we expect you to be capable of maintaining it as well. The way you install your software differs depending on the software. You could be using tools such as pip, gem or npm to install to a directory in your home folder, you could be using a virtual environment, or you could be compiling your own binary. We suggest you look at the documentation of the software you're using very thoroughly, and make sure you are comfortable with what you are doing and aware of your responsibilities. After installing your software locally onto your account, you will probably want to add an alias in your dotfiles (for example .profile or .bashrc) to make using your manually installed version easier. You can look at the second step in [[Installing packages#Composer]] for an example on how to make a program accessible everywhere. In case you are using your piece of software for a web service, you will want to make sure you edit your fastcgi script or any other involved scripts to use your binary by changing the path or hardcoding the location. ===Node.js=== We do not offer Node.js by default because we can't give you the most recent release. But you can use nvm ([https://github.com/creationix/nvm Node Version Manager]) which installs the required version for you. The installation should be straightforward and a guide can be found [https://github.com/nvm-sh/nvm#installing-and-updating here]. ===Composer=== We do not provide a global installation of Composer to our users because of different version requirements set by different applications which are not compatible with our setup. If you want to run Composer, you can do a manual install of it. First, log in on SSH and then follow these steps to install Composer: # Follow [https://getcomposer.org/download/ the manual steps] from "Command-line installation" to "php.ini" (the white code block). # Type: <code>mkdir -p ~/.local/bin && mv composer.phar ~/.local/bin && echo 'export PATH=$PATH:~/.local/bin' >> ~/.bashrc</code> and press Enter. You can now run <code>composer.phar</code> from anywhere. [[Category:Shell]] 972f332c9ff03b60546d680aba92bc260571fc58 0 80 1794 1729 2023-02-24T05:09:04Z Bert 8 wikitext text/x-wiki {{notice|To use a forwarder as an alias, access to the KU Leuven SMTP server is required. Since 24 February 2023 not all students have access to this server by default any more. If you are unable to send emails after following our documentation, then you may want to register on https://ulyssis.org/smtp/ for SMTP access.}} If you have your own domain, it's very easy to use [[Forwarders]] to forward email from addresses under your own domain to other email addresses at external providers or your ULYSSIS mailbox. While you can always reply with the address of that external provider or the @ulyssis.org address of your mailbox, it's often preferred to also use the address of your own domain when replying to messages or starting conversations. In that case you will want to configure an alias for your forwarder. While you are free to use whatever provider, email application or webmail application you prefer, we have step-by-step manuals available for some specific case. You can find them listed here: * [[Add an alias in ULYSSIS webmail]] * [[Add an alias in Thunderbird]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] [[Category:Mail]] eb3ec8d486e32a310076dbc94175eead6dfd27a0 1795 1794 2023-02-24T05:09:32Z Bert 8 wikitext text/x-wiki {{notice|To use a forwarder as an alias, access to the KU Leuven SMTP server is required|Since 24 February 2023 not all students have access to this server by default any more. If you are unable to send emails after following our documentation, then you may want to register on https://ulyssis.org/smtp/ for SMTP access.}} If you have your own domain, it's very easy to use [[Forwarders]] to forward email from addresses under your own domain to other email addresses at external providers or your ULYSSIS mailbox. While you can always reply with the address of that external provider or the @ulyssis.org address of your mailbox, it's often preferred to also use the address of your own domain when replying to messages or starting conversations. In that case you will want to configure an alias for your forwarder. While you are free to use whatever provider, email application or webmail application you prefer, we have step-by-step manuals available for some specific case. You can find them listed here: * [[Add an alias in ULYSSIS webmail]] * [[Add an alias in Thunderbird]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] [[Category:Mail]] ceb2d0c7e034ff40af4838000e051796306e3b67 1799 1795 2023-02-24T11:04:38Z Bert 8 wikitext text/x-wiki {{notice|To use a forwarder as an alias, access to the KU Leuven SMTP server is required|Since 24 February 2023, not all students have access to smtps.kuleuven.be by default any more. If you are unable to send emails after following the instructions outlined in documentation, then you may have to register on https://ulyssis.org/smtp/ for SMTP access.}} If you have your own domain, it's very easy to use [[Forwarders]] to forward email from addresses under your own domain to other email addresses at external providers or your ULYSSIS mailbox. While you can always reply with the address of that external provider or the @ulyssis.org address of your mailbox, it's often preferred to also use the address of your own domain when replying to messages or starting conversations. In that case you will want to configure an alias for your forwarder. While you are free to use whatever provider, email application or webmail application you prefer, we have step-by-step manuals available for some specific case. You can find them listed here: * [[Add an alias in ULYSSIS webmail]] * [[Add an alias in Thunderbird]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] [[Category:Mail]] 7f8023375e4980c773d35eaa0ea706dd82ac2d5f 1800 1799 2023-02-24T11:08:44Z Bert 8 wikitext text/x-wiki {{notice|To use a forwarder as an alias, access to the KU Leuven SMTP server is required|Since 24 February 2023, not all students have access to smtps.kuleuven.be by default anymore. If you are unable to send emails after following the instructions outlined in our documentation, then you may have to register on https://ulyssis.org/smtp/ for SMTP access.}} If you have your own domain, it's very easy to use [[Forwarders]] to forward email from addresses under your own domain to other email addresses at external providers or your ULYSSIS mailbox. While you can always reply with the address of that external provider or the @ulyssis.org address of your mailbox, it's often preferred to also use the address of your own domain when replying to messages or starting conversations. In that case you will want to configure an alias for your forwarder. While you are free to use whatever provider, email application or webmail application you prefer, we have step-by-step manuals available for some specific case. You can find them listed here: * [[Add an alias in ULYSSIS webmail]] * [[Add an alias in Thunderbird]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] [[Category:Mail]] d0fd6ca3ac8af33a317a89b77fdaee1fc97320df 1801 1800 2023-02-24T11:09:43Z Bert 8 wikitext text/x-wiki {{notice|To use a forwarder as an alias, access to the KU Leuven SMTP server is required|Since 24 February 2023, not all students have access to smtps.kuleuven.be by default anymore. If you are unable to send emails after following the instructions outlined in our documentation, then you may have to register on https://ulyssis.org/smtp/ to (re)gain SMTP access.}} If you have your own domain, it's very easy to use [[Forwarders]] to forward email from addresses under your own domain to other email addresses at external providers or your ULYSSIS mailbox. While you can always reply with the address of that external provider or the @ulyssis.org address of your mailbox, it's often preferred to also use the address of your own domain when replying to messages or starting conversations. In that case you will want to configure an alias for your forwarder. While you are free to use whatever provider, email application or webmail application you prefer, we have step-by-step manuals available for some specific case. You can find them listed here: * [[Add an alias in ULYSSIS webmail]] * [[Add an alias in Thunderbird]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] [[Category:Mail]] 8192472f4a82dfae7671be7df87daae27996b492 0 34 1796 1726 2023-02-24T05:09:45Z Bert 8 wikitext text/x-wiki {{notice|To use a forwarder as an alias, access to the KU Leuven SMTP server is required|Since 24 February 2023 not all students have access to this server by default any more. If you are unable to send emails after following our documentation, then you may want to register on https://ulyssis.org/smtp/ for SMTP access.}} You may want to send e-mail from Gmail using your @ulyssis.org address, or another domain name that you use for your account. Gmail allows you to do this, but asks for SMTP info. We don't provide SMTP on our own mail server, but you can use the SMTP servers of the KU Leuven. Because you should only be able to send mails from an email address you actually own, make sure that you configured receiving mails before starting this process. Gmail will send a confirmation mail to the provided email address to confirm that you own it. # In Gmail, click on the gear icon at the top right. # Click '''See all settings''' (Dutch: '''Alle instellingen bekijken'''). # Go to the tab '''Accounts and Import''' (Dutch: '''Accounts en import'''). # Under '''Send mail as:''' (Dutch: '''Mail verzenden als:'''), click on: '''Add another email address''' (Dutch: '''Nog een e-mailadres toevoegen'''). # Fill in the email address you want to send from, and check '''Treat as an alias.''' (Dutch: '''Beschouwen als alias.''') More info: https://support.google.com/a/answer/1710338 # Optionally: Enter a '''Name''', the recipient will see this name instead of or next to your email address. # Click on '''Next step''' (Dutch: '''Volgende stap'''). # Fill in the [https://admin.kuleuven.be/icts/english/services/email/imap-configuratie-en KU Leuven SMTP information] ([https://admin.kuleuven.be/icts/services/email/imap-configuratie Dutch]): #*'''SMTP server''': '''smtps.kuleuven.be''' #* '''Port''': '''465''' #* '''Username''': your KU Leuven intranet userid r or u-number e.g. r0123456 #* '''Password''': your central KU Leuven password #* '''Secured connection using''': '''SSL''' # Click on the '''Add Account''' (Dutch: '''Account toevoegen''') button. # Confirm your request using the link or code, you just received via an email on the address you provided. You can now send emails in Gmail from this address: # In Gmail, click '''Compose''' (Dutch: '''Opstellen'''). # Click on the email address next to '''From''' (Dutch: '''Van'''). # Select the email address you want to send from. [[Category:Mail]] 213e520b66294a013c49065f0bbdc402fd95ab2b 0 72 1797 1734 2023-02-24T05:09:51Z Bert 8 wikitext text/x-wiki {{notice|Adding an alias to Hotmail/Outlook is not advised|Hotmail/Outlook does not use a relevant SMTP server, for example the one of the KU Leuven, to send emails as an alias. This may cause recipients to automatically reject your email or mark it as spam. You can circumvent this issue by using Thunderbird or another email provider. Please refer to [[Using a forwarder as an alias]] for some potential alternatives.}} {{notice|To use a forwarder as an alias, access to the KU Leuven SMTP server is required|Since 24 February 2023 not all students have access to this server by default any more. If you are unable to send emails after following our documentation, then you may want to register on https://ulyssis.org/smtp/ for SMTP access.}} You may want to send e-mail from Outlook.com using your @ulyssis.org address, or another domain name that you use for your account. Outlook.com allows you to do this by configuring a few settings. Because you should only be able to send mails from an e-mail address you actually own, make sure that you configured receiving mails before starting this process. Outlook.com will send a confirmation mail to the provided e-mail address to confirm that you own it. # In Outlook.com, click on your profile image. # Click '''My Microsoft account''' (Dutch: '''Mijn Microsoft-account'''). # Go to the tab '''Your info''' (Dutch: '''Je gegevens'''). # Under '''Account info''' (Dutch: '''Rekeninggegevens''') click on: '''Sign-in preferences''' (Dutch: '''Aanmeldingsvoorkeuren'''). # You will have to log in again to proceed. Click '''Add email''' (Dutch: '''E-mailadres toevoegen'''). # Select '''Add an existing email address as a Microsoft account alias''' (Dutch: '''Een bestaand e-mailadres als een Microsoft-accountalias toevoegen''') and fill in the email address you want to send from. # Click '''Add alias''' (Dutch: '''Alias toevoegen'''). # Confirm your request using the link or code, you just received via an email on the address you provided. You can now send emails in Outlook.com from this address: # In Outlook.com, click '''New message''' (Dutch: '''Nieuw bericht'''). # Click on '''From''' (Dutch: '''Van''') and select the email address. [[Category:Mail]] 360bda1636f1e3c30cd4a4d9d91bee63cc06a771 0 77 1798 1725 2023-02-24T05:09:58Z Bert 8 wikitext text/x-wiki {{notice|To use a forwarder as an alias, access to the KU Leuven SMTP server is required|Since 24 February 2023 not all students have access to this server by default any more. If you are unable to send emails after following our documentation, then you may want to register on https://ulyssis.org/smtp/ for SMTP access.}} You may want to send e-mail from Thunderbird using your @ulyssis.org address, or another domain name that you use for your account. Thunderbird allows you to do this, but to configure this properly, you should not use your provider's SMTP server. They will add an extra header stating the original e-mail address the e-mail is sent from. Some e-mail clients show this information, which might be unwanted. The KU Leuven also provides an SMTP server which you can use as a student. It accepts e-mail originating from any e-mail adress, and can therefore be used for this purpose. It should be noted that this is an '''authenticated''' server, so any potential abuse can be tracked back to you. You should '''not''' use this for any malicious purpose. == Adding the KU Leuven SMTP server in Thunderbird == If you already have set up your KU Leuven e-mail in Thunderbird, you can skip this step and proceed to [[#Configure an identity for your e-mail account|Configure an identity for your e-mail account]] below. Go to your '''Account Settings''' (Edit > Account Settings or Tools > Account Settings, depending on your operating system). At the bottom of the left sidebar, you will find an entry named '''Outgoing Server (SMTP)'''. Click this to access your SMTP settings. In your SMTP settings, you should see a list of existing SMTP servers. We want to add a new entry, so click the '''Add...''' button. In the screen that pops up, fill in the settings of the KU Leuven SMTP server, using the example screenshot below based on the [https://admin.kuleuven.be/icts/english/services/email/imap-configuratie-en official ICTS documentation]. Replace the displayed user name with your own KULid (m/r/s/u number). You will have to fill in the corresponding password on first use. [[File:Thunderbird-SMTPS.png]] == Configure an identity for your e-mail account == Back in the '''Account Settings''' screen, click on your e-mail address (not on any of its children). In the screen that opens, there will be a button '''Manage Identities...''' at the bottom. Click it. In the new screen, there will be one existing identity already: the default identity corresponding with your normal e-mail address. We want to add a new identity, so click the '''Add...''' button. In the screen that pops up, fill in the name and e-mail address you wish to use. At the bottom, make sure you choose the SMTP server of your KULid. This is shown in the image below. [[File:Thunderbird-Identity.png]] If you're adding an identity for a group alias, you may also want to automatically send a copy of any replies or emails you're sending to the alias itself to make sure all others are aware of it. To do that, enable the BCC checkbox under the '''Copies & Folders''' tab. It should automatically contain the alias. == Sending your first e-mail == When you compose a new e-mail, you can change the sender in the "From" field to the identity you just configured. If everything was installed correctly, Thunderbird will show you a pop-up to enter your KU Leuven password when you try to send the e-mail. In this pop-up, you can choose to save this password for later use. [[Category:Mail]] 8502d77bbc37f7c9a2168784407963b232bbc486 10 262 1802 2023-02-24T11:12:01Z Bert 8 Created page with "{{notice|To use a forwarder as an alias, access to the KU Leuven SMTP server is required|Since 24 February 2023, not all students have access to smtps.kuleuven.be by default a..." wikitext text/x-wiki {{notice|To use a forwarder as an alias, access to the KU Leuven SMTP server is required|Since 24 February 2023, not all students have access to smtps.kuleuven.be by default anymore. If you are unable to send emails after following the instructions outlined in our documentation, then you may have to register on https://ulyssis.org/smtp/ to (re)gain SMTP access.}} ef767c06b034a0f775a9f18d74cbb5fb3abf1e60 0 80 1803 1801 2023-02-24T11:12:18Z Bert 8 wikitext text/x-wiki {{SMTPnotice}} If you have your own domain, it's very easy to use [[Forwarders]] to forward email from addresses under your own domain to other email addresses at external providers or your ULYSSIS mailbox. While you can always reply with the address of that external provider or the @ulyssis.org address of your mailbox, it's often preferred to also use the address of your own domain when replying to messages or starting conversations. In that case you will want to configure an alias for your forwarder. While you are free to use whatever provider, email application or webmail application you prefer, we have step-by-step manuals available for some specific case. You can find them listed here: * [[Add an alias in ULYSSIS webmail]] * [[Add an alias in Thunderbird]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] [[Category:Mail]] 2f48385d880c1ec89e6a4241184fd6cd02bcf789 1804 1803 2023-02-24T11:12:44Z Bert 8 wikitext text/x-wiki {{SMTPnotice}} If you have your own domain, it's very easy to use [[Forwarders]] to forward email from addresses under your own domain to other email addresses at external providers or your ULYSSIS mailbox. While you can always reply with the address of that external provider or the @ulyssis.org address of your mailbox, it's often preferred to also use the address of your own domain when replying to messages or starting conversations. In that case you will want to configure an alias for your forwarder. While you are free to use whatever provider, email application or webmail application you prefer, we have step-by-step manuals available for some specific case. You can find them listed here: * [[Add an alias in ULYSSIS webmail]] * [[Add an alias in Thunderbird]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] [[Category:Mail]] 06868b2bb7eefccade2768b92cfd0637f61b110e 1811 1804 2023-02-24T11:30:50Z Bert 8 wikitext text/x-wiki {{SMTPnotice|a forwarder as an alias}} If you have your own domain, it's very easy to use [[Forwarders]] to forward email from addresses under your own domain to other email addresses at external providers or your ULYSSIS mailbox. While you can always reply with the address of that external provider or the @ulyssis.org address of your mailbox, it's often preferred to also use the address of your own domain when replying to messages or starting conversations. In that case you will want to configure an alias for your forwarder. While you are free to use whatever provider, email application or webmail application you prefer, we have step-by-step manuals available for some specific case. You can find them listed here: * [[Add an alias in ULYSSIS webmail]] * [[Add an alias in Thunderbird]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] [[Category:Mail]] 3e76d5b62cce5b0d5e765094713946ba157f8074 0 77 1805 1798 2023-02-24T11:12:49Z Bert 8 wikitext text/x-wiki {{SMTPnotice}} You may want to send e-mail from Thunderbird using your @ulyssis.org address, or another domain name that you use for your account. Thunderbird allows you to do this, but to configure this properly, you should not use your provider's SMTP server. They will add an extra header stating the original e-mail address the e-mail is sent from. Some e-mail clients show this information, which might be unwanted. The KU Leuven also provides an SMTP server which you can use as a student. It accepts e-mail originating from any e-mail adress, and can therefore be used for this purpose. It should be noted that this is an '''authenticated''' server, so any potential abuse can be tracked back to you. You should '''not''' use this for any malicious purpose. == Adding the KU Leuven SMTP server in Thunderbird == If you already have set up your KU Leuven e-mail in Thunderbird, you can skip this step and proceed to [[#Configure an identity for your e-mail account|Configure an identity for your e-mail account]] below. Go to your '''Account Settings''' (Edit > Account Settings or Tools > Account Settings, depending on your operating system). At the bottom of the left sidebar, you will find an entry named '''Outgoing Server (SMTP)'''. Click this to access your SMTP settings. In your SMTP settings, you should see a list of existing SMTP servers. We want to add a new entry, so click the '''Add...''' button. In the screen that pops up, fill in the settings of the KU Leuven SMTP server, using the example screenshot below based on the [https://admin.kuleuven.be/icts/english/services/email/imap-configuratie-en official ICTS documentation]. Replace the displayed user name with your own KULid (m/r/s/u number). You will have to fill in the corresponding password on first use. [[File:Thunderbird-SMTPS.png]] == Configure an identity for your e-mail account == Back in the '''Account Settings''' screen, click on your e-mail address (not on any of its children). In the screen that opens, there will be a button '''Manage Identities...''' at the bottom. Click it. In the new screen, there will be one existing identity already: the default identity corresponding with your normal e-mail address. We want to add a new identity, so click the '''Add...''' button. In the screen that pops up, fill in the name and e-mail address you wish to use. At the bottom, make sure you choose the SMTP server of your KULid. This is shown in the image below. [[File:Thunderbird-Identity.png]] If you're adding an identity for a group alias, you may also want to automatically send a copy of any replies or emails you're sending to the alias itself to make sure all others are aware of it. To do that, enable the BCC checkbox under the '''Copies & Folders''' tab. It should automatically contain the alias. == Sending your first e-mail == When you compose a new e-mail, you can change the sender in the "From" field to the identity you just configured. If everything was installed correctly, Thunderbird will show you a pop-up to enter your KU Leuven password when you try to send the e-mail. In this pop-up, you can choose to save this password for later use. [[Category:Mail]] 5d85a778af46d0d7520c94267a927b8b0bd61ad9 1814 1805 2023-02-24T11:31:12Z Bert 8 wikitext text/x-wiki {{SMTPnotice|a forwarder as an alias}} You may want to send e-mail from Thunderbird using your @ulyssis.org address, or another domain name that you use for your account. Thunderbird allows you to do this, but to configure this properly, you should not use your provider's SMTP server. They will add an extra header stating the original e-mail address the e-mail is sent from. Some e-mail clients show this information, which might be unwanted. The KU Leuven also provides an SMTP server which you can use as a student. It accepts e-mail originating from any e-mail adress, and can therefore be used for this purpose. It should be noted that this is an '''authenticated''' server, so any potential abuse can be tracked back to you. You should '''not''' use this for any malicious purpose. == Adding the KU Leuven SMTP server in Thunderbird == If you already have set up your KU Leuven e-mail in Thunderbird, you can skip this step and proceed to [[#Configure an identity for your e-mail account|Configure an identity for your e-mail account]] below. Go to your '''Account Settings''' (Edit > Account Settings or Tools > Account Settings, depending on your operating system). At the bottom of the left sidebar, you will find an entry named '''Outgoing Server (SMTP)'''. Click this to access your SMTP settings. In your SMTP settings, you should see a list of existing SMTP servers. We want to add a new entry, so click the '''Add...''' button. In the screen that pops up, fill in the settings of the KU Leuven SMTP server, using the example screenshot below based on the [https://admin.kuleuven.be/icts/english/services/email/imap-configuratie-en official ICTS documentation]. Replace the displayed user name with your own KULid (m/r/s/u number). You will have to fill in the corresponding password on first use. [[File:Thunderbird-SMTPS.png]] == Configure an identity for your e-mail account == Back in the '''Account Settings''' screen, click on your e-mail address (not on any of its children). In the screen that opens, there will be a button '''Manage Identities...''' at the bottom. Click it. In the new screen, there will be one existing identity already: the default identity corresponding with your normal e-mail address. We want to add a new identity, so click the '''Add...''' button. In the screen that pops up, fill in the name and e-mail address you wish to use. At the bottom, make sure you choose the SMTP server of your KULid. This is shown in the image below. [[File:Thunderbird-Identity.png]] If you're adding an identity for a group alias, you may also want to automatically send a copy of any replies or emails you're sending to the alias itself to make sure all others are aware of it. To do that, enable the BCC checkbox under the '''Copies & Folders''' tab. It should automatically contain the alias. == Sending your first e-mail == When you compose a new e-mail, you can change the sender in the "From" field to the identity you just configured. If everything was installed correctly, Thunderbird will show you a pop-up to enter your KU Leuven password when you try to send the e-mail. In this pop-up, you can choose to save this password for later use. [[Category:Mail]] fdd7b598344936c19853c5da63097f31afb80ccc 0 34 1806 1796 2023-02-24T11:12:57Z Bert 8 wikitext text/x-wiki {{SMTPnotice}} You may want to send e-mail from Gmail using your @ulyssis.org address, or another domain name that you use for your account. Gmail allows you to do this, but asks for SMTP info. We don't provide SMTP on our own mail server, but you can use the SMTP servers of the KU Leuven. Because you should only be able to send mails from an email address you actually own, make sure that you configured receiving mails before starting this process. Gmail will send a confirmation mail to the provided email address to confirm that you own it. # In Gmail, click on the gear icon at the top right. # Click '''See all settings''' (Dutch: '''Alle instellingen bekijken'''). # Go to the tab '''Accounts and Import''' (Dutch: '''Accounts en import'''). # Under '''Send mail as:''' (Dutch: '''Mail verzenden als:'''), click on: '''Add another email address''' (Dutch: '''Nog een e-mailadres toevoegen'''). # Fill in the email address you want to send from, and check '''Treat as an alias.''' (Dutch: '''Beschouwen als alias.''') More info: https://support.google.com/a/answer/1710338 # Optionally: Enter a '''Name''', the recipient will see this name instead of or next to your email address. # Click on '''Next step''' (Dutch: '''Volgende stap'''). # Fill in the [https://admin.kuleuven.be/icts/english/services/email/imap-configuratie-en KU Leuven SMTP information] ([https://admin.kuleuven.be/icts/services/email/imap-configuratie Dutch]): #*'''SMTP server''': '''smtps.kuleuven.be''' #* '''Port''': '''465''' #* '''Username''': your KU Leuven intranet userid r or u-number e.g. r0123456 #* '''Password''': your central KU Leuven password #* '''Secured connection using''': '''SSL''' # Click on the '''Add Account''' (Dutch: '''Account toevoegen''') button. # Confirm your request using the link or code, you just received via an email on the address you provided. You can now send emails in Gmail from this address: # In Gmail, click '''Compose''' (Dutch: '''Opstellen'''). # Click on the email address next to '''From''' (Dutch: '''Van'''). # Select the email address you want to send from. [[Category:Mail]] 633daab94aa5eae371818f9ff21f2056e888cf8d 1812 1806 2023-02-24T11:31:02Z Bert 8 wikitext text/x-wiki {{SMTPnotice|a forwarder as an alias}} You may want to send e-mail from Gmail using your @ulyssis.org address, or another domain name that you use for your account. Gmail allows you to do this, but asks for SMTP info. We don't provide SMTP on our own mail server, but you can use the SMTP servers of the KU Leuven. Because you should only be able to send mails from an email address you actually own, make sure that you configured receiving mails before starting this process. Gmail will send a confirmation mail to the provided email address to confirm that you own it. # In Gmail, click on the gear icon at the top right. # Click '''See all settings''' (Dutch: '''Alle instellingen bekijken'''). # Go to the tab '''Accounts and Import''' (Dutch: '''Accounts en import'''). # Under '''Send mail as:''' (Dutch: '''Mail verzenden als:'''), click on: '''Add another email address''' (Dutch: '''Nog een e-mailadres toevoegen'''). # Fill in the email address you want to send from, and check '''Treat as an alias.''' (Dutch: '''Beschouwen als alias.''') More info: https://support.google.com/a/answer/1710338 # Optionally: Enter a '''Name''', the recipient will see this name instead of or next to your email address. # Click on '''Next step''' (Dutch: '''Volgende stap'''). # Fill in the [https://admin.kuleuven.be/icts/english/services/email/imap-configuratie-en KU Leuven SMTP information] ([https://admin.kuleuven.be/icts/services/email/imap-configuratie Dutch]): #*'''SMTP server''': '''smtps.kuleuven.be''' #* '''Port''': '''465''' #* '''Username''': your KU Leuven intranet userid r or u-number e.g. r0123456 #* '''Password''': your central KU Leuven password #* '''Secured connection using''': '''SSL''' # Click on the '''Add Account''' (Dutch: '''Account toevoegen''') button. # Confirm your request using the link or code, you just received via an email on the address you provided. You can now send emails in Gmail from this address: # In Gmail, click '''Compose''' (Dutch: '''Opstellen'''). # Click on the email address next to '''From''' (Dutch: '''Van'''). # Select the email address you want to send from. [[Category:Mail]] dcb5d3f6a83586e1a904805789dc08526d483c07 0 72 1807 1797 2023-02-24T11:13:02Z Bert 8 wikitext text/x-wiki {{notice|Adding an alias to Hotmail/Outlook is not advised|Hotmail/Outlook does not use a relevant SMTP server, for example the one of the KU Leuven, to send emails as an alias. This may cause recipients to automatically reject your email or mark it as spam. You can circumvent this issue by using Thunderbird or another email provider. Please refer to [[Using a forwarder as an alias]] for some potential alternatives.}} {{SMTPnotice}} You may want to send e-mail from Outlook.com using your @ulyssis.org address, or another domain name that you use for your account. Outlook.com allows you to do this by configuring a few settings. Because you should only be able to send mails from an e-mail address you actually own, make sure that you configured receiving mails before starting this process. Outlook.com will send a confirmation mail to the provided e-mail address to confirm that you own it. # In Outlook.com, click on your profile image. # Click '''My Microsoft account''' (Dutch: '''Mijn Microsoft-account'''). # Go to the tab '''Your info''' (Dutch: '''Je gegevens'''). # Under '''Account info''' (Dutch: '''Rekeninggegevens''') click on: '''Sign-in preferences''' (Dutch: '''Aanmeldingsvoorkeuren'''). # You will have to log in again to proceed. Click '''Add email''' (Dutch: '''E-mailadres toevoegen'''). # Select '''Add an existing email address as a Microsoft account alias''' (Dutch: '''Een bestaand e-mailadres als een Microsoft-accountalias toevoegen''') and fill in the email address you want to send from. # Click '''Add alias''' (Dutch: '''Alias toevoegen'''). # Confirm your request using the link or code, you just received via an email on the address you provided. You can now send emails in Outlook.com from this address: # In Outlook.com, click '''New message''' (Dutch: '''Nieuw bericht'''). # Click on '''From''' (Dutch: '''Van''') and select the email address. [[Category:Mail]] a7710550473b66b425a002156926bc357162e014 1813 1807 2023-02-24T11:31:07Z Bert 8 wikitext text/x-wiki {{notice|Adding an alias to Hotmail/Outlook is not advised|Hotmail/Outlook does not use a relevant SMTP server, for example the one of the KU Leuven, to send emails as an alias. This may cause recipients to automatically reject your email or mark it as spam. You can circumvent this issue by using Thunderbird or another email provider. Please refer to [[Using a forwarder as an alias]] for some potential alternatives.}} {{SMTPnotice|a forwarder as an alias}} You may want to send e-mail from Outlook.com using your @ulyssis.org address, or another domain name that you use for your account. Outlook.com allows you to do this by configuring a few settings. Because you should only be able to send mails from an e-mail address you actually own, make sure that you configured receiving mails before starting this process. Outlook.com will send a confirmation mail to the provided e-mail address to confirm that you own it. # In Outlook.com, click on your profile image. # Click '''My Microsoft account''' (Dutch: '''Mijn Microsoft-account'''). # Go to the tab '''Your info''' (Dutch: '''Je gegevens'''). # Under '''Account info''' (Dutch: '''Rekeninggegevens''') click on: '''Sign-in preferences''' (Dutch: '''Aanmeldingsvoorkeuren'''). # You will have to log in again to proceed. Click '''Add email''' (Dutch: '''E-mailadres toevoegen'''). # Select '''Add an existing email address as a Microsoft account alias''' (Dutch: '''Een bestaand e-mailadres als een Microsoft-accountalias toevoegen''') and fill in the email address you want to send from. # Click '''Add alias''' (Dutch: '''Alias toevoegen'''). # Confirm your request using the link or code, you just received via an email on the address you provided. You can now send emails in Outlook.com from this address: # In Outlook.com, click '''New message''' (Dutch: '''Nieuw bericht'''). # Click on '''From''' (Dutch: '''Van''') and select the email address. [[Category:Mail]] 8875e6b8c8101d739c18ab152cd4de882ef4a84e 1820 1813 2023-05-10T12:39:37Z Milanmeu 47 wikitext text/x-wiki {{notice|Adding an alias to Hotmail/Outlook is not advised|Hotmail/Outlook does not use a relevant SMTP server, for example the one of the KU Leuven, to send emails as an alias. This may cause recipients to automatically reject your email or mark it as spam. You can circumvent this issue by using Thunderbird or another email provider. Please refer to [[Using a forwarder as an alias]] for some potential alternatives.}} You may want to send e-mail from Outlook.com using your @ulyssis.org address, or another domain name that you use for your account. Outlook.com allows you to do this by configuring a few settings. Because you should only be able to send mails from an e-mail address you actually own, make sure that you configured receiving mails before starting this process. Outlook.com will send a confirmation mail to the provided e-mail address to confirm that you own it. # In Outlook.com, click on your profile image. # Click '''My Microsoft account''' (Dutch: '''Mijn Microsoft-account'''). # Go to the tab '''Your info''' (Dutch: '''Je gegevens'''). # Under '''Account info''' (Dutch: '''Rekeninggegevens''') click on: '''Sign-in preferences''' (Dutch: '''Aanmeldingsvoorkeuren'''). # You will have to log in again to proceed. Click '''Add email''' (Dutch: '''E-mailadres toevoegen'''). # Select '''Add an existing email address as a Microsoft account alias''' (Dutch: '''Een bestaand e-mailadres als een Microsoft-accountalias toevoegen''') and fill in the email address you want to send from. # Click '''Add alias''' (Dutch: '''Alias toevoegen'''). # Confirm your request using the link or code, you just received via an email on the address you provided. You can now send emails in Outlook.com from this address: # In Outlook.com, click '''New message''' (Dutch: '''Nieuw bericht'''). # Click on '''From''' (Dutch: '''Van''') and select the email address. [[Category:Mail]] 5fb3d44be731c2f488b1341d2a5655dd3d0c94e8 1821 1820 2023-05-10T12:39:58Z Milanmeu 47 wikitext text/x-wiki {{notice|Adding an alias to Hotmail/Outlook is not advised|Hotmail/Outlook does not use a relevant SMTP server, for example the one of the KU Leuven, to send emails as an alias. This may cause recipients to automatically reject your email or mark it as spam. You can circumvent this issue by using Thunderbird or another email provider. Please refer to [[Using a forwarder as an alias]] for some potential alternatives.}} You may want to send e-mail from Outlook.com using your @ulyssis.org address, or another domain name that you use for your account. Outlook.com allows you to do this by configuring a few settings. Because you should only be able to send mails from an e-mail address you actually own, make sure that you configured receiving mails before starting this process. Outlook.com will send a confirmation mail to the provided e-mail address to confirm that you own it. # In Outlook.com, click on your profile image. # Click '''My Microsoft account''' (Dutch: '''Mijn Microsoft-account'''). # Go to the tab '''Your info''' (Dutch: '''Je gegevens'''). # Under '''Account info''' (Dutch: '''Rekeninggegevens''') click on: '''Sign-in preferences''' (Dutch: '''Aanmeldingsvoorkeuren'''). # You will have to log in again to proceed. Click '''Add email''' (Dutch: '''E-mailadres toevoegen'''). # Select '''Add an existing email address as a Microsoft account alias''' (Dutch: '''Een bestaand e-mailadres als een Microsoft-accountalias toevoegen''') and fill in the email address you want to send from. # Click '''Add alias''' (Dutch: '''Alias toevoegen'''). # Confirm your request using the link or code, you just received via an email on the address you provided. You can now send emails in Outlook.com from this address: # In Outlook.com, click '''New message''' (Dutch: '''Nieuw bericht'''). # Click on '''From''' (Dutch: '''Van''') and select the email address. [[Category:Mail]] b4547f75d1556afc97ffe7055fb3006dd9eab28b 0 19 1808 1245 2023-02-24T11:13:22Z Bert 8 wikitext text/x-wiki {{SMTPnotice}} Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mailbox regularly, because all important information will be sent to this address. You can check your e-mail using webmail or an email client of your own. It is also possible to configure your email address in UCC to automatically [[Forwarders|forward]] all correspondence to another address. ==Webmail== You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to login. ==POP and IMAP access== You can access your ulyssis mail with POP or IMAP. The configuration parameters are: * '''server''': <code>mail.ulyssis.org</code> * '''port''': 993 * '''username''': ''your ULYSSIS username'' * '''password''': ''your ULYSSIS password'' * '''security''': SSL ==SMTP== ULYSSIS doesn't offer SMTP. Instead, you can use KULeuven's SMTP server: * '''server''': <code>smtps.kuleuven.be</code> * '''port''': 443 * '''username''': ''your student id'' * '''password''': ''your KULeuven password'' * '''security''': SSL == Advanced == Your emails are stored within your account under ~/Maildir. These files can of course be read with a command line email client such as alpine or mutt. We support sendmail style local delivery using .forward. More information is available in the official documentation of [https://www.sendmail.org/~ca/email/doc8.9/op-sh-2.html#sh-2.8 Sendmail] and [http://www.postfix.org/local.8.html Postfix]. While it's possible to use .forward to simply forward email to other addresses, we recommend only using it when the same feature is not available through our control panel [https://ucc.ulyssis.org UCC]. Specifically, .forward can be used to pass emails to other applications. In the past, a popular application to pass email through was procmail. However, procmail has not seen development for about 2 decades, and its developer suggests not using it anymore. So while some users may find procmail filters useful, we do not support or suggest its use anymore. A detailed manual for procmail is available on the [https://wiki.archlinux.org/index.php/Procmail ArchWiki]. [[Category:Mail]] 5b6dc79b1c6cc5a802b328270fa0e69b8f70baa3 1816 1808 2023-02-24T11:32:43Z Bert 8 wikitext text/x-wiki Your ulyssis account includes an email address: <code>''username''@ulyssis.org</code>. It is important you check your ulyssis mailbox regularly, because all important information will be sent to this address. You can check your e-mail using webmail or an email client of your own. It is also possible to configure your email address in UCC to automatically [[Forwarders|forward]] all correspondence to another address. ==Webmail== You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to login. ==POP and IMAP access== You can access your ulyssis mail with POP or IMAP. The configuration parameters are: * '''server''': <code>mail.ulyssis.org</code> * '''port''': 993 * '''username''': ''your ULYSSIS username'' * '''password''': ''your ULYSSIS password'' * '''security''': SSL ==SMTP== {{SMTPnotice|your mailbox with an external application}} ULYSSIS doesn't offer SMTP. Instead, you can use KULeuven's SMTP server: * '''server''': <code>smtps.kuleuven.be</code> * '''port''': 443 * '''username''': ''your student id'' * '''password''': ''your KULeuven password'' * '''security''': SSL == Advanced == Your emails are stored within your account under ~/Maildir. These files can of course be read with a command line email client such as alpine or mutt. We support sendmail style local delivery using .forward. More information is available in the official documentation of [https://www.sendmail.org/~ca/email/doc8.9/op-sh-2.html#sh-2.8 Sendmail] and [http://www.postfix.org/local.8.html Postfix]. While it's possible to use .forward to simply forward email to other addresses, we recommend only using it when the same feature is not available through our control panel [https://ucc.ulyssis.org UCC]. Specifically, .forward can be used to pass emails to other applications. In the past, a popular application to pass email through was procmail. However, procmail has not seen development for about 2 decades, and its developer suggests not using it anymore. So while some users may find procmail filters useful, we do not support or suggest its use anymore. A detailed manual for procmail is available on the [https://wiki.archlinux.org/index.php/Procmail ArchWiki]. [[Category:Mail]] ad6d205ea9806d9f74b57cccea408155813c09be 0 220 1809 1666 2023-02-24T11:13:29Z Bert 8 wikitext text/x-wiki {{SMTPnotice}} When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to use it as your own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not appear, or this is not your first mailbox; click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, proceed by entering the login details for your mailbox. The first step is to fill in your name, email address and password (this email address should be your ULYSSIS username followed by <code>@ulyssis.org</code>): [[File:Fill in email.png|left|alt=|thumb|432x432px]] Next, the button "Configure manually..." on the bottom left will become clickable (as seen on the screenshot above). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- || || INCOMING || OUTGOING |- || Protocol: || IMAP || SMTP |- || Server: || mail.ulyssis.org || smtps.kuleuven.be |- || Port: || 993 || 443 |- || SSL: || SSL/TLS || SSL/TLS |- | style="padding-right: 10px" | Authentication: || Autodetect || Autodetect |- || Username: | style="padding-right: 10px" | ULYSSIS username || r/m/s/u number |- | colspan="3" | Notice the ports used to configure a ULYSSIS mailbox are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down. |} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, Thunderbird will try to connect to the mail server. When successful, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up will close when the "Done" button has been clicked. After the pop-up closes, a mailbox should be added to the left sidebar of the main Thunderbird window. By clicking on the inbox tab, your emails should start showing up (as seen in the last screenshot). After finishing up this setup, your mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent. [[Category:Mail]] 977ca53969f10db5db2ffa9d9fca8d25dbc34c3b 1815 1809 2023-02-24T11:31:55Z Bert 8 wikitext text/x-wiki {{SMTPnotice|your mailbox in Thundebird}} When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to use it as your own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not appear, or this is not your first mailbox; click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, proceed by entering the login details for your mailbox. The first step is to fill in your name, email address and password (this email address should be your ULYSSIS username followed by <code>@ulyssis.org</code>): [[File:Fill in email.png|left|alt=|thumb|432x432px]] Next, the button "Configure manually..." on the bottom left will become clickable (as seen on the screenshot above). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- || || INCOMING || OUTGOING |- || Protocol: || IMAP || SMTP |- || Server: || mail.ulyssis.org || smtps.kuleuven.be |- || Port: || 993 || 443 |- || SSL: || SSL/TLS || SSL/TLS |- | style="padding-right: 10px" | Authentication: || Autodetect || Autodetect |- || Username: | style="padding-right: 10px" | ULYSSIS username || r/m/s/u number |- | colspan="3" | Notice the ports used to configure a ULYSSIS mailbox are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down. |} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, Thunderbird will try to connect to the mail server. When successful, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up will close when the "Done" button has been clicked. After the pop-up closes, a mailbox should be added to the left sidebar of the main Thunderbird window. By clicking on the inbox tab, your emails should start showing up (as seen in the last screenshot). After finishing up this setup, your mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent. [[Category:Mail]] b10037f830f89917e30181d3918cb442bf2995ff 1817 1815 2023-02-24T11:33:01Z Bert 8 wikitext text/x-wiki {{SMTPnotice|your mailbox in Thunderbird}} When you create a ULYSSIS account, you get an email address: <code>''username''@ulyssis.org</code>. Usually, this address gets forwarded to your KU Leuven email address. However, you can choose to use it as your own [[Mailbox|ULYSSIS mailbox]]. It is possible to check this mailbox via https://webmail.ulyssis.org. However, it is far more convenient and efficient to use a standalone email client. This article will explain the process of adding a mailbox to the Thunderbird client. ==Thunderbird== Thunderbird is a free and open source email client made by Mozilla. It is available for download at https://thunderbird.net. You can then install the downloaded file like you would install any other application. Once installed, launch Thunderbird and configure a mailbox using the steps below. ==Adding a ULYSSIS mailbox to Thunderbird== If this is the first mailbox being added to Thunderbird, the following pop-up should come up: [[File:First Open TB.png|left|alt=|thumb|432x432px]] If the pop-up did not appear, or this is not your first mailbox; click the email button (highlighted in blue in the screenshot below) under the "Set Up Another Account" section: [[File:New Mailbox.png|left|alt=|thumb|600x600px]] Once the pop-up is present, proceed by entering the login details for your mailbox. The first step is to fill in your name, email address and password (this email address should be your ULYSSIS username followed by <code>@ulyssis.org</code>): [[File:Fill in email.png|left|alt=|thumb|432x432px]] Next, the button "Configure manually..." on the bottom left will become clickable (as seen on the screenshot above). When this button is clicked, the pop-up should look like this: [[File:Click Configure Manually.png|left|alt=|thumb|479x479px]] Now, fill in the information as follows: [[File:Fill advanced.png|left|alt=|thumb|479x479px]] {| class="wikitable" |+ Manual settings |- || || INCOMING || OUTGOING |- || Protocol: || IMAP || SMTP |- || Server: || mail.ulyssis.org || smtps.kuleuven.be |- || Port: || 993 || 443 |- || SSL: || SSL/TLS || SSL/TLS |- | style="padding-right: 10px" | Authentication: || Autodetect || Autodetect |- || Username: | style="padding-right: 10px" | ULYSSIS username || r/m/s/u number |- | colspan="3" | Notice the ports used to configure a ULYSSIS mailbox are not automatically recognized by Thunderbird. This means they should be entered manually instead of using the drop-down. |} The "Re-test" button on the bottom right of the following screenshot is used to validate the settings. When pressed, Thunderbird will try to connect to the mail server. When successful, the pop-up should look like this: [[File:After Clicking Retest GOOD.png|left|alt=|thumb|479x479px]] If this test succeeds, the pop-up will close when the "Done" button has been clicked. After the pop-up closes, a mailbox should be added to the left sidebar of the main Thunderbird window. By clicking on the inbox tab, your emails should start showing up (as seen in the last screenshot). After finishing up this setup, your mailbox should synchronize automatically. [[File:After Clicking GetMessages.png|left|alt=|thumb|600x600px]] When sending the first email after configuration, Thunderbird might show a pop-up: "Enter your password for r0000000 on smtps.kuleuven.be:". It is really important to enter your KU Leuven password (the password used for central login), otherwise your email will not be sent. [[Category:Mail]] 9541b46a371c5648680c390f165847679b6c2ff6 10 262 1810 1802 2023-02-24T11:29:57Z Bert 8 wikitext text/x-wiki {{notice|To use {{{1}}}, access to the KU Leuven SMTP server is required|Since 24 February 2023, not all students have access to smtps.kuleuven.be by default anymore. If you are unable to send emails after following the instructions outlined in our documentation, then you may have to register on https://ulyssis.org/smtp/ to (re)gain SMTP access.}} 1eec27db4c99ca98bda31c2aa6584b1f70c26af4 0 3 1818 1752 2023-04-04T20:12:29Z Vincenttc 21 wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Reducing disk usage|Help, my account uses too much disk space]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Making Backups]] * [[Secure file permissions]] * [[Reducing disk usage]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2022]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Sending email from websites]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL/TLS|Getting SSL/TLS (HTTPS security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Claiming a port]] * [[ULYSSIS security measures]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Mailbox in Thunderbird]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Add an alias in ULYSSIS webmail]] * [[Spam]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up WordPress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] * [[Updating WordPress]] * [[Updating MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] * [[Using PHPPgAdmin]] * [[Using Adminer]] * [[Making Backups]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[Exporting your KU Leuven class schedule and calendar]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 9e4bd04c9347a5b0ad0027addb9da049c1f5ea3e 1847 1818 2024-08-24T20:31:32Z Pcy 37 /* Webserver */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Reducing disk usage|Help, my account uses too much disk space]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Making Backups]] * [[Secure file permissions]] * [[Reducing disk usage]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2024]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Sending email from websites]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL/TLS|Getting SSL/TLS (HTTPS security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Claiming a port]] * [[ULYSSIS security measures]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Mailbox in Thunderbird]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Add an alias in ULYSSIS webmail]] * [[Spam]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up WordPress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] * [[Updating WordPress]] * [[Updating MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] * [[Using PHPPgAdmin]] * [[Using Adminer]] * [[Making Backups]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[Exporting your KU Leuven class schedule and calendar]] </div> <div style="clear:both;"></div> </div> __NOTOC__ 1d8bc62466e94ff732f8a2f0b2617aef3c097fed 0 98 1819 1575 2023-05-09T21:25:19Z Bert 8 wikitext text/x-wiki ==About== MediaWikiShibboleth is a MediaWiki extension created by ULYSSIS to allow for login through the Central KU Leuven Login (Shibboleth). The extension disables editing and creating of (talk) pages by anonymous users, and requires Shibboleth authentication for account creation and login. ==Prerequisites== Before installing, you need to have SSL and Shibboleth (Central KU Leuven Login) enabled on your domain. * For instructions on how to get SSL/TLS: https://docs.ulyssis.org/Getting_SSL/TLS * Information about requesting Shibboleth: https://docs.ulyssis.org/Shibboleth Once you know everything is installed properly, you can proceed to install the extension. ==Installation== First, download the latest release from [https://github.com/ULYSSIS-KUL/MediaWikiShibboleth/releases/latest/download/MediaWikiShibboleth.zip github]. Unzip the zip file in the <code>extensions/</code> directory in your MediaWiki installation folder. Make sure there is now a <code>MediaWikiShibboleth</code> folder in <code>extensions/</code>. Finally, locate the <code>LocalSettings.php</code> file in your MediaWiki installation folder and add the following lines to it: wfLoadExtension('MediaWikiShibboleth'); $wgGroupPermissions['*']['createaccount'] = false; $wgRevokePermissions['Shibboleth']['editmyprivateinfo'] = true; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['writeapi'] = false; If you want to allow anonymous editing, you should <b>not</b> add the last 2 lines of the previous paragraph. This really defeats the purpose of the extension though. ==Configuration== MediaWikiShibboleth has some configuration options which allow for restricting who can log in to your wiki. These restrictions are cumulative. For example, it is possible to allow only students enrolled in a specific degree or programme to log in. These options work especially well with restricting the access of the wiki to logged-in users only. === Restricting access to logged-in users only === This option is not an option provided by the extension, but very useful in its context. If you do not want guest visitors to be able to view any page of your wiki, add the following line to your <code>LocalSettings.php</code>: $wgGroupPermissions['*']['read'] = false; === MWSStudentsOnly === This option tells MediaWikiShibboleth to only allow students to log in. KU Leuven employees, alumni, doctoral students, teaching assistants etc. will not be able to log in using their employee account. Do keep in mind doctoral students also have a student account, which will still work. Set this option by adding $wgMWSStudentsOnly = true; to <code>LocalSettings.php</code>. If you combine this option with "Restricting access to logged-in users only", only students will be able to view, log in and edit your wiki. === MWSAllowedKULids === This option can be used to only allow specific KUL ids to log in. An example KUL id is "r0653730". If this option is set to "", no KUL id checking will be performed. Set this option by adding $wgMWSAllowedKULids = "r0653730, r0300342, KUL id 3..."; to <code>LocalSettings.php</code>. You can add as many KUL ids as you like, separated by a comma. === MWSAllowedDegrees === This option can be used to only allow students enrolled in specific degrees/programmes to log in. An example KUL degree number is "51016742". If this option is set to "", no degree number checking will be performed. Set this option by adding $wgMWSAllowedDegrees = "51016742, 51016835, 51016753..."; to <code>LocalSettings.php</code>. You can add as many degree numbers as you like, separated by a comma. === Translations === It's possible to translate and modify all public MediaWikiShibboleth messages. The translations can be found in the <code>extensions/MediaWikiShibboleth/i18n/</code>. Dutch (<code>nl.json</code>) and English (<code>en.json</code>) translations are already provided. Even the provided translations can be customized, and we strongly advise you to do so, in order to match them with your wiki situation. ==Operation== When the extension is installed successfully, anonymous users will not be able to create an account and the account creation page will be removed from the home page. On the log in page, a new image is added: if you click on this image, you will be logged in using Shibboleth. If you want to log in with an explicit username/password combination, you can click "Login without Central KU Leuven login" to expand a login menu. The new log in page looks like this with "Login without Central KU Leuven login" expanded: [[File:Login.png|thumb|none]] ==Creating accounts== If you want to create password accounts, you can navigate to the CreateAccount special page (make sure you are logged in using an administrator account). This is necessary to create accounts for users without a KU Leuven login. You should select "Use a temporary random password and send it to the specified email address". [[File:CreateAccount.png|thumb|none]] [[Category:Security & anti-spam]] [[Category:CMSs]] 0e58737456f924e3e10bebe3e9e82a331222504f 0 37 1822 1459 2023-09-11T19:11:52Z Thomasd 40 /* Python and Django */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <code>.cgi</code> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <code>www</code> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <code>hello.cgi</code>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your programming languae, framework or application. Just do a web search for "''keyword'' mod_fcgid", where ''keyword'' is the programming language, framework or application you're planning to use, and you will often find good instructions. We've included some examples below You'll want to treat this starter script as a <code>mod_fcgid</code> script, and usually, you'll want to redirect everything to this script, so you can use an <code>.htaccess</code> file that looks like this: <syntaxhighlight lang="apache">Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</syntaxhighlight> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <code>.htaccess</code> file. {{warning|Warning!|Do not place sensitive files inside the web accessible folder. Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.}} It is adviced to only place the fcgi starter script, <code>.htaccess</code> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [[Managing_Cron_jobs | cronjob]] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than where it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django and Go examples below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <code>touch</code>: <pre>touch starter.fcgi</pre> Replace <code>starter.fcgi</code> with the name of your starter script. === Examples === ==== Python and Django ==== If you want to make a website using Python and [https://www.djangoproject.com/ Django], we recommend that you use a virtual environment. You can use the following steps to get up and running with Django on your ULYSSIS hosting account. <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <code>~/.venv</code>, for example: <pre>python3 -m venv ~/.venv</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django and flup for FastCGI inside of this virtualenv: <pre>pip install django flup6</pre> </li> <li> Create a new Django project: <pre>django-admin startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Edit the allowed hosts in your Django project's settings, in <code>mysite/mysite/settings.py</code>. Look for the line <code>ALLOWED_HOSTS = []</code> and replace it with: <pre> ALLOWED_HOSTS = [ 'username.ulyssis.be', 'username.studentenweb.org' ] </pre> </li> <li> Put an <code>.htaccess</code> file in your site's directory, e.g. the <code>www</code> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace <code>user</code> with org if you are an organization, and <code>username</code> with your ULYSSIS username): <syntaxhighlight lang="python">#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </syntaxhighlight> Call this script <code>mysite.fcgi</code>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [https://flask.palletsprojects.com/en/1.1.x/deploying/fastcgi/ Flask documentation for FastCGI] ==== Go ==== To make a website or web application in Go and host it on your ULYSSIS hosting account, you can use the standard library ''fcgi'' package. <ol> <li> [[Accessing shell servers over SSH|Log in to a shell server]]</li> <li> Put an <code>.htaccess</code> file in your site's directory (e.g. the <code>www</code> folder) with a reference to your executable. Here we've chosen <code>mysite.fcgi</code>, but you can adapt this to your liking. <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Write your code, and compile the binary to <code>mysite.fcgi</code>. Below you can find a basic example of how to register two handlers (of which one is the fallback), then start the FastCGI client, and finally have a function (which is called as a goroutine) to check if the binary has been replaced so old processes don't stick around. <syntaxhighlight lang="go">package main import ( "fmt" "net/http" "net/http/fcgi" "os" "path/filepath" "time" ) func uri_interesting(w http.ResponseWriter, r *http.Request) { w.WriteHeader(http.StatusOK) fmt.Fprintln(w, "<h1>Oh, seems like this link isn't that interesting after all</h1>") fmt.Fprintln(w, "<p>Back to the <a href=\"/\">Homepage</a></p>") } func uri_default(w http.ResponseWriter, r *http.Request) { if r.URL.Path != "/" { w.WriteHeader(http.StatusNotFound) fmt.Fprintln(w, "<h1>This page doesn't exist</h1>") fmt.Fprintln(w, "<p>Back to the <a href=\"/\">Homepage</a></p>") } else { w.WriteHeader(http.StatusOK) fmt.Fprintln(w, "<h1>Welcome to this testwebsite!</h1>") fmt.Fprintln(w, "<p>This website is written in Go but doesn't really do much.") fmt.Fprintln(w, "Feel free to visit this <a href=\"/interesting/link\">Interesting link</a> or this <a href=\"/non-existent/link\">non-existent link</a>.</p>") } } func main() { go check_selfreplacement() http.HandleFunc("/interesting/link", uri_interesting) http.HandleFunc("/", uri_default) if err := fcgi.Serve(nil, nil); err != nil { panic(err) } } func check_selfreplacement() { fcgi_location, _ := os.Executable() fcgi_location, _ = filepath.EvalSymlinks(fcgi_location) start_stat, _ := os.Stat(fcgi_location) for { current_stat, _ := os.Stat(fcgi_location) if start_stat.ModTime() != current_stat.ModTime() { os.Exit(0) } time.Sleep(1 * time.Second) } } </syntaxhighlight> If you want to give this example a try, save it as <code>mysite.fcgi.go</code> and then use <code>go build mysite.fcgi.go</code> to compile it. </li> <li>Visit your website to verify everything works</li> </ol> [[Category:Webserver]] 6d9989e43b0dc63a432c8b5e2f61dfc2fd6d56ea 1823 1822 2023-09-11T19:13:17Z Thomasd 40 /* Python and Django */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <code>.cgi</code> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <code>www</code> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <code>hello.cgi</code>): <pre>#!/usr/bin/env python print 'Content-Type: text/plain\n' print 'Hello world!'</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your programming languae, framework or application. Just do a web search for "''keyword'' mod_fcgid", where ''keyword'' is the programming language, framework or application you're planning to use, and you will often find good instructions. We've included some examples below You'll want to treat this starter script as a <code>mod_fcgid</code> script, and usually, you'll want to redirect everything to this script, so you can use an <code>.htaccess</code> file that looks like this: <syntaxhighlight lang="apache">Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</syntaxhighlight> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <code>.htaccess</code> file. {{warning|Warning!|Do not place sensitive files inside the web accessible folder. Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.}} It is adviced to only place the fcgi starter script, <code>.htaccess</code> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [[Managing_Cron_jobs | cronjob]] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than where it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django and Go examples below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <code>touch</code>: <pre>touch starter.fcgi</pre> Replace <code>starter.fcgi</code> with the name of your starter script. === Examples === ==== Python and Django ==== If you want to make a website using Python and [https://www.djangoproject.com/ Django], we recommend that you use a virtual environment. You can use the following steps to get up and running with Django on your ULYSSIS hosting account. <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <code>~/.venv</code>, for example: <pre>python3 -m venv ~/.venv</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django and flup for FastCGI inside of this virtualenv: <pre>pip install django flup6</pre> </li> <li> Create a new Django project: <pre>django-admin startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Edit the allowed hosts in your Django project's settings, in <code>mysite/mysite/settings.py</code>. Look for the line <code>ALLOWED_HOSTS = []</code> and replace it with: <pre> ALLOWED_HOSTS = [ 'username.ulyssis.be', 'username.studentenweb.org' ] </pre> Use your ULYSSIS username in place of ''username''. </li> <li> Put an <code>.htaccess</code> file in your site's directory, e.g. the <code>www</code> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace <code>user</code> with org if you are an organization, and <code>username</code> with your ULYSSIS username): <syntaxhighlight lang="python">#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </syntaxhighlight> Call this script <code>mysite.fcgi</code>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [https://flask.palletsprojects.com/en/1.1.x/deploying/fastcgi/ Flask documentation for FastCGI] ==== Go ==== To make a website or web application in Go and host it on your ULYSSIS hosting account, you can use the standard library ''fcgi'' package. <ol> <li> [[Accessing shell servers over SSH|Log in to a shell server]]</li> <li> Put an <code>.htaccess</code> file in your site's directory (e.g. the <code>www</code> folder) with a reference to your executable. Here we've chosen <code>mysite.fcgi</code>, but you can adapt this to your liking. <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Write your code, and compile the binary to <code>mysite.fcgi</code>. Below you can find a basic example of how to register two handlers (of which one is the fallback), then start the FastCGI client, and finally have a function (which is called as a goroutine) to check if the binary has been replaced so old processes don't stick around. <syntaxhighlight lang="go">package main import ( "fmt" "net/http" "net/http/fcgi" "os" "path/filepath" "time" ) func uri_interesting(w http.ResponseWriter, r *http.Request) { w.WriteHeader(http.StatusOK) fmt.Fprintln(w, "<h1>Oh, seems like this link isn't that interesting after all</h1>") fmt.Fprintln(w, "<p>Back to the <a href=\"/\">Homepage</a></p>") } func uri_default(w http.ResponseWriter, r *http.Request) { if r.URL.Path != "/" { w.WriteHeader(http.StatusNotFound) fmt.Fprintln(w, "<h1>This page doesn't exist</h1>") fmt.Fprintln(w, "<p>Back to the <a href=\"/\">Homepage</a></p>") } else { w.WriteHeader(http.StatusOK) fmt.Fprintln(w, "<h1>Welcome to this testwebsite!</h1>") fmt.Fprintln(w, "<p>This website is written in Go but doesn't really do much.") fmt.Fprintln(w, "Feel free to visit this <a href=\"/interesting/link\">Interesting link</a> or this <a href=\"/non-existent/link\">non-existent link</a>.</p>") } } func main() { go check_selfreplacement() http.HandleFunc("/interesting/link", uri_interesting) http.HandleFunc("/", uri_default) if err := fcgi.Serve(nil, nil); err != nil { panic(err) } } func check_selfreplacement() { fcgi_location, _ := os.Executable() fcgi_location, _ = filepath.EvalSymlinks(fcgi_location) start_stat, _ := os.Stat(fcgi_location) for { current_stat, _ := os.Stat(fcgi_location) if start_stat.ModTime() != current_stat.ModTime() { os.Exit(0) } time.Sleep(1 * time.Second) } } </syntaxhighlight> If you want to give this example a try, save it as <code>mysite.fcgi.go</code> and then use <code>go build mysite.fcgi.go</code> to compile it. </li> <li>Visit your website to verify everything works</li> </ol> [[Category:Webserver]] 1d68200bf94cb46eae2556e4d73c799d6d467bb5 1833 1823 2024-04-14T22:53:16Z Bert 8 /* CGI */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <code>.cgi</code> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <code>www</code> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <code>hello.cgi</code>): <pre>#!/usr/bin/env python3 print('Content-Type: text/plain\n') print('Hello world!')</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your programming languae, framework or application. Just do a web search for "''keyword'' mod_fcgid", where ''keyword'' is the programming language, framework or application you're planning to use, and you will often find good instructions. We've included some examples below You'll want to treat this starter script as a <code>mod_fcgid</code> script, and usually, you'll want to redirect everything to this script, so you can use an <code>.htaccess</code> file that looks like this: <syntaxhighlight lang="apache">Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</syntaxhighlight> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <code>.htaccess</code> file. {{warning|Warning!|Do not place sensitive files inside the web accessible folder. Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.}} It is adviced to only place the fcgi starter script, <code>.htaccess</code> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [[Managing_Cron_jobs | cronjob]] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than where it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django and Go examples below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <code>touch</code>: <pre>touch starter.fcgi</pre> Replace <code>starter.fcgi</code> with the name of your starter script. === Examples === ==== Python and Django ==== If you want to make a website using Python and [https://www.djangoproject.com/ Django], we recommend that you use a virtual environment. You can use the following steps to get up and running with Django on your ULYSSIS hosting account. <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <code>~/.venv</code>, for example: <pre>python3 -m venv ~/.venv</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django and flup for FastCGI inside of this virtualenv: <pre>pip install django flup6</pre> </li> <li> Create a new Django project: <pre>django-admin startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Edit the allowed hosts in your Django project's settings, in <code>mysite/mysite/settings.py</code>. Look for the line <code>ALLOWED_HOSTS = []</code> and replace it with: <pre> ALLOWED_HOSTS = [ 'username.ulyssis.be', 'username.studentenweb.org' ] </pre> Use your ULYSSIS username in place of ''username''. </li> <li> Put an <code>.htaccess</code> file in your site's directory, e.g. the <code>www</code> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace <code>user</code> with org if you are an organization, and <code>username</code> with your ULYSSIS username): <syntaxhighlight lang="python">#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </syntaxhighlight> Call this script <code>mysite.fcgi</code>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [https://flask.palletsprojects.com/en/1.1.x/deploying/fastcgi/ Flask documentation for FastCGI] ==== Go ==== To make a website or web application in Go and host it on your ULYSSIS hosting account, you can use the standard library ''fcgi'' package. <ol> <li> [[Accessing shell servers over SSH|Log in to a shell server]]</li> <li> Put an <code>.htaccess</code> file in your site's directory (e.g. the <code>www</code> folder) with a reference to your executable. Here we've chosen <code>mysite.fcgi</code>, but you can adapt this to your liking. <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Write your code, and compile the binary to <code>mysite.fcgi</code>. Below you can find a basic example of how to register two handlers (of which one is the fallback), then start the FastCGI client, and finally have a function (which is called as a goroutine) to check if the binary has been replaced so old processes don't stick around. <syntaxhighlight lang="go">package main import ( "fmt" "net/http" "net/http/fcgi" "os" "path/filepath" "time" ) func uri_interesting(w http.ResponseWriter, r *http.Request) { w.WriteHeader(http.StatusOK) fmt.Fprintln(w, "<h1>Oh, seems like this link isn't that interesting after all</h1>") fmt.Fprintln(w, "<p>Back to the <a href=\"/\">Homepage</a></p>") } func uri_default(w http.ResponseWriter, r *http.Request) { if r.URL.Path != "/" { w.WriteHeader(http.StatusNotFound) fmt.Fprintln(w, "<h1>This page doesn't exist</h1>") fmt.Fprintln(w, "<p>Back to the <a href=\"/\">Homepage</a></p>") } else { w.WriteHeader(http.StatusOK) fmt.Fprintln(w, "<h1>Welcome to this testwebsite!</h1>") fmt.Fprintln(w, "<p>This website is written in Go but doesn't really do much.") fmt.Fprintln(w, "Feel free to visit this <a href=\"/interesting/link\">Interesting link</a> or this <a href=\"/non-existent/link\">non-existent link</a>.</p>") } } func main() { go check_selfreplacement() http.HandleFunc("/interesting/link", uri_interesting) http.HandleFunc("/", uri_default) if err := fcgi.Serve(nil, nil); err != nil { panic(err) } } func check_selfreplacement() { fcgi_location, _ := os.Executable() fcgi_location, _ = filepath.EvalSymlinks(fcgi_location) start_stat, _ := os.Stat(fcgi_location) for { current_stat, _ := os.Stat(fcgi_location) if start_stat.ModTime() != current_stat.ModTime() { os.Exit(0) } time.Sleep(1 * time.Second) } } </syntaxhighlight> If you want to give this example a try, save it as <code>mysite.fcgi.go</code> and then use <code>go build mysite.fcgi.go</code> to compile it. </li> <li>Visit your website to verify everything works</li> </ol> [[Category:Webserver]] 8e3586bc6b0fbbaccf1cb339c966bff9ba50e332 0 10 1824 1708 2023-09-17T14:55:44Z Bert 8 /* Requesting SSL from the KU Leuven */ wikitext text/x-wiki ULYSSIS does not sell or offer any other SSL certificates than our self-signed certificate. We will however guide requests and install a certificate from the KU Leuven if you are eligible for one, and we will also install certificates you have bought or obtained elsewhere. ==Requesting SSL from the KU Leuven== The KU Leuven partners with other universities through TERENA/Géant to arrange certificates for its services, organisations and academic structures. We have permission to request free SSL/TLS certificates for student unions (kringen) recognized by LOKO or faculty consultative bodies (facultaire overlegorganen) recognized by Studentenraad KU Leuven as well as organisations (vrije verenigingen) recognized by LOKO or KU Leuven. We are not eligible to request SSL/TLS certificates for individuals with a personal account, nor research groups or staff associations. We suggest those latter groups request certificates from KU Leuven ICTS directly or consider Let's Encrypt or another third party service. Before sending us a request, the following steps have to be performed: * Set up the site that needs SSL if that's not already the case * Make sure our nameservers are being used for the involved domain(s), as explained on [[Adding domain names]] * Consider all subdomains (whether separate websites or not) you wish to have certificates for * Make a list of all relevant arguments for your use of SSL/TLS certificates. It's important to consider aspects of your website where important or personal information is exchanged: registration, login pages, newsletter signup, etc. These arguments have to apply to your current site. Future plans are not considered valid arguments. When '''all''' steps are done, the account holder of the ULYSSIS account can send an email to ulyssis@ulyssis.org containing their name, the name of the organisation, the relevant arguments what you will use SSL for and the domain and if needed a list of subdomains that should be covered by the certificate. Based on our previous experience and our arrangements with ICTS we will consider whether you are eligible for certificates and whether your request is well-founded. We will then generate the required cryptographic key and request and submit them on the certificate platform supplied by ICTS and its partners. Depending on the situation, the verification and delivery of the certificate can take some time. As soon as the certificate has been issued, we will install it and notify you. For procedures to request certificates, we follow instructions from ICTS. These instructions have changed several times in the past, so it's possible for a new request or for a renewal, you may have to follow a different procedure or make changes. {{notice|Limitations|ICTS does not allow SSL requests for historic *.student.kuleuven.be domains. We judge requests for username.ulyssis.be and username.studentenweb.org on an individual basis.}} ==External certificates== To install external certificates we require the certificate itself, the private key, and possibly the chain. We prefer you also send us (a link to) the documentation of your supplier. As certificate files, especially private keys, are a delicate matter we suggest you just email us the path in your homedirectory you've put them and we will move them over to the webserver safely. For more information concerning this procedure you can always contact us on ulyssis@ulyssis.org ===Let's Encrypt=== We currently do not have an automated system for renewing and deploying certificates such as those supplied by Let's Encrypt. We are however looking into automating this process in the future. Since more of our users are starting to use Let's Encrypt, and all of their certificates need to be renewed frequently, we have a specific procedure now. When wishing to add a certificate with Let's Encrypt to your website, or renew your existing one, first create a folder <code>letsencrypt</code> in your '''home directory'''. Then add a folder per domain or group of domains: mkdir -p ~/letsencrypt/mydomain.be Certificates should be stored in these folders, according to the following file structure: letsencrypt/ └── mydomain.be/ ├── mydomain.be.chain (the CA file) ├── mydomain.be.crt (the cert file; "public key") └── mydomain.be.key (the key file; "private key") If you already possess the necessary files, renaming and copying them accordingly is sufficient. '''You still have to email us to install your certificate.''' More information in the last section on this page. Otherwise, you can generate or renew your certificates using acme.sh. This is explained in the next section. ==== Generating certificates ==== {{notice|If you use a <code>.htaccess</code> file in the webroot of the domain name, make sure to add the following lines at the top of the file:|<pre><IfModule mod_rewrite.c> RewriteRule "^.well-known/acme-challenge" - [L] </IfModule></pre>}} Because the normal method of generating Let's Encrypt certificates, certbot, requires root access, it's impossible for normal users to do so on our servers. Luckily there are plenty of alternatives which implement the Let's Encrypt protocol. In this tutorial, we'll show how to use the acme.sh program to generate certificates on the ULYSSIS servers. '''If you already followed this section to generate certificates, skip to the next section on renewing certificates.''' Firstly, execute the following commands to download the acme.sh script in your home directory and make it executable: curl -o ~/acme.sh https://raw.githubusercontent.com/acmesh-official/acme.sh/master/acme.sh chmod +x ~/acme.sh Next, determine for which domains and subdomains you want to generate a certificate. You will need to generate a single certificate for each domain and subdomain which points to the same folder on your account (in most cases this is <code>www</code> in your home directory). The following example command will generate a certificate for <code>mydomain.be</code> and <code>www.mydomain.be</code> which points to the <code>www</code> folder in the home directory. '''Change the parameters''' as explained below before executing this command! ~/acme.sh --issue --cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt --key-file ~/letsencrypt/mydomain.be/mydomain.be.key --ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain -m "email@mydomain.be" -w ~/www -d mydomain.be -d www.mydomain.be --server letsencrypt The explanation of these many parameters is as follows: * <code>--issue</code> tells acme.sh to generate a new certificate. * <code>--cert-file ~/letsencrypt/mydomain.be/mydomain.be.crt</code> tells acme.sh to store the certificate file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. '''This folder should already exist''', please refer to the previous section if you have not created this folder yet. * <code>--key-file ~/letsencrypt/mydomain.be/mydomain.be.key</code> tells acme.sh to store the key file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>--ca-file ~/letsencrypt/mydomain.be/mydomain.be.chain</code> tells acme.sh to store the CA file in the <code>letsencrypt/mydomain.be</code> folder in your home directory, using the special file name as required by the file structure. * <code>-m "email@mydomain.be"</code> tells acme.sh the email address associated with the certificate. Let's Encrypt will remind this email address (if provided) when the certificate is close to expiring. * <code>-w ~/www</code> tells acme.sh where the domains in this certificate point to. Make sure to change the <code>www</code> part if the domains point to a different folder in your home directory. * <code>-d mydomain.be</code> and <code>-d www.mydomain.be</code> tell acme.sh that the certificate should protect <code>mydomain.be</code> and <code>www.mydomain.be</code>. The first domain name will be the "main domain", which is important for renewing. You should '''add all domain names''' pointing to the <code>-w</code> folder. * <code>--server letsencrypt</code> tells acme.sh to use https://letsencrypt.org/ as Certificate Authority (CA). After executing this command with the right parameters, your certificate should be generated successfully. When you have to renew the certificate in the future, you should follow the instructions in the next section. '''Don't forget to email us to install your new certificate.''' More information in the last section on this page. ==== Renewing certificates ==== To renew the certificates of <code>mydomain.be</code>, just execute: ~/acme.sh --renew -d mydomain.be For the <code>-d</code> parameter, you have to provide the '''first''' domain name you provided when generating the certificate (in the previous section, this was <code>mydomain.be</code>. If you are not sure which domain name to use, you can execute the command: ~/acme.sh --list This will generate a list of available certificates, which looks a bit like this: Main_Domain KeyLength SAN_Domains CA Created Renew mydomain.be "" www.mydomain.be LetsEncrypt.org ... ... ... ... ... ... ... ... In this example, the main domain is <code>mydomain.be</code>. The renewed certificates will automatically be copied to the files you provided in the command to generate the certificates (see previous section). '''After renewing the certificate, you have to email us to install your certificate.''' More information in the next section. ==== Getting your certificates installed ==== Check whether everything is stored correctly by executing the following command: ulyssis-certificate check mydomain.be If everything looks good, you should only see lines starting with <code>[ OK ]</code>. Any line starting with <code>[FAIL]</code> or <code>[ABRT]</code> means a check has failed, you must correct this error before asking us to install your certificate. Once all steps are done and if you are the '''account holder''', '''you can send us an email clearly stating the account name, for which domains we need to add certificates and where the files are stored'''. If you are renewing existing certificates, also clearly state that in your email. We have largely automated the installation of certificates. If you do not follow these instructions, your request will be denied or you may end up with broken SSL, so make sure you follow this procedure carefully. [[Category:Webserver]] 9c6da1574e9aba5f7089b6c21d5eb6238ea5cc1d 0 20 1825 1569 2023-09-28T06:59:17Z Ziik 53 /* Finishing up installation */ wikitext text/x-wiki This page will go through a basic setup of WordPress, and it gives a few specifics for setting it up on a hosted account over at ULYSSIS. ==Putting setup-files in place== First you need to download WordPress from their website, https://wordpress.org/download/. After you've received a zip file, you have to extract it using your file manager (Windows: ''use right-click and select "extract all"''; OSX: ''double-click the zip, it automatically extracts''; Linux: ''right-click the file, and select "extract here"''), this gives you a directory named <code>wordpress</code>. Next, you have to move the '''contents''' of the <code>wordpress</code> directory to your webroot directory on our servers. Mostly this will be the <code>www</code> directory. Your webroot can be accessed via SFTP. If you need further instructions, you can find detailed instructions on: [[Accessing your files]]. == Setting up a database == Besides files, we also need a database to install WordPress on. If you haven't created a new database for the purpose of this installation, you can do this through UCC. Instruction on how to do this are available on [[Using MySQL]]. If you haven't created a database user yet, or don't know the password, you can also find more information there.<br> '''Warning:''' Postgresql databases are not supported by WordPress, only use MySQL databases. == Installing WordPress == Now we are ready to install WordPress, so we need to visit the web installer. If you're using a custom domain based on this guide: [[Adding domain names]], you can access the installer by visiting your domain. If you do not use such a domain, the installer can be found on <code>username.studentenweb.org</code> or <code>username.ulyssis.be</code> (replace <code>username</code> with your actual username). This is where you have to set up your website. The easiest way to do this, is by following the wizard. The setup will ask you for your database configuration: *'''Database Name/Databasenaam:''' the name of the MySQL database *'''Username/Gebruikersnaam:''' your username *'''Password/Wachtwoord:''' your MySQL database password *'''Database Host/Hostnaam:''' <code>mysql.ulyssis.org</code> *'''Table Prefix:''' only change this if you have multiple installations of WordPress in your database<br> So it will look something like this:<br> [[File:wordpress_screenshot.png|thumb|left|600px]] In the next step you need to fill in your own preferences. == Finishing up installation == Finally you will be prompted to log into your WordPress website. Now the installation is finished. {{info|We advise all WordPress users to enable automatic updates for their plugins, themes and WordPress itself. You can find detailed instructions on [[Updating WordPress]].}} To help you design your website, there are a few guides from WordPress that can help you: *https://wordpress.org/support/article/first-steps-with-wordpress-b/ *https://wordpress.org/support/article/using-themes/#get-new-themes *https://wordpress.org/support/article/managing-plugins/ ==Setting up multiple instances of WordPress== If you want to have multiple instances of a WordPress site, you need to create a new folder in your <code>www</code> directory on your shell account. Then you need a virtual host for this folder, for this you have to send us an email asking for this. After your new virtual host has been configured, you need to do the same steps that you would do for a regular WordPress installation, i.e. the steps in the section above. You can also use WordPress' [https://wordpress.org/support/article/create-a-network/ multisite] option. If you need more help with this, you can find it [https://wordpress.org/support/forum/multisite here]. [[Category:CMSs]] 5d145c104acfe3045766b6f2029a29ac94f779f2 0 221 1826 1712 2023-10-26T08:13:04Z Erico 50 /* Ignoring specific software */ wikitext text/x-wiki ==Introduction== Many of our users use the same popular software to run their website. However, as is common in popular and widespread software, various bugs or errors can occur in the program. These flaws can be exploited by hackers to gain access to websites or databases. Whenever a new update is released for any popular software (e.g., WordPress, MediaWiki, Joomla) hackers will find out which security flaws have been patched, and using this knowledge, they try to find users who haven't updated their software, to gain access to the websites or databases. This is the reason why it is so critical to update the software itself, plugins, themes, or any related software as soon as the updates roll out. To help facilitate this and prevent security breaches, we have created a tool, the Software Version Checker, to help you keep the most commonly used software up-to-date. Currently, this feature is only active if you have an organization or student union account. ==What to do when you receive an e-mail== When you receive an e-mail from the Software Version Checker, it is of utmost importance to update the software mentioned in the e-mail. It is also the best time to check if the other software you use is up-to-date. As mentioned below, our tool does not check all software. You can find more information [[Updating WordPress|here]] on how to automate this for WordPress to save a lot of time and effort. Since updating MediaWiki can be a somewhat daunting process, we have made a more detailed guide available on [[Updating MediaWiki]]. ==Supported Software== Sadly not every piece of software can be supported. Because of this, we have decided to choose the most popular software, since they are more likely to get security breaches. *Drupal (including modules and themes) *Joomla (Plugins are not supported) *MediaWiki (MediaWiki Extensions and Themes are not supported) *phpBB (including plugins and styles) *WordPress (including plugins and themes) ==Functionality of the Software Version Checker== The Software Version Checker fulfills the following functions : *Scan relevant files, detect supported software, and store in database *Check the version and validity of outdated software *Notify accounts that are using outdated software The Software Version Checker does this once every day. ==Ignoring specific software== The Software Version Checker allows specified paths to be excluded from its search. If you believe you have software that should be ignored (for example certain custom plugins or themes), you are free to e-mail a request to ulyssis@ulyssis.org. Please list your account name, the location of the specific file(s), the nature of what is being detected, and a detailed description of the specific situation. ==Ignoring Organisations/Student Unions== The Software Version Checker also allows our users to ignore specific Organisations or Student Unions entirely. This feature is possible on request, but only after extensive deliberation with ULYSSIS. Enabling this feature also has possible consequences; no more mails about software that is outdated, unless it is enabled on request, and no possible support if the user's account gets hacked. If the account does get hacked it will be suspend immediately. 42a3ab74fd3bef86b378eacc4af1c634e2a6d148 0 263 1827 2023-10-26T08:35:36Z Erico 50 Created page with "To register an account, follow these steps: # Go to https://ucc.ulyssis.org/accounts and log in using your Central KU Leuven Account. # Select the kind of account you wish to..." wikitext text/x-wiki To register an account, follow these steps: # Go to https://ucc.ulyssis.org/accounts and log in using your Central KU Leuven Account. # Select the kind of account you wish to register: #* Most people will want to register a '''regular account''' for '''personal use'''. #* If you are a '''recognised organisation''' by LOKO, the KU Leuven or another relevant entity, you may be entitled to an organisation account, which has a reduced price. You can use the following to verify if you are eligible: #**The list of associations (vrije verenigingen) recognised by [http://loko.be/verenigingen/ LOKO]. #**If you are a daughter organisation of one or multiple faculty unions (kringen), for example a fakbar. #**KU Leuven research groups. Please email us on [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org] with a link to your faculty/department's list of research groups. #**Organisations recognised by their faculty as an (optional) part of the curriculum and that have a permanent character. For example the [https://iiw.kuleuven.be/studeren/opleidingen/techinvent/ventures-teams teams] of the Postgraduate Tech Innovations in Ventures & Teams at Group T. #**Organisations outside of Campus Leuven, but within the KU Leuven association, are considered on an indivual basis. Feel free to send us more details on [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org] and we will review your particular situation. #*If you are a recognised '''faculty union''' (kring), assembly organisation (overkoepelende organisatie), or '''faculty consultative body''' (facultair overlegorgaan) you are entitled to a free account. You can use the following to verify if you are eligible: #**The list of recognised faculty unions (kringen) from LOKO on http://loko.be/verenigingen/. #** The list of recognised assembly organisations (overkoepelende organisaties) on the [https://kennisdatabank.loko.be/index.php/Studentenorganisaties_in_Leuven#Overkoepelende_organisaties LOKO knowledge database]. #**The list of recognised faculty consultative bodies from the Studentenraad KU Leuven on https://www.sturakuleuven.be/onze-werking/facultaire-overlegorganen/. # After picking your account type you have to choose which options you want, as well as a username and a language. # Accept the ULYSSIS terms of use and confirm your order. # An email will be sent to your KU Leuven email address to confirm your order alongside a request for payment. # As soon as we have received and processed your payment, your account will be activated and you will receive instructions to set a password. e878845c657ef4b3d3aeae7aed2649632ea91bbb 1828 1827 2023-10-26T08:36:21Z Erico 50 wikitext text/x-wiki To register an account, follow these steps: # Go to https://ucc.ulyssis.org/accounts and log in using your Central KU Leuven Account. # Select the kind of account you wish to register: #* Most people will want to register a '''regular account''' for '''personal use'''. #* If you are a '''recognised organisation''' by LOKO, the KU Leuven or another relevant entity, you may be entitled to an organisation account, which has a reduced price. You can use the following to verify if you are eligible: #**The list of associations (vrije verenigingen) recognised by [http://loko.be/verenigingen/ LOKO]. #**KU Leuven research groups. Please email us on [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org] with a link to your faculty/department's list of research groups. #**Organisations recognised by their faculty as an (optional) part of the curriculum and that have a permanent character. For example the [https://iiw.kuleuven.be/studeren/opleidingen/techinvent/ventures-teams teams] of the Postgraduate Tech Innovations in Ventures & Teams at Group T. #**If you are a daughter organisation of one or multiple faculty unions (kringen), for example a fakbar. #**Organisations outside of Campus Leuven, but within the KU Leuven association, are considered on an indivual basis. Feel free to send us more details on [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org] and we will review your particular situation. #*If you are a recognised '''faculty union''' (kring), assembly organisation (overkoepelende organisatie), or '''faculty consultative body''' (facultair overlegorgaan) you are entitled to a free account. You can use the following to verify if you are eligible: #**The list of recognised faculty unions (kringen) from LOKO on http://loko.be/verenigingen/. #** The list of recognised assembly organisations (overkoepelende organisaties) on the [https://kennisdatabank.loko.be/index.php/Studentenorganisaties_in_Leuven#Overkoepelende_organisaties LOKO knowledge database]. #**The list of recognised faculty consultative bodies from the Studentenraad KU Leuven on https://www.sturakuleuven.be/onze-werking/facultaire-overlegorganen/. # After picking your account type you have to choose which options you want, as well as a username and a language. # Accept the ULYSSIS terms of use and confirm your order. # An email will be sent to your KU Leuven email address to confirm your order alongside a request for payment. # As soon as we have received and processed your payment, your account will be activated and you will receive instructions to set a password. a51c753597bd608ce5958d7a460628c8b1fd4b25 6 264 1829 2023-11-28T20:02:26Z Vincenttc 21 wikitext text/x-wiki iCal link in Outlook sharing-mail 7e15eadd3e97436bbbaee88c93ba570eeb9d515f 0 78 1830 1790 2023-11-28T20:03:09Z Vincenttc 21 Uitleg voor iCal link krijgen als ge geen MS account hebt wikitext text/x-wiki This guide will explain how your KU Leuven calendar and class schedule, which you can see on Toledo and kuloket, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Thunderbird, Outlook, Windows Calendar, etc.), following the steps below. === Synchronizing your class schedule to your KU Leuven calendar === [[File:Agenda Sync.png|thumb|235x235px|Image 1 - Where to find Agenda Sync]] Your first step will be to visit KU Loket via Toledo or by visiting [http://kuloket.be kuloket.be] . Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture in image 1. Now you will get an overview of your different agendas. Here you will need to select which one you wish to export. Next you will be presented a window with settings. The settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed further here. [[File:Agenda Synchronisation on.png|thumb|268x268px|Image 2 - Synchronisation status|alt=]] The only necessary step here is to make sure our '''synchronisation is on'''. We can check this at the top of the page. If the synchronisation is off, simply select restart sync at the top right. It's possible you will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. It should look as shown in image 2. === Importing your KU Leuven calendar into Thunderbird/Google Calendar/Outlook/... === [[File:Agenda in Outlook.png|thumb|209x209px|Image 3 - Calendar]] First, '''visit your personal student email'''. This can be done via Toledo or by visiting [https://owa.student.kuleuven.be owa.student.kuleuven.be]. This should bring you to your personal KU Leuven mailbox. On the left side of the page, you should see several icons (Mail, Calendar, People). Here you will need to '''select''' '''<nowiki/>'Calendar'''' (Image 3), which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are put on Toledo by your professors, should also be shown here now). If the calendar is still completely empty, make sure they're selected within 'My Calendars' on the left of your calendar overview. If it doesn't show up in this list, check if your agenda settings in KU Loket are set correctly according to image 2 and that you are looking at time period where classes are scheduled (not a holiday period). '''<nowiki/>'''[[File:Select Agenda.png|thumb|216x216px|Image 4 - Sharing your agenda]] Continuing in the top right corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a dropdown where you can select which agenda you would like to share (Image 4) (In this case we want to select UURROOSTER). Next you'll be shown a 'Sharing and permissions' window. In here simply enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'Can view all details' is selected from the dropdown menu (this should be done by default). Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email. In this email you want to copy the '''iCal link below the button 'Accept and view calendar'''' (see Image 5). Importing the iCal link to your chosen personal agenda can vary widely depending on which personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: [[File:ICal link in Outlook sharing-mail.png|alt=|thumb|261x261px|Image 5 - iCal link in Outlook sharing-mail]] * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 Almost all calendar services support importing iCal. If your chosen calendar service is not listed here, you can try searching the internet on how to import iCal for your service. [[Category:Tutorials]] 7b714f593e2f587f156a424165a98591bf19aad3 1831 1830 2023-11-28T20:20:58Z Vincenttc 21 wikitext text/x-wiki This guide will explain how your KU Leuven calendar and class schedule, which you can see on Toledo and kuloket, can be made more accessible even outside of Toledo. The procedure can be done by synchronizing the KU Leuven calendar with your personal agenda (e.g. Google Calendar, Thunderbird, Outlook, Windows Calendar, etc.), following the steps below. === Synchronizing your class schedule to your KU Leuven calendar === Your first step will be to visit KU Loket via Toledo or by visiting [http://kuloket.be kuloket.be] . Using the tabs on top of this page, go to '''Agenda''' and select '''Agenda Sync''' below, as shown in the picture in image 1. Now you will get an overview of your different agendas. Here you will need to select which one you wish to export. Next you will be presented a window with settings. The settings can be changed to your personal liking, but are not necessary to be edited for synchronizing your agenda so they will not be discussed further here. The only necessary step here is to make sure our '''synchronisation is on'''. We can check this at the top of the page. If the synchronisation is off, simply select restart sync at the top right. It's possible you will need to '''wait about 15 minutes''', to make sure KU Loket saved all the settings correctly. It should look as shown in image 2. <gallery mode=packed heights="160px"> File:Agenda Sync.png|Image 1 - Where to find Agenda Sync File:Agenda Synchronisation on.png|Image 2 - Synchronisation status </gallery> === Importing your KU Leuven calendar into Thunderbird/Google Calendar/Outlook/... === First, '''visit your personal student email'''. This can be done via Toledo or by visiting [https://owa.student.kuleuven.be owa.student.kuleuven.be]. This should bring you to your personal KU Leuven mailbox. On the left side of the page, you should see several icons (Mail, Calendar, People). Here you will need to '''select''' '''<nowiki/>'Calendar'''' (Image 3), which should bring you to a page with an overview of the KU Leuven calendar (future tasks and courses that are put on Toledo by your professors, should also be shown here now). If the calendar is still completely empty, make sure they're selected within 'My Calendars' on the left of your calendar overview. If it doesn't show up in this list, check if your agenda settings in KU Loket are set correctly according to image 2 and that you are looking at time period where classes are scheduled (not a holiday period). Continuing in the top right corner of the page, below the menu bar, there should be 2 buttons (share, print), as shown in the screenshot. You will need to select the '''share''' button. This will open a dropdown where you can select which agenda you would like to share (Image 4) (In this case we want to select UURROOSTER). Next you'll be shown a 'Sharing and permissions' window. In here simply enter a personal (non-KU Leuven) email address. When you have filled in the address, make sure 'Can view all details' is selected from the dropdown menu (this should be done by default). Now you will need to check the mailbox of the email address you entered before. Normally you should have received an email. In this email you want to copy the '''iCal link below the button 'Accept and view calendar'''' (see Image 5). Importing the iCal link to your chosen personal agenda can vary widely depending on which personal agenda you are using. We list a few links here on how to import iCal into the agenda for the most common services: * ''Google Calendar:'' https://support.google.com/calendar/answer/37648?hl=en * ''Outlook Calendar:'' https://www.howtogeek.com/661142/how-to-add-an-icalendar-link-to-your-outlook-calendar/ * ''Thunderbird:'' https://support.mozilla.org/en-US/questions/1105153 Almost all calendar services support importing iCal. If your chosen calendar service is not listed here, you can try searching the internet on how to import iCal for your service. <gallery mode=packed heights="160px" class="center"> File:Agenda in Outlook.png|Image 3 - Calendar File:Select Agenda.png|Image 4 - Sharing your agenda File:ICal link in Outlook sharing-mail.png|Image 5 - iCal link in Outlook sharing-mail </gallery> [[Category:Tutorials]] ca7ff55f2c470a085ab2ba628bdbc81c0ccc07e2 0 7 1832 1527 2024-04-11T15:24:31Z Timo 54 wikitext text/x-wiki ULYSSIS hosts its own IRC network. IRC stands for Internet Relay Chat, [https://en.wikipedia.org/wiki/Internet_Relay_Chat IRC on wikipedia]. It is a chat protocol that mainly focuses on group chat, but also allows for private chat. For any support questions, you are free to contact us via email on ulyssis@ulyssis.org, but if your questions are of a less sensitive nature and could benefit from a back-and-forth, it could be useful to contact us on IRC. Do keep in mind that you may have to wait until someone notices your question, which may take a while. If you don't have a question and just want to hang out in our chat, feel free to join! Keep in mind that our IRC network has been a social space for several generations, so you will find alumni and students from different walks of life there, not just ULYSSIS members and users. ==Web IRC client== If you won't regularly use our IRC or if you just want to check it out, you can use our web IRC client. You can find it at [https://webirc.ulyssis.org/ webirc.ulyssis.org]. Remember to leave your web IRC browser tab open while you wait for a response. ==IRC network details== Below are specific instructions for some clients, but if you are already familiar with IRC, here are the details you need to connect to our server. We highly recommend using SSL. Server: irc.ulyssis.org Port: 6668 (SSL) Channel: #ulyssis If <code>irc.ulyssis.org</code> is down, you can also try the other server in the same network, hosted at <code>irc2.ulyssis.org</code>. Both are connected to each other and you can use them interchangeably. It is advised to add it as a fallback in your IRC client. ==IRC clients== To use IRC, you'll need an IRC client. We advise the terminal based [https://irssi.org/ irssi] or [https://weechat.org/ weechat] for Linux and [https://hexchat.github.io/ hexchat] or [https://www.mirc.com/ mIRC] for Windows, but there are a lot of other free options. You can only receive messages over IRC while you're connected. Therefore, we advise you to run irssi or weechat in either a screen or a tmux session. With a ULYSSIS account, you can run screen or tmux on our shellservers, as they keep running 24/7 you can use them to keep track of your conversations. Screen and tmux are similar programs. Screen has been around for longer and is more tested, while tmux is more modern with new features and being easier to use for beginners. ===Using irssi on our shell servers=== ====Connect to the shellserver==== Use the ssh command in your Linux or OS X terminal, or use PuTTY to connect on windows. Extensive information on how to do so can be found on [[Accessing shell servers over SSH]]. ====Start irssi in a screen==== *When on the shellserver, enter <code>screen -U</code> to start a screen session, or <code>tmux</code> to start a tmux session. *Enter <code>irssi</code> to start irssi *Connect to the IRC server: <code>/connect -ssl irc.ulyssis.org 6668</code> *Connect to the public channel: <code>/join #ulyssis</code> ====Screen usage==== *To exit the screen: press Ctrl-A and press D ('detach') to return to the shellserver. *To reconnect: enter <code>screen -r</code> or <code>screen -DR</code> (the latter will create a new screen if it wasn't already made). ====Tmux usage==== *To exit the tmux session: press Ctrl-B and press D ('detach') to return to the shellserver. *To reconnect: enter <code>tmux attach</code> ====Help, I can't reconnect to my session!==== *Check if you are on the right shell server and didn't make a typing error. *If everything is correct, your screen may have been stopped by a crash or a reboot of our shellserver. You can check the [http://status.ulyssis.org status] section of our website for more information about possible downtimes. *Make sure you use the right program (<code>screen</code> if you started a screen session and <code>tmux</code> if you started a tmux session) ==Using ZNC== Alternatively, if you don't like using terminal-based clients, or just want to run your client locally, you can connect with our [https://znc.ulyssis.org/ ZNC server]. However, to use it, you'll need a ULYSSIS account. ZNC connects to our IRC server in your place (fill in the details at the beginning of this article). You can then connect to ZNC with a client of your choice, and it will send you the history you've missed while you were offline. Log in to our ZNC server. In your settings, create a new network. Fill in the basic details (server name, nickname, set <code>BindHost</code> to <code>0.0.0.0</code>). In the server field, fill in <code>irc.ulyssis.org +6668</code>. Add <code>#ulyssis</code> as a channel. You may want to increase the buffer count. Then save at the bottom of the page. In your IRC client, connect to the server <code>znc.ulyssis.org</code> on port 6666 (with SSL) and set <code>username/network:password</code> as password to the server. Replace <code>username</code> with your ULYSSIS username, <code>network</code> with the name of the network in your znc settings, and <code>password</code> with your ULYSSIS password. ==Using Bitlbee== With [https://www.bitlbee.org/main.php/news.r.html Bitlbee], you can connect to other services as if they were an IRC server. It is available at <code>bitlbee.ulyssis.org</code> on ports 7000 and 7001 (SSL). For documentation on how to use Bitlbee, we refer to the manual on its website. This service is only reachable from within the ULYSSIS and KU Leuven networks. [[Category:Shell]] [[Category:ULYSSIS Public Services]] e950c45b8907f041e599fa06d2682cfd687dd8aa 0 154 1834 1488 2024-04-29T12:24:37Z Timo 54 /* Identifying which files & folders use the most disk space */ typo wikitext text/x-wiki __TOC__ This page discusses what happens when you use more disk space than has been allotted to your account (your quota) and how to reduce your disk usage. You may have been pointed here through an automatic email notification you are running over your quota, or through our support. This page is also useful if you want to reduce your disk usage even if you're not using more than your quota. You can check your current disk usage as well as your quota on https://ucc.ulyssis.org/quota. This page first discusses what happens when you use more disk space than is available to your account type (so you therefore go over your quota). This is followed by a detailed manual on how to use the command line tool ''ncdu'' to look for the files and folders that may be causing trouble within your account. Finally, there's a list of examples of common causes for large disk space usage. == What happens when I go over my quota? == If you are using more disk space than the allowed quota for your account type for more than seven consecutive days (the so-called grace period), you will no longer be able to write any additional files or extend existing files. You will probably no longer be able to edit websites on your account or it might even stop working outright. If you haven't configured a forwarder for your <code>''username''@ulyssis.org</code> email address, you will lose emails sent to this address. The grace period of seven days is intended for you to have time to reduce your disk space. You will receive an email every day reminding you that you are using too much disk space. In order to prevent impact on other users in cases where disk usage within an account suddenly and substantially surges, an additional quota slightly higher than your normal quota is imposed, independent of any grace period. == Identifying which files & folders use the most disk space == It is not always easy to immediately identify what is taking up space on your account. Sadly, there are no dependable cross-platform tools to help with this. Instead, we will be using the command line tool ''ncdu'', which runs directly on one of our shell servers. You do not need to be proficient with command line interfaces in order to use this tool, the step-by-step manual below will guide you through the process. However, should you get stuck, do not hesitate to contact us at <code>ulyssis@ulyssis.org</code>. * Connect through SSH to one of the shell servers: https://docs.ulyssis.org/Accessing_shell_servers_over_SSH * Type in <code>ncdu</code> and press enter. You will then see that <code>ncdu</code> is scanning your account. * Once <code>ncdu</code> has finished scanning, it will display which files or folders located directly in your home directory are using the most disk space. When the filename starts with <code>/</code> it is a folder. The results are ordered by size, so it makes most sense to start with the top items. * You can select different files/folders using the '''up and down arrow keys''', navigate the directory structure using either the '''enter and backspace''' keys or the '''left and right''' arrows to move in and out of folders, quit ncdu by pressing '''q''' and delete a file or folder with '''d'''. Be careful to not delete files you still need as you will need to contact us in order to restore them from a backup. * You can check your progress on https://ucc.ulyssis.org/quota. The percentage and values displayed are always current and accurate, there is no delay.[[File:Disk usage ncdu.png|thumb|760x760px]] === Common sources of unnecessary disk usage === * Your ULYSSIS mailbox: Depending on your account settings, your ''@ulyssis.org'' email account may be used as a forwarder or an inbox. When set to ''Inbox'' on https://ucc.ulyssis.org/mail, email will be saved to the ''Maildir'' folder within your account. A substantial amount of email, especially with large attachments, may grow to quite a significant size. You can verify the contents of your mailbox easily by logging in on https://webmail.ulyssis.org using your ULYSSIS account credentials. You can then remove those emails that are no longer useful, and don't forget to empty the trash. To remove the entire mailbox, you can simply remove the Maildir folder from your account (using ncdu, Cyberduck, or another tool). To empty the trash manually, you can remove the ''Maildir/.Trash'' folder. If you no longer wish to use you mailbox, don't forget to change the configuration on https://ucc.ulyssis.org/mail to forward your messages, since you may receive relevant information about your account through this address. * Old websites: if you have older websites on your account that you are no longer using, it might be worth removing them in their entirety. If the deleted website uses a database (this will always be the case if your using WordPress, MediaWiki or another popular CMS), then you should also delete those through our control panel: https://ucc.ulyssis.org (either the MySQL or PostgreSQL sections). If this website had an associated (sub)domain, please send us an email to have it removed. Also keep in mind that old websites may pose a security risk, so it's never good to leave them lying about. * Unused images: in the case of many CMSes (WordPress, Drupal, ...), removing an image from a post will not delete it. For example, in the case of WordPress it will still be available through the Media Library. You can easily find these [https://wordpress.com/support/media/2/#unattached-files unattached files]. In order to reclaim the disk space used by the image, you will have to [https://wordpress.com/support/trash/#permanently-deleting-an-upload delete] it there as well. Similarly, MediaWiki offers a list of ''unused files'' as a special page available in the list of ''Special Pages''. Keep in mind that WordPress or MediaWiki might not always be aware an image or other file is used when it has not been added through its interfaces or through a third party plugin. * Large images: images and especially pictures are often several MBs in size and often have a large resolution. While this is great for editing and printing, such large sizes are not all that useful for inclusion in a webpage. They can make your site load slower and use more disk space without a significant increase in quality. You should therefore consider resizing images before uploading them or installing a plugin, module or extension that reduces their size on upload. However, make sure to watch out for plugins that keep the original image around as this will not reduce but increase your disk usage. For a tutorial on how to resize images, you can take a look at https://wordpress.com/support/media/image-optimization/. This tutorial is geared towards WordPress, but is also applicable in general. If you are using MediaWiki, we have written a plugin that reduces the size of various types of files. You can find more details on [[Setting up MediaWiki#Extensions|Setting up MediaWiki - Extensions]]. * Backups: ULYSSIS makes daily backups of all account data, including databases, and keeps them for at least a month. It is therefore not necessary to make automated backups of your own, for example with plugins such as [https://nl.wordpress.org/plugins/updraftplus/ Updraft] for WordPress. Although it is a good practice to make backups whenever you are making large changes to your site, it is not necessary to keep them after you have verified that your site works correctly. * Anything missing on this list? Feel free to contact us on <code>ulyssis@ulyssis.org</code> with your suggestions. [[Category:Files]] [[Category:Account]] 22029db43d09c101b7fe9436a6b19139d89b2233 1835 1834 2024-04-29T12:31:09Z Timo 54 /* Common sources of unnecessary disk usage */ wikitext text/x-wiki __TOC__ This page discusses what happens when you use more disk space than has been allotted to your account (your quota) and how to reduce your disk usage. You may have been pointed here through an automatic email notification you are running over your quota, or through our support. This page is also useful if you want to reduce your disk usage even if you're not using more than your quota. You can check your current disk usage as well as your quota on https://ucc.ulyssis.org/quota. This page first discusses what happens when you use more disk space than is available to your account type (so you therefore go over your quota). This is followed by a detailed manual on how to use the command line tool ''ncdu'' to look for the files and folders that may be causing trouble within your account. Finally, there's a list of examples of common causes for large disk space usage. == What happens when I go over my quota? == If you are using more disk space than the allowed quota for your account type for more than seven consecutive days (the so-called grace period), you will no longer be able to write any additional files or extend existing files. You will probably no longer be able to edit websites on your account or it might even stop working outright. If you haven't configured a forwarder for your <code>''username''@ulyssis.org</code> email address, you will lose emails sent to this address. The grace period of seven days is intended for you to have time to reduce your disk space. You will receive an email every day reminding you that you are using too much disk space. In order to prevent impact on other users in cases where disk usage within an account suddenly and substantially surges, an additional quota slightly higher than your normal quota is imposed, independent of any grace period. == Identifying which files & folders use the most disk space == It is not always easy to immediately identify what is taking up space on your account. Sadly, there are no dependable cross-platform tools to help with this. Instead, we will be using the command line tool ''ncdu'', which runs directly on one of our shell servers. You do not need to be proficient with command line interfaces in order to use this tool, the step-by-step manual below will guide you through the process. However, should you get stuck, do not hesitate to contact us at <code>ulyssis@ulyssis.org</code>. * Connect through SSH to one of the shell servers: https://docs.ulyssis.org/Accessing_shell_servers_over_SSH * Type in <code>ncdu</code> and press enter. You will then see that <code>ncdu</code> is scanning your account. * Once <code>ncdu</code> has finished scanning, it will display which files or folders located directly in your home directory are using the most disk space. When the filename starts with <code>/</code> it is a folder. The results are ordered by size, so it makes most sense to start with the top items. * You can select different files/folders using the '''up and down arrow keys''', navigate the directory structure using either the '''enter and backspace''' keys or the '''left and right''' arrows to move in and out of folders, quit ncdu by pressing '''q''' and delete a file or folder with '''d'''. Be careful to not delete files you still need as you will need to contact us in order to restore them from a backup. * You can check your progress on https://ucc.ulyssis.org/quota. The percentage and values displayed are always current and accurate, there is no delay.[[File:Disk usage ncdu.png|thumb|760x760px]] === Common sources of unnecessary disk usage === * Your ULYSSIS mailbox: Depending on your account settings, your ''@ulyssis.org'' email account may be used as a forwarder or an inbox. When set to ''Inbox'' on https://ucc.ulyssis.org/mail, email will be saved to the ''Maildir'' folder within your account. A substantial amount of email, especially with large attachments, may grow to quite a significant size. You can verify the contents of your mailbox easily by logging in on https://webmail.ulyssis.org using your ULYSSIS account credentials. You can then remove those emails that are no longer useful, and don't forget to empty the trash. To remove the entire mailbox, you can simply remove the Maildir folder from your account (using ncdu, [[Accessing your files#Using Cyberduck|Cyberduck]], or another tool). To empty the trash manually, you can remove the ''Maildir/.Trash'' folder. If you no longer wish to use you mailbox, don't forget to change the configuration on https://ucc.ulyssis.org/mail to forward your messages, since you may receive relevant information about your account through this address. * Old websites: if you have older websites on your account that you are no longer using, it might be worth removing them in their entirety. If the deleted website uses a database (this will always be the case if your using WordPress, MediaWiki or another popular CMS), then you should also delete those through our control panel: https://ucc.ulyssis.org (either the MySQL or PostgreSQL sections). If this website had an associated (sub)domain, please send us an email to have it removed. Also keep in mind that old websites may pose a security risk, so it's never good to leave them lying about. * Unused images: in the case of many CMSes (WordPress, Drupal, ...), removing an image from a post will not delete it. For example, in the case of WordPress it will still be available through the Media Library. You can easily find these [https://wordpress.com/support/media/2/#unattached-files unattached files]. In order to reclaim the disk space used by the image, you will have to [https://wordpress.com/support/trash/#permanently-deleting-an-upload delete] it there as well. Similarly, MediaWiki offers a list of ''unused files'' as a special page available in the list of ''Special Pages''. Keep in mind that WordPress or MediaWiki might not always be aware an image or other file is used when it has not been added through its interfaces or through a third party plugin. * Large images: images and especially pictures are often several MBs in size and often have a large resolution. While this is great for editing and printing, such large sizes are not all that useful for inclusion in a webpage. They can make your site load slower and use more disk space without a significant increase in quality. You should therefore consider resizing images before uploading them or installing a plugin, module or extension that reduces their size on upload. However, make sure to watch out for plugins that keep the original image around as this will not reduce but increase your disk usage. For a tutorial on how to resize images, you can take a look at https://wordpress.com/support/media/image-optimization/. This tutorial is geared towards WordPress, but is also applicable in general. If you are using MediaWiki, we have written a plugin that reduces the size of various types of files. You can find more details on [[Setting up MediaWiki#Extensions|Setting up MediaWiki - Extensions]]. * Backups: ULYSSIS makes daily backups of all account data, including databases, and keeps them for at least a month. It is therefore not necessary to make automated backups of your own, for example with plugins such as [https://nl.wordpress.org/plugins/updraftplus/ Updraft] for WordPress. Although it is a good practice to make backups whenever you are making large changes to your site, it is not necessary to keep them after you have verified that your site works correctly. * Anything missing on this list? Feel free to contact us on <code>ulyssis@ulyssis.org</code> with your suggestions. [[Category:Files]] [[Category:Account]] 16f52a99d1ecc5d69b009dced7d7e8e40af842d9 0 104 1836 1740 2024-06-06T22:13:07Z Arnodb 49 wikitext text/x-wiki PHP code is run with PHP-FPM as your ULYSSIS user. This means you can tighten up you website's security by denying other users the permission to read your PHP files. However, due to the way the Apache webserver works, it must be able to determine the existence of your PHP files. Non-PHP files in your www directory must remain readable by other users, because Apache reads these as it's own user. === Recommended permissions === * www directory (and other directories from where websites are served), including subdirectories: <code>0705/drwx---r-x</code> * Static website files (css, images, html, ...): <code>0604/-rw----r--</code> * Configuration files containing secrets/passwords: <code>0600/-rw-------</code> * Other directories and files that are not part of a website: <code>0600/-rw-------</code> or <code>0700/-rwx------</code> === Securing configuration files containing secrets/passwords === If you have any files that you want to protect from the prying eyes of other users, such as API keys, first you need to ensure that the directory containing your important file, is not writeable by other users. This is easiest to do by creating a new directory, dedicated to housing your protected files. For this you can run <code>mkdir safe</code>, followed by <code>chmod 700 safe</code> and finally moving the file into the safe directory. Then you can make your file readable and writeable solely by you. To do this you run <code>chmod 600 safe/name_of_file</code>. In Cyberduck, you can do this by making a new directory, right-clicking on it, clicking on "Info", clicking on the "Permissions" tab, and changing the permissions so that for "Owner", all the boxes ("Read", "Write" and "Execute") are ticked and for "Group" and "Other", no boxes should be ticked. Next you can move the protected file into the safe directory. Once you go into the safe directory, you can then finish by right-clicking on the secret file, clicking on "Info", clicking on the "Permissions" tab, and changing the permissions according to the following screenshots: [[File:Config-php-dropdown.png]] [[File:Config-php-permissions.png]] === Securing database login info === Suppose you have a file called <code>config.php</code>, containing login information for your database. To secure this information, you can make it readable and writeable by only you, and nobody else using <code>chmod 600 config.php</code>. In Cyberduck, you can do this by right-clicking on the config file, clicking on "Info", clicking on the "Permissions" tab, and changing the permissions according to the following screenshots: [[File:Config-php-dropdown.png]] [[File:Config-php-permissions.png]] === Securing uploads directory === Also, if there are directories that you made writeable by others, e.g. an uploads folder, this is no longer necessary. If this directory is called <code>uploads</code>, you can remove write rights for others with <code>chmod go-w uploads</code>. In Cyberduck, you can do this by right-clicking on the config file, clicking on "Info", clicking on the "Permissions" tab, and changing the permissions according to the following screenshots: [[File:Uploads-dropdown.png]] [[File:Uploads-permissions.png]] [[Category:Files]] [[Category:Security & anti-spam]] bb523f7c089a21134d44d55f76c8b9adc68188e4 1837 1836 2024-06-07T09:26:24Z Arnodb 49 wikitext text/x-wiki PHP code is run with PHP-FPM as your ULYSSIS user. This means you can tighten up you website's security by denying other users the permission to read your PHP files. However, due to the way the Apache webserver works, it must be able to determine the existence of your PHP files. Non-PHP files in your www directory must remain readable by other users, because Apache reads these as it's own user. === Recommended permissions === * www directory (and other directories from where websites are served), including subdirectories: <code>0705/drwx---r-x</code> * Static website files (css, images, html, ...): <code>0604/-rw----r--</code> * Configuration files containing secrets/passwords: <code>0600/-rw-------</code> * Other directories and files that are not part of a website: <code>0600/-rw-------</code> or <code>0700/-rwx------</code> === Securing database login info === Suppose you have a file called <code>config.php</code>, containing login information for your database. To secure this information, you can make it readable and writeable by only you, and nobody else using <code>chmod 600 config.php</code>. In Cyberduck, you can do this by right-clicking on the config file, clicking on "Info", clicking on the "Permissions" tab, and changing the permissions according to the following screenshots: [[File:Config-php-dropdown.png]] [[File:Config-php-permissions.png]] === Securing uploads directory === Also, if there are directories that you made writeable by others, e.g. an uploads folder, this is no longer necessary. If this directory is called <code>uploads</code>, you can remove write rights for others with <code>chmod go-w uploads</code>. In Cyberduck, you can do this by right-clicking on the config file, clicking on "Info", clicking on the "Permissions" tab, and changing the permissions according to the following screenshots: [[File:Uploads-dropdown.png]] [[File:Uploads-permissions.png]] [[Category:Files]] [[Category:Security & anti-spam]] === Home directory security === For the permissions mentioned above to fully work, it is important for the parent directories to have the correct permissions. Our system already gives your home directory the correct permissions for this. Other users cannot read your files, or even find out what files exist. Even in case you mistakingly give everyone every permission to a file, only you can access it, because others do not have permission to go into your home directory. {{notice|Important| If you any secret files into your www directory, it may be publicly accessible via your website! Therefore, please make sure any files you want to protect are not in the www directory. }} 78011db44b93e7b122d8d833dafafe754d27b4fc 1838 1837 2024-06-07T09:27:30Z Arnodb 49 /* Home directory security */ wikitext text/x-wiki PHP code is run with PHP-FPM as your ULYSSIS user. This means you can tighten up you website's security by denying other users the permission to read your PHP files. However, due to the way the Apache webserver works, it must be able to determine the existence of your PHP files. Non-PHP files in your www directory must remain readable by other users, because Apache reads these as it's own user. === Recommended permissions === * www directory (and other directories from where websites are served), including subdirectories: <code>0705/drwx---r-x</code> * Static website files (css, images, html, ...): <code>0604/-rw----r--</code> * Configuration files containing secrets/passwords: <code>0600/-rw-------</code> * Other directories and files that are not part of a website: <code>0600/-rw-------</code> or <code>0700/-rwx------</code> === Securing database login info === Suppose you have a file called <code>config.php</code>, containing login information for your database. To secure this information, you can make it readable and writeable by only you, and nobody else using <code>chmod 600 config.php</code>. In Cyberduck, you can do this by right-clicking on the config file, clicking on "Info", clicking on the "Permissions" tab, and changing the permissions according to the following screenshots: [[File:Config-php-dropdown.png]] [[File:Config-php-permissions.png]] === Securing uploads directory === Also, if there are directories that you made writeable by others, e.g. an uploads folder, this is no longer necessary. If this directory is called <code>uploads</code>, you can remove write rights for others with <code>chmod go-w uploads</code>. In Cyberduck, you can do this by right-clicking on the config file, clicking on "Info", clicking on the "Permissions" tab, and changing the permissions according to the following screenshots: [[File:Uploads-dropdown.png]] [[File:Uploads-permissions.png]] [[Category:Files]] [[Category:Security & anti-spam]] === Home directory security === For the permissions mentioned above to fully work, it is important for the parent directories to have the correct permissions. Our system already gives your home directory the correct permissions for this. Other users cannot read your files, or even find out what files exist. Even in case you mistakingly give everyone every permission to one of your files, only you can access it, because others do not have permission to go into your home directory. {{notice|Important| If you any secret files into your www directory, it may be publicly accessible via your website! Therefore, please make sure any files you want to protect are not in the www directory. }} 924f88b61491f06891c240dae87bf8803a89de91 1839 1838 2024-06-07T21:34:07Z Arnodb 49 /* Home directory security */ wikitext text/x-wiki PHP code is run with PHP-FPM as your ULYSSIS user. This means you can tighten up you website's security by denying other users the permission to read your PHP files. However, due to the way the Apache webserver works, it must be able to determine the existence of your PHP files. Non-PHP files in your www directory must remain readable by other users, because Apache reads these as it's own user. === Recommended permissions === * www directory (and other directories from where websites are served), including subdirectories: <code>0705/drwx---r-x</code> * Static website files (css, images, html, ...): <code>0604/-rw----r--</code> * Configuration files containing secrets/passwords: <code>0600/-rw-------</code> * Other directories and files that are not part of a website: <code>0600/-rw-------</code> or <code>0700/-rwx------</code> === Securing database login info === Suppose you have a file called <code>config.php</code>, containing login information for your database. To secure this information, you can make it readable and writeable by only you, and nobody else using <code>chmod 600 config.php</code>. In Cyberduck, you can do this by right-clicking on the config file, clicking on "Info", clicking on the "Permissions" tab, and changing the permissions according to the following screenshots: [[File:Config-php-dropdown.png]] [[File:Config-php-permissions.png]] === Securing uploads directory === Also, if there are directories that you made writeable by others, e.g. an uploads folder, this is no longer necessary. If this directory is called <code>uploads</code>, you can remove write rights for others with <code>chmod go-w uploads</code>. In Cyberduck, you can do this by right-clicking on the config file, clicking on "Info", clicking on the "Permissions" tab, and changing the permissions according to the following screenshots: [[File:Uploads-dropdown.png]] [[File:Uploads-permissions.png]] [[Category:Files]] [[Category:Security & anti-spam]] === Home directory security === For the permissions mentioned above to fully work, it is important for the parent directories to have the correct permissions. Our system already gives your home directory the correct permissions for this. Other users cannot read your files, or even find out what files exist. Even in case you mistakingly give everyone every permission to one of your files, only you can access it, because others do not have permission to go into your home directory. {{notice|Important| If you have any secret files in your www directory, it may be publicly accessible via your website! Therefore, please make sure any files you want to protect are not in the www directory. }} 76b31f5e59376aa5cb17152630bcafb7734dec42 1840 1839 2024-06-09T09:10:55Z Arnodb 49 wikitext text/x-wiki PHP code is run with PHP-FPM as your ULYSSIS user. This means you can tighten up you website's security by denying other users the permission to read your PHP files. However, due to the way the Apache webserver works, it must be able to determine the existence of your PHP files. Non-PHP files in your www directory must remain readable by other users, because Apache reads these as it's own user. === Recommended permissions === * www directory (and other directories from where websites are served), including subdirectories: <code>0705/drwx---r-x</code> * Static website files (css, images, html, ...): <code>0604/-rw----r--</code> * Configuration files containing secrets/passwords: <code>0600/-rw-------</code> * Other directories and files that are not part of a website: <code>0600/-rw-------</code> or <code>0700/-rwx------</code> === Home directory security === For the permissions mentioned above to fully work, it is important for the parent directories to have the correct permissions. Our system already gives your home directory the correct permissions for this. Other users cannot read your files, or even find out what files exist. Even in case you mistakingly give everyone every permission to one of your files, only you can access it, because others do not have permission to go into your home directory. {{notice|Important| If you have any secret files in your www directory, it may be publicly accessible via your website! Therefore, please make sure any files you want to protect are not in the www directory. }} === Securing database login info === Suppose you have a file called <code>config.php</code>, containing login information for your database. To secure this information, you can make it readable and writeable by only you, and nobody else using <code>chmod 600 config.php</code>. In Cyberduck, you can do this by right-clicking on the config file, clicking on "Info", clicking on the "Permissions" tab, and changing the permissions according to the following screenshots: [[File:Config-php-dropdown.png]] [[File:Config-php-permissions.png]] === Securing uploads directory === Also, if there are directories that you made writeable by others, e.g. an uploads folder, this is no longer necessary. If this directory is called <code>uploads</code>, you can remove write rights for others with <code>chmod go-w uploads</code>. In Cyberduck, you can do this by right-clicking on the config file, clicking on "Info", clicking on the "Permissions" tab, and changing the permissions according to the following screenshots: [[File:Uploads-dropdown.png]] [[File:Uploads-permissions.png]] [[Category:Files]] [[Category:Security & anti-spam]] 6a7b3a91523bc30b9695517633f870a29afda16a 1841 1840 2024-06-09T09:12:16Z Arnodb 49 wikitext text/x-wiki PHP code is run with PHP-FPM as your ULYSSIS user. This means you can tighten up you website's security by denying other users the permission to read your PHP files. However, due to the way the Apache webserver works, it must be able to determine the existence of your PHP files. Non-PHP files in your www directory must remain readable by other users, because Apache reads these as its own user. === Recommended permissions === * www directory (and other directories from where websites are served), including subdirectories: <code>0705/drwx---r-x</code> * Static website files (css, images, html, ...): <code>0604/-rw----r--</code> * Configuration files containing secrets/passwords: <code>0600/-rw-------</code> * Other directories and files that are not part of a website: <code>0600/-rw-------</code> or <code>0700/-rwx------</code> === Home directory security === For the permissions mentioned above to fully work, it is important for the parent directories to have the correct permissions. Our system already gives your home directory the correct permissions for this. Other users cannot read your files, or even find out what files exist. Even in case you mistakingly give everyone every permission to one of your files, only you can access it, because others do not have permission to go into your home directory. {{notice|Important| If you have any secret files in your www directory, it may be publicly accessible via your website! Therefore, please make sure any files you want to protect are not in the www directory. }} === Securing database login info === Suppose you have a file called <code>config.php</code>, containing login information for your database. To secure this information, you can make it readable and writeable by only you, and nobody else using <code>chmod 600 config.php</code>. In Cyberduck, you can do this by right-clicking on the config file, clicking on "Info", clicking on the "Permissions" tab, and changing the permissions according to the following screenshots: [[File:Config-php-dropdown.png]] [[File:Config-php-permissions.png]] === Securing uploads directory === Also, if there are directories that you made writeable by others, e.g. an uploads folder, this is no longer necessary. If this directory is called <code>uploads</code>, you can remove write rights for others with <code>chmod go-w uploads</code>. In Cyberduck, you can do this by right-clicking on the config file, clicking on "Info", clicking on the "Permissions" tab, and changing the permissions according to the following screenshots: [[File:Uploads-dropdown.png]] [[File:Uploads-permissions.png]] [[Category:Files]] [[Category:Security & anti-spam]] 76d6f2ef69900af9476d1a7042d5c85a4b4a48fe 1842 1841 2024-06-11T00:47:00Z Bert 8 wikitext text/x-wiki PHP code is run with PHP-FPM as your ULYSSIS user. This means you can tighten up you website's security by denying other users the permission to read your PHP files. However, due to the way the Apache webserver works, it must be able to determine the existence of your PHP files. Non-PHP files in your www directory must remain readable by other users, because Apache reads these as its own user. === Recommended permissions === * www directory (and other directories from where websites are served), including subdirectories: <code>0705/drwx---r-x</code> * Static website files (css, images, html, ...): <code>0604/-rw----r--</code> * Configuration files containing secrets/passwords: <code>0600/-rw-------</code> * Other directories and files that are not part of a website: <code>0600/-rw-------</code> or <code>0700/-rwx------</code> === Home directory security === For the permissions mentioned above to fully work, it is important for the parent directories to have the correct permissions. Our system already gives your home directory the correct permissions for this. Other users cannot read your files, or even find out what files exist. Even in case you mistakingly give everyone every permission to one of your files, only you can access it, because others do not have permission to go into your home directory. {{notice|Important|If you have any secret files in your www directory, it may be publicly accessible via your website! Therefore, please make sure any files you want to protect are not in the www directory.}} === Securing database login info === Suppose you have a file called <code>config.php</code>, containing login information for your database. To secure this information, you can make it readable and writeable by only you, and nobody else using <code>chmod 600 config.php</code>. In Cyberduck, you can do this by right-clicking on the config file, clicking on "Info", clicking on the "Permissions" tab, and changing the permissions according to the following screenshots: [[File:Config-php-dropdown.png]] [[File:Config-php-permissions.png]] === Securing uploads directory === Also, if there are directories that you made writeable by others, e.g. an uploads folder, this is no longer necessary. If this directory is called <code>uploads</code>, you can remove write rights for others with <code>chmod go-w uploads</code>. In Cyberduck, you can do this by right-clicking on the config file, clicking on "Info", clicking on the "Permissions" tab, and changing the permissions according to the following screenshots: [[File:Uploads-dropdown.png]] [[File:Uploads-permissions.png]] [[Category:Files]] [[Category:Security & anti-spam]] 397a7d63fb8d6da9945d73bcbee23f1e2c266555 1843 1842 2024-06-11T07:13:32Z Arnodb 49 wikitext text/x-wiki PHP code is run with PHP-FPM as your ULYSSIS user. This means you can tighten up you website's security by denying other users the permission to read your PHP files. However, due to the way the Apache webserver works, it must be able to determine the existence of your PHP files. Non-PHP files in your www directory must remain readable by others, because Apache reads these as its own user. === Recommended permissions === * www directory (and other directories from where websites are served), including subdirectories: <code>0705/drwx---r-x</code> * Static website files (css, images, html, ...): <code>0604/-rw----r--</code> * Configuration files containing secrets/passwords: <code>0600/-rw-------</code> * Other directories and files that are not part of a website: <code>0600/-rw-------</code> or <code>0700/-rwx------</code> === Home directory security === For the permissions mentioned above to fully work, it is important for the parent directories to have the correct permissions. Our system already gives your home directory the correct permissions for this. Other users cannot read your files, or even find out what files exist. Even in case you mistakingly give everyone every permission to one of your files, only you can access it, because others do not have permission to go into your home directory. {{notice|Important|If you have any secret files in your www directory, it may be publicly accessible via your website! Therefore, please make sure any files you want to protect are not in the www directory.}} === Securing database login info === Suppose you have a file called <code>config.php</code>, containing login information for your database. To secure this information, you can make it readable and writeable by only you, and nobody else using <code>chmod 600 config.php</code>. In Cyberduck, you can do this by right-clicking on the config file, clicking on "Info", clicking on the "Permissions" tab, and changing the permissions according to the following screenshots: [[File:Config-php-dropdown.png]] [[File:Config-php-permissions.png]] === Securing uploads directory === Also, if there are directories that you made writeable by others, e.g. an uploads folder, this is no longer necessary. If this directory is called <code>uploads</code>, you can remove write rights for others with <code>chmod go-w uploads</code>. In Cyberduck, you can do this by right-clicking on the config file, clicking on "Info", clicking on the "Permissions" tab, and changing the permissions according to the following screenshots: [[File:Uploads-dropdown.png]] [[File:Uploads-permissions.png]] [[Category:Files]] [[Category:Security & anti-spam]] e7e8871de0396d68f5828be50d2b553ccfcc205e 0 265 1844 2024-07-07T15:58:42Z Pcy 37 Created page with "This page lists the changes to the webservers of ULYSSIS in the summer of 2024, and how you can prepare for it. If any of these instructions are not clear to you, or if you have some more questions about the changes, '''don't hesitate to e-mail us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]'''. == When are the changes planned? == These changes are planned in the weekend of <TBC>. == What will change? == We will upgrade the Ubuntu release on our servers from 2..." wikitext text/x-wiki This page lists the changes to the webservers of ULYSSIS in the summer of 2024, and how you can prepare for it. If any of these instructions are not clear to you, or if you have some more questions about the changes, '''don't hesitate to e-mail us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]'''. == When are the changes planned? == These changes are planned in the weekend of <TBC>. == What will change? == We will upgrade the Ubuntu release on our servers from 22.04 LTS to 24.04 LTS. This will include newer version of many services. An overview of the most important version changes can be found below. For other services/packages, you can always use the [https://packages.ubuntu.com/ Ubuntu Package Search]. The distribution name for Ubuntu 24.04 LTS is "noble". * PHP will be updated from 8.1 to 8.3 * PostgreSQL will be updated from 14 to 16.2 * MariaDB (MySQL) will be updated from 10.6.7 to 10.11.8 * Python will be updated from 3.10 to 3.12 Furthermore, many services (such as Apache2) are migrating their regex engine from PCRE to PCRE2. You can find a list of incompatibilities [https://stackoverflow.com/questions/70273084/regex-differences-between-pcre-and-pcre2 here]. If you host your own PHP website, you might want to check out these guides: * [https://www.php.net/manual/en/migration82.php Migrating from PHP 8.1.x to PHP 8.2.x] * [https://www.php.net/manual/en/migration83.php Migrating from PHP 8.2.x to PHP 8.3.x] Note that any existing Python virtual environments in use will need to be recreated in order to function properly. 595620b3ffce90d5f8ddeac9f670bc6b2c0baa54 1845 1844 2024-08-05T20:55:53Z Pcy 37 /* When are the changes planned? */ wikitext text/x-wiki This page lists the changes to the webservers of ULYSSIS in the summer of 2024, and how you can prepare for it. If any of these instructions are not clear to you, or if you have some more questions about the changes, '''don't hesitate to e-mail us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]'''. == When are the changes planned? == These changes are planned to be applied on 8 and 9 september, 2024. == What will change? == We will upgrade the Ubuntu release on our servers from 22.04 LTS to 24.04 LTS. This will include newer version of many services. An overview of the most important version changes can be found below. For other services/packages, you can always use the [https://packages.ubuntu.com/ Ubuntu Package Search]. The distribution name for Ubuntu 24.04 LTS is "noble". * PHP will be updated from 8.1 to 8.3 * PostgreSQL will be updated from 14 to 16.2 * MariaDB (MySQL) will be updated from 10.6.7 to 10.11.8 * Python will be updated from 3.10 to 3.12 Furthermore, many services (such as Apache2) are migrating their regex engine from PCRE to PCRE2. You can find a list of incompatibilities [https://stackoverflow.com/questions/70273084/regex-differences-between-pcre-and-pcre2 here]. If you host your own PHP website, you might want to check out these guides: * [https://www.php.net/manual/en/migration82.php Migrating from PHP 8.1.x to PHP 8.2.x] * [https://www.php.net/manual/en/migration83.php Migrating from PHP 8.2.x to PHP 8.3.x] Note that any existing Python virtual environments in use will need to be recreated in order to function properly. 867d1a2f62c28f3bf3e59d3e115810e677898564 1846 1845 2024-08-05T20:56:05Z Pcy 37 /* When are the changes planned? */ wikitext text/x-wiki This page lists the changes to the webservers of ULYSSIS in the summer of 2024, and how you can prepare for it. If any of these instructions are not clear to you, or if you have some more questions about the changes, '''don't hesitate to e-mail us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]'''. == When are the changes planned? == These changes are planned to be applied on Sunday 8 and Monday 9 september, 2024. == What will change? == We will upgrade the Ubuntu release on our servers from 22.04 LTS to 24.04 LTS. This will include newer version of many services. An overview of the most important version changes can be found below. For other services/packages, you can always use the [https://packages.ubuntu.com/ Ubuntu Package Search]. The distribution name for Ubuntu 24.04 LTS is "noble". * PHP will be updated from 8.1 to 8.3 * PostgreSQL will be updated from 14 to 16.2 * MariaDB (MySQL) will be updated from 10.6.7 to 10.11.8 * Python will be updated from 3.10 to 3.12 Furthermore, many services (such as Apache2) are migrating their regex engine from PCRE to PCRE2. You can find a list of incompatibilities [https://stackoverflow.com/questions/70273084/regex-differences-between-pcre-and-pcre2 here]. If you host your own PHP website, you might want to check out these guides: * [https://www.php.net/manual/en/migration82.php Migrating from PHP 8.1.x to PHP 8.2.x] * [https://www.php.net/manual/en/migration83.php Migrating from PHP 8.2.x to PHP 8.3.x] Note that any existing Python virtual environments in use will need to be recreated in order to function properly. 7d9634d72bd72e817de19477f36e5d57cbf1ef20 0 152 1848 1566 2024-08-28T16:42:51Z Bert 8 wikitext text/x-wiki It's definitely possible to run multiple websites on a single ULYSSIS account. So you do not need to buy a new account to run a secondary website on. Very often this is used for running a wiki installation together with a WordPress installation, but in fact you can combine almost any CMS (like WordPress, Drupal or Joomla) or software. This is also called 'running multiple instances'. As an example: You have a primary WordPress installation on youroganization.be, but beside that you would also like a blog that runs on Joomla. By following this guide, you can have a main WordPress installation while also having a separate blog on blog.yourorganization.be . The "blog." of this URL is also called a subdomain. If you would like more information regarding subdomains and what they can be used for, you can find more details on [https://en.wikipedia.org/wiki/Subdomain Wikipedia]. So to run multiple installations on your website, you will need to follow a few steps: First of all, you will need access to one of our shell servers. If you need more information on how to do this, you can visit the following page: [[Accessing your files]]. Continuing, we need to make a new directory in your home folder, preferably next to the <code>www</code> folder where you installed the software that is running on your main website. It is also possible to install the new software to a new directory inside your <code>www</code>, but we do not recommend this for most users because it will be very confusing for later maintenance and updates. We also recommend to name the new directory to something obvious (e.g. a directory named <code>wiki</code> for a wiki installation), this will help future maintainers of your account. Next, you will need to send us an email at ulyssis@ulyssis.org to connect the newly made directory to your subdomain. The information you need to send us is: the '''path''' to the new directory (often this will look something like this: /home/user/<your_username>/<name_of_the_directory>), and the '''subdomain''' you want this website to run on (e.g. blog.yourorganization.be). When you receive a reply back from us that everything is in order, you will need to follow the steps from https://docs.ulyssis.org/Setting_up_WordPress, https://docs.ulyssis.org/Setting_up_Joomla, https://docs.ulyssis.org/Setting_up_Drupal or something else. This depends on what software you are planning to install on the new subdomain. While running the setup for your software, make sure to you install it to the '''right directory''', and adjust the configurations where needed. If you have made edits to the .htaccess file for your website in the past, be cautious as it may interfere with your new installation on the subdomain. When everything is complete, you should now have another website running at e.g. <chosen_subdomain>.yourorganization.be . If you have further questions or problems regarding the guide above, do not hesitate to contact us. 5f50c18790ae92859bd6c4cca7a692829b2b8a46 0 16 1849 881 2024-08-31T12:32:12Z Timo 54 /* Text editors */ wikitext text/x-wiki Once you've connected, you can use these commands to use the ULYSSIS shell. First of all, whenever you need to type a longer command or filename, try the <code>TAB</code> key as it will try to complete the name of the command or file you are typing. Pressing <code>TAB</code> twice will show a list of possible completions. A more extensive document on this can be found at http://info.ee.surrey.ac.uk/Teaching/Unix/. ==Basic file managment== cd directoryname Change directory. Works the same as under MS-DOS. cd without argument changes to your home directory (like My Documents in windows). Go to the parent directory with <code>cd ..</code> ls List the contents of the current directory. Many different formats are available, a common one is <code>ls -al</code>. To accomodate MS-DOS/Windows users, <code>dir</code> is an alias (synonym) for <code>ls -alF</code>, which gives output similar to the <code>dir</code> command in MS-DOS/Windows. cp inputfile targetfile Copy inputfile to targetfile. Additional arguments (e.g. -r or -v are explained in the man-page.) mv inputfile targetfile Move inputfile to targetfile. Additional arguments (e.g. -i or -v are explained in the man-page.) This is the way to rename a file. Note that you cannot use a construction like mv *.htm *.html to add an ``l'' to a bunch of files. A small shell script can provide a way to do this: <code>for i in *.htm; do mv i; done</code> rm filename Remove filename. Additional arguments (e.g. -r or -v are explained in the man-page.) Note: there is no undelete-alike function in most unices. mkdir dirname Creates a directory called dirname. rmdir dirname Removes an empty directory. Use rm -r to delete a directory and recursively everything in it. Add -f to disable any prompts (dangerous!). ==Getting help== man command-name Displays manual pages, if available. E.g. man ls. Use 'q' to exit. Relatives: apropos, help. apropos word Searches through headers of all man pages. help command-name Displays help about command-name. Only for internal bash-functions. bash The Bourne Again SHell. Widely used successor of sh, the Bourne shell. This is the program you're working under after you open a ssh-session (you don't have to start it to use it). Bash interprets your commands, and executes them. Tab-completion, * and ? expansions, etc are all bash functions. man bash will give you tons of info about it. Alternatives : tcsh, zsh, rc ==Text editors== It's easier to use a text editor on a server, than editing your file locally and uploading that file. nano Probably the easiest text editor. Should be self-explanatory. The symbol ^ is used for the ctrl key and M- stands for alt. joe Another easy text editor. Press Ctrl+C to quit. vim Probably the best text editor. Start editing by pressing i. Stop editing by pressing the escape key. Save and quit with :wq. Quit without saving with :q!. ==Utilities== df Displays info about the free diskspace on the system. df . will give info about the filesystem where the current directory resides. The output becomes a bit more readable with the -h switch. du Displays info about the diskusage in the current directory (and its subdirectories. A common parameter is -s , equivalent to -summarize , to summarize the disk-usage (without the per-subdir totals). quota Displays info about your diskusage, and your disk quota. Quota are limits on diskusage, imposed by the system administrator. The system will warn you if you exceed these limits. ps Displays info about processes. Various options possible, for example ps auxf gives info on all processes, including process owner, memory usage, and parent-child indication. htop Displays top CPU processes. Use it to see what gets most cpu power at the moment. Don't leave top open for a long time, since it eats cpu time itself. (quit with 'q'). [[Category:Shell]] e3b9d1395c187fdfbfd57348086cb772c7437fe5 1850 1849 2024-08-31T12:35:31Z Timo 54 wikitext text/x-wiki Once you've connected, you can use these commands to use the ULYSSIS shell. First of all, whenever you need to type a longer command or filename, try the <code>TAB</code> key as it will try to complete the name of the command or file you are typing. Pressing <code>TAB</code> twice will show a list of possible completions. A more extensive document on this can be found at https://info-ee.surrey.ac.uk/Teaching/Unix/index.html. ==Basic file managment== cd directoryname Change directory. Works the same as under MS-DOS. cd without argument changes to your home directory (like My Documents in windows). Go to the parent directory with <code>cd ..</code> ls List the contents of the current directory. Many different formats are available, a common one is <code>ls -al</code>. To accomodate MS-DOS/Windows users, <code>dir</code> is an alias (synonym) for <code>ls -alF</code>, which gives output similar to the <code>dir</code> command in MS-DOS/Windows. cp inputfile targetfile Copy inputfile to targetfile. Additional arguments (e.g. -r or -v are explained in the man-page.) mv inputfile targetfile Move inputfile to targetfile. Additional arguments (e.g. -i or -v are explained in the man-page.) This is the way to rename a file. Note that you cannot use a construction like mv *.htm *.html to add an ``l'' to a bunch of files. A small shell script can provide a way to do this: <code>for i in *.htm; do mv i; done</code> rm filename Remove filename. Additional arguments (e.g. -r or -v are explained in the man-page.) Note: there is no undelete-alike function in most unices. mkdir dirname Creates a directory called dirname. rmdir dirname Removes an empty directory. Use rm -r to delete a directory and recursively everything in it. Add -f to disable any prompts (dangerous!). ==Getting help== man command-name Displays manual pages, if available. E.g. man ls. Use 'q' to exit. Relatives: apropos, help. apropos word Searches through headers of all man pages. help command-name Displays help about command-name. Only for internal bash-functions. bash The Bourne Again SHell. Widely used successor of sh, the Bourne shell. This is the program you're working under after you open a ssh-session (you don't have to start it to use it). Bash interprets your commands, and executes them. Tab-completion, * and ? expansions, etc are all bash functions. man bash will give you tons of info about it. Alternatives : tcsh, zsh, rc ==Text editors== It's easier to use a text editor on a server, than editing your file locally and uploading that file. nano Probably the easiest text editor. Should be self-explanatory. The symbol ^ is used for the ctrl key and M- stands for alt. joe Another easy text editor. Press Ctrl+C to quit. vim Probably the best text editor. Start editing by pressing i. Stop editing by pressing the escape key. Save and quit with :wq. Quit without saving with :q!. ==Utilities== df Displays info about the free diskspace on the system. df . will give info about the filesystem where the current directory resides. The output becomes a bit more readable with the -h switch. du Displays info about the diskusage in the current directory (and its subdirectories. A common parameter is -s , equivalent to -summarize , to summarize the disk-usage (without the per-subdir totals). quota Displays info about your diskusage, and your disk quota. Quota are limits on diskusage, imposed by the system administrator. The system will warn you if you exceed these limits. ps Displays info about processes. Various options possible, for example ps auxf gives info on all processes, including process owner, memory usage, and parent-child indication. htop Displays top CPU processes. Use it to see what gets most cpu power at the moment. Don't leave top open for a long time, since it eats cpu time itself. (quit with 'q'). [[Category:Shell]] c3be4d42fea172e2a6a416e7d9d4412a8aa7562b 1851 1850 2024-08-31T12:37:33Z Timo 54 wikitext text/x-wiki Once you've connected, you can use these commands to use the ULYSSIS shell. First of all, whenever you need to type a longer command or filename, try the <code>TAB</code> key as it will try to complete the name of the command or file you are typing. Pressing <code>TAB</code> twice will show a list of possible completions. A more extensive document on this can be found at https://info-ee.surrey.ac.uk/Teaching/Unix/. ==Basic file managment== cd directoryname Change directory. Works the same as under MS-DOS. cd without argument changes to your home directory (like My Documents in windows). Go to the parent directory with <code>cd ..</code> ls List the contents of the current directory. Many different formats are available, a common one is <code>ls -al</code>. To accomodate MS-DOS/Windows users, <code>dir</code> is an alias (synonym) for <code>ls -alF</code>, which gives output similar to the <code>dir</code> command in MS-DOS/Windows. cp inputfile targetfile Copy inputfile to targetfile. Additional arguments (e.g. -r or -v are explained in the man-page.) mv inputfile targetfile Move inputfile to targetfile. Additional arguments (e.g. -i or -v are explained in the man-page.) This is the way to rename a file. Note that you cannot use a construction like mv *.htm *.html to add an ``l'' to a bunch of files. A small shell script can provide a way to do this: <code>for i in *.htm; do mv i; done</code> rm filename Remove filename. Additional arguments (e.g. -r or -v are explained in the man-page.) Note: there is no undelete-alike function in most unices. mkdir dirname Creates a directory called dirname. rmdir dirname Removes an empty directory. Use rm -r to delete a directory and recursively everything in it. Add -f to disable any prompts (dangerous!). ==Getting help== man command-name Displays manual pages, if available. E.g. man ls. Use 'q' to exit. Relatives: apropos, help. apropos word Searches through headers of all man pages. help command-name Displays help about command-name. Only for internal bash-functions. bash The Bourne Again SHell. Widely used successor of sh, the Bourne shell. This is the program you're working under after you open a ssh-session (you don't have to start it to use it). Bash interprets your commands, and executes them. Tab-completion, * and ? expansions, etc are all bash functions. man bash will give you tons of info about it. Alternatives : tcsh, zsh, rc ==Text editors== It's easier to use a text editor on a server, than editing your file locally and uploading that file. nano Probably the easiest text editor. Should be self-explanatory. The symbol ^ is used for the ctrl key and M- stands for alt. joe Another easy text editor. Press Ctrl+C to quit. vim Probably the best text editor. Start editing by pressing i. Stop editing by pressing the escape key. Save and quit with :wq. Quit without saving with :q!. ==Utilities== df Displays info about the free diskspace on the system. df . will give info about the filesystem where the current directory resides. The output becomes a bit more readable with the -h switch. du Displays info about the diskusage in the current directory (and its subdirectories. A common parameter is -s , equivalent to -summarize , to summarize the disk-usage (without the per-subdir totals). quota Displays info about your diskusage, and your disk quota. Quota are limits on diskusage, imposed by the system administrator. The system will warn you if you exceed these limits. ps Displays info about processes. Various options possible, for example ps auxf gives info on all processes, including process owner, memory usage, and parent-child indication. htop Displays top CPU processes. Use it to see what gets most cpu power at the moment. Don't leave top open for a long time, since it eats cpu time itself. (quit with 'q'). [[Category:Shell]] 5c18cf926645b65ebc80709fed61cdbad2c1e157 1852 1851 2024-08-31T12:40:23Z Timo 54 /* Getting help */ wikitext text/x-wiki Once you've connected, you can use these commands to use the ULYSSIS shell. First of all, whenever you need to type a longer command or filename, try the <code>TAB</code> key as it will try to complete the name of the command or file you are typing. Pressing <code>TAB</code> twice will show a list of possible completions. A more extensive document on this can be found at https://info-ee.surrey.ac.uk/Teaching/Unix/. ==Basic file managment== cd directoryname Change directory. Works the same as under MS-DOS. cd without argument changes to your home directory (like My Documents in windows). Go to the parent directory with <code>cd ..</code> ls List the contents of the current directory. Many different formats are available, a common one is <code>ls -al</code>. To accomodate MS-DOS/Windows users, <code>dir</code> is an alias (synonym) for <code>ls -alF</code>, which gives output similar to the <code>dir</code> command in MS-DOS/Windows. cp inputfile targetfile Copy inputfile to targetfile. Additional arguments (e.g. -r or -v are explained in the man-page.) mv inputfile targetfile Move inputfile to targetfile. Additional arguments (e.g. -i or -v are explained in the man-page.) This is the way to rename a file. Note that you cannot use a construction like mv *.htm *.html to add an ``l'' to a bunch of files. A small shell script can provide a way to do this: <code>for i in *.htm; do mv i; done</code> rm filename Remove filename. Additional arguments (e.g. -r or -v are explained in the man-page.) Note: there is no undelete-alike function in most unices. mkdir dirname Creates a directory called dirname. rmdir dirname Removes an empty directory. Use rm -r to delete a directory and recursively everything in it. Add -f to disable any prompts (dangerous!). ==Getting help== man command-name Displays manual pages, if available. E.g. man ls. Use 'q' to exit. Relatives: apropos, help. apropos word Searches through headers of all man pages. help command-name Displays help about command-name. Only for internal bash-functions. bash The Bourne Again SHell. Widely used successor of sh, the Bourne shell. This is the program you're working under after you open a ssh-session (you don't have to start it to use it). Bash interprets your commands, and executes them. Tab-completion, * and ? expansions, etc are all bash functions. man bash will give you tons of info about it. Alternatives : tcsh, zsh, rc ==Text editors== It's easier to use a text editor on a server, than editing your file locally and uploading that file. nano Probably the easiest text editor. Should be self-explanatory. The symbol ^ is used for the ctrl key and M- stands for alt. vim Probably the best text editor. Start editing by pressing i. Stop editing by pressing the escape key. Save and quit with :wq. Quit without saving with :q!. ==Utilities== df Displays info about the free diskspace on the system. df . will give info about the filesystem where the current directory resides. The output becomes a bit more readable with the -h switch. du Displays info about the diskusage in the current directory (and its subdirectories. A common parameter is -s , equivalent to -summarize , to summarize the disk-usage (without the per-subdir totals). quota Displays info about your diskusage, and your disk quota. Quota are limits on diskusage, imposed by the system administrator. The system will warn you if you exceed these limits. ps Displays info about processes. Various options possible, for example ps auxf gives info on all processes, including process owner, memory usage, and parent-child indication. htop Displays top CPU processes. Use it to see what gets most cpu power at the moment. Don't leave top open for a long time, since it eats cpu time itself. (quit with 'q'). [[Category:Shell]] 2caba93ec2539e16a673ad8480a07a841a069452 0 34 1853 1812 2024-10-12T12:24:08Z Milanmeu 47 Google stuurt geen bevestigingsmail wikitext text/x-wiki {{SMTPnotice|a forwarder as an alias}} You may want to send e-mail from Gmail using your @ulyssis.org address, or another domain name that you use for your account. Gmail allows you to do this, but asks for SMTP info. We don't provide SMTP on our own mail server, but you can use the SMTP servers of the KU Leuven. # In Gmail, click on the gear icon at the top right. # Click '''See all settings''' (Dutch: '''Alle instellingen bekijken'''). # Go to the tab '''Accounts and Import''' (Dutch: '''Accounts en import'''). # Under '''Send mail as:''' (Dutch: '''Mail verzenden als:'''), click on: '''Add another email address''' (Dutch: '''Nog een e-mailadres toevoegen'''). # Fill in the email address you want to send from, and check '''Treat as an alias.''' (Dutch: '''Beschouwen als alias.''') More info: https://support.google.com/a/answer/1710338 # Optionally: Enter a '''Name''', the recipient will see this name instead of or next to your email address. # Click on '''Next step''' (Dutch: '''Volgende stap'''). # Fill in the [https://admin.kuleuven.be/icts/english/services/email/imap-configuratie-en KU Leuven SMTP information] ([https://admin.kuleuven.be/icts/services/email/imap-configuratie Dutch]): #*'''SMTP server''': '''smtps.kuleuven.be''' #* '''Port''': '''465''' #* '''Username''': your KU Leuven intranet userid r or u-number e.g. r0123456 #* '''Password''': your central KU Leuven password #* '''Secured connection using''': '''SSL''' # Click on the '''Add Account''' (Dutch: '''Account toevoegen''') button. # Confirm your request using the link or code, you just received via an email on the address you provided. You can now send emails in Gmail from this address: # In Gmail, click '''Compose''' (Dutch: '''Opstellen'''). # Click on the email address next to '''From''' (Dutch: '''Van'''). # Select the email address you want to send from. [[Category:Mail]] fa354134f55cc0fb62456cddc89c21be9f90a3b6 0 77 1854 1814 2024-10-13T13:29:21Z Milanmeu 47 wikitext text/x-wiki {{SMTPnotice|a forwarder as an alias}} You may want to send e-mail from Thunderbird using your @ulyssis.org address, or another domain name that you use for your account. Thunderbird allows you to do this. The KU Leuven provides an SMTP server which you can use as a student. Make sure the give your KU Leuven account access to this SMTP server using our tool on https://ulyssis.org/smtp before configuring Thunderbird. == Add a mailbox to Thuderbird == Before you can add an alias to send mails, you should have a mailbox configured in Thunderbird. If you want to add your @ulyssis.org mailbox, you can use our [[Mailbox in Thunderbird]] docs. For other mail providers refer to their documentation or the documentation of Thunderbird. == Adding the KU Leuven SMTP server in Thunderbird == If you already have the KU Leuven SMTP server configured in Thunderbird, you can skip this step and proceed to [[#Configure an identity for your e-mail account|Configure an identity for your e-mail account]] below. You may have already added the KU Leuven SMTP server in Thunderbird when you created another alias or if you added your @ulyssis.org mailbox using our [[Mailbox in Thunderbird]] docs. Go to your '''Account Settings''' (Edit > Account Settings or Tools > Account Settings, depending on your operating system). At the bottom of the left sidebar, you will find an entry named '''Outgoing Server (SMTP)'''. Click this to access your SMTP settings. In your SMTP settings, you should see a list of existing SMTP servers. We want to add a new entry, so click the '''Add...''' button. In the screen that pops up, fill in the settings of the KU Leuven SMTP server, using the example screenshot below. Replace the displayed user name with your own KULid (m/r/s/u number). You will have to fill in the corresponding password on first use. [[File:Thunderbird-SMTPS.png]] == Configure an identity for your e-mail account == Back in the '''Account Settings''' screen, in the left sidebar, click on your e-mail address (not on any of its children). In the screen that opens, there will be a button '''Manage Identities...''' at the bottom. Click it. In the new screen, there will be one existing identity already: the default identity corresponding with your normal e-mail address. We want to add a new identity, so click the '''Add...''' button. In the screen that pops up, fill in the name and e-mail address you wish to use. At the bottom, make sure you choose the KU Leuven SMTP server as '''Outgoing Server'''. This is shown in the image below. [[File:Thunderbird-Identity.png]] If you're adding an identity for a group alias, you may also want to automatically send a copy of any replies or emails you're sending to the alias itself to make sure all others are aware of it. To do that, enable the BCC checkbox under the '''Copies & Folders''' tab. It should automatically contain the alias. == Sending your first e-mail == When you compose a new e-mail, you can change the sender in the "From" field to the identity you just configured. If everything was installed correctly, Thunderbird will show you a pop-up to enter your KU Leuven password when you try to send the e-mail. In this pop-up, you can choose to save this password for later use. [[Category:Mail]] 98630f019a74dbcbfe6e3ea558542d398c92b9f1 1855 1854 2024-10-13T13:30:40Z Milanmeu 47 /* Add a mailbox to Thuderbird */ wikitext text/x-wiki {{SMTPnotice|a forwarder as an alias}} You may want to send e-mail from Thunderbird using your @ulyssis.org address, or another domain name that you use for your account. Thunderbird allows you to do this. The KU Leuven provides an SMTP server which you can use as a student. Make sure the give your KU Leuven account access to this SMTP server using our tool on https://ulyssis.org/smtp before configuring Thunderbird. == Add a mailbox to Thuderbird == Before you can add an alias to send mails, you should have a mailbox configured in Thunderbird. If you want to add your @ulyssis.org mailbox, you can use our [[Mailbox in Thunderbird]] docs. For other mail providers refer to their documentation or the documentation of Thunderbird. In most cases you can just follow the configuration steps when you first open Thunderbird. == Adding the KU Leuven SMTP server in Thunderbird == If you already have the KU Leuven SMTP server configured in Thunderbird, you can skip this step and proceed to [[#Configure an identity for your e-mail account|Configure an identity for your e-mail account]] below. You may have already added the KU Leuven SMTP server in Thunderbird when you created another alias or if you added your @ulyssis.org mailbox using our [[Mailbox in Thunderbird]] docs. Go to your '''Account Settings''' (Edit > Account Settings or Tools > Account Settings, depending on your operating system). At the bottom of the left sidebar, you will find an entry named '''Outgoing Server (SMTP)'''. Click this to access your SMTP settings. In your SMTP settings, you should see a list of existing SMTP servers. We want to add a new entry, so click the '''Add...''' button. In the screen that pops up, fill in the settings of the KU Leuven SMTP server, using the example screenshot below. Replace the displayed user name with your own KULid (m/r/s/u number). You will have to fill in the corresponding password on first use. [[File:Thunderbird-SMTPS.png]] == Configure an identity for your e-mail account == Back in the '''Account Settings''' screen, in the left sidebar, click on your e-mail address (not on any of its children). In the screen that opens, there will be a button '''Manage Identities...''' at the bottom. Click it. In the new screen, there will be one existing identity already: the default identity corresponding with your normal e-mail address. We want to add a new identity, so click the '''Add...''' button. In the screen that pops up, fill in the name and e-mail address you wish to use. At the bottom, make sure you choose the KU Leuven SMTP server as '''Outgoing Server'''. This is shown in the image below. [[File:Thunderbird-Identity.png]] If you're adding an identity for a group alias, you may also want to automatically send a copy of any replies or emails you're sending to the alias itself to make sure all others are aware of it. To do that, enable the BCC checkbox under the '''Copies & Folders''' tab. It should automatically contain the alias. == Sending your first e-mail == When you compose a new e-mail, you can change the sender in the "From" field to the identity you just configured. If everything was installed correctly, Thunderbird will show you a pop-up to enter your KU Leuven password when you try to send the e-mail. In this pop-up, you can choose to save this password for later use. [[Category:Mail]] 611ab0ad11a2efaf3b3e2fe0c7651e19dd63dc47 1857 1855 2024-10-14T00:02:13Z Bert 8 /* Add a mailbox to Thuderbird */ wikitext text/x-wiki {{SMTPnotice|a forwarder as an alias}} You may want to send e-mail from Thunderbird using your @ulyssis.org address, or another domain name that you use for your account. Thunderbird allows you to do this. The KU Leuven provides an SMTP server which you can use as a student. Make sure the give your KU Leuven account access to this SMTP server using our tool on https://ulyssis.org/smtp before configuring Thunderbird. == Add a mailbox to Thuderbird == Before you can add an alias to send mails, you should set up a mailbox in Thunderbird. Most commonly you will want to set up the mailbox in which you receive the emails you want to reply to. If you are for example wanting to configure pr@mystudentunion.be in Thunderbird, and this email address forwards to johndoe@student.kuleuven.be, then you will want to configure johndoe@student.kuleuven.be inside Thunderbird before continuing. If you want to add your @ulyssis.org mailbox, you can use our [[Mailbox in Thunderbird]] docs. For other mail providers refer to their documentation or the documentation of Thunderbird. In most cases (for example Gmail, Google, Hotmail and Outlook.com) Thunderbird will autodetect the right configuration once you enter your email address and password. Otherwise you may need to look at the documentation provided by your email provider. For your KU Leuven mailbox you can always check their [https://admin.kuleuven.be/icts/services/email/m365/configuratie-in-thunderbird-via-imap official documentation]. == Adding the KU Leuven SMTP server in Thunderbird == If you already have the KU Leuven SMTP server configured in Thunderbird, you can skip this step and proceed to [[#Configure an identity for your e-mail account|Configure an identity for your e-mail account]] below. You may have already added the KU Leuven SMTP server in Thunderbird when you created another alias or if you added your @ulyssis.org mailbox using our [[Mailbox in Thunderbird]] docs. Go to your '''Account Settings''' (Edit > Account Settings or Tools > Account Settings, depending on your operating system). At the bottom of the left sidebar, you will find an entry named '''Outgoing Server (SMTP)'''. Click this to access your SMTP settings. In your SMTP settings, you should see a list of existing SMTP servers. We want to add a new entry, so click the '''Add...''' button. In the screen that pops up, fill in the settings of the KU Leuven SMTP server, using the example screenshot below. Replace the displayed user name with your own KULid (m/r/s/u number). You will have to fill in the corresponding password on first use. [[File:Thunderbird-SMTPS.png]] == Configure an identity for your e-mail account == Back in the '''Account Settings''' screen, in the left sidebar, click on your e-mail address (not on any of its children). In the screen that opens, there will be a button '''Manage Identities...''' at the bottom. Click it. In the new screen, there will be one existing identity already: the default identity corresponding with your normal e-mail address. We want to add a new identity, so click the '''Add...''' button. In the screen that pops up, fill in the name and e-mail address you wish to use. At the bottom, make sure you choose the KU Leuven SMTP server as '''Outgoing Server'''. This is shown in the image below. [[File:Thunderbird-Identity.png]] If you're adding an identity for a group alias, you may also want to automatically send a copy of any replies or emails you're sending to the alias itself to make sure all others are aware of it. To do that, enable the BCC checkbox under the '''Copies & Folders''' tab. It should automatically contain the alias. == Sending your first e-mail == When you compose a new e-mail, you can change the sender in the "From" field to the identity you just configured. If everything was installed correctly, Thunderbird will show you a pop-up to enter your KU Leuven password when you try to send the e-mail. In this pop-up, you can choose to save this password for later use. [[Category:Mail]] 4ab3fc1891e35b4b028a72422fcf7e2b2b7d6a6c 1858 1857 2024-10-14T00:02:43Z Bert 8 /* Add a mailbox to Thuderbird */ wikitext text/x-wiki {{SMTPnotice|a forwarder as an alias}} You may want to send e-mail from Thunderbird using your @ulyssis.org address, or another domain name that you use for your account. Thunderbird allows you to do this. The KU Leuven provides an SMTP server which you can use as a student. Make sure the give your KU Leuven account access to this SMTP server using our tool on https://ulyssis.org/smtp before configuring Thunderbird. == Add a mailbox to Thuderbird == Before you can add an alias to send mails, you should set up a mailbox in Thunderbird. Most commonly you will want to set up the mailbox in which you receive the emails you want to reply to. If you are for example trying to configure pr@mystudentunion.be in Thunderbird, and this email address forwards to johndoe@student.kuleuven.be, then you will want to configure johndoe@student.kuleuven.be inside Thunderbird before continuing. If you want to add your @ulyssis.org mailbox, you can use our [[Mailbox in Thunderbird]] docs. For other mail providers refer to their documentation or the documentation of Thunderbird. In most cases (for example Gmail, Google, Hotmail and Outlook.com) Thunderbird will autodetect the right configuration once you enter your email address and password. Otherwise you may need to look at the documentation provided by your email provider. For your KU Leuven mailbox you can always check their [https://admin.kuleuven.be/icts/services/email/m365/configuratie-in-thunderbird-via-imap official documentation]. == Adding the KU Leuven SMTP server in Thunderbird == If you already have the KU Leuven SMTP server configured in Thunderbird, you can skip this step and proceed to [[#Configure an identity for your e-mail account|Configure an identity for your e-mail account]] below. You may have already added the KU Leuven SMTP server in Thunderbird when you created another alias or if you added your @ulyssis.org mailbox using our [[Mailbox in Thunderbird]] docs. Go to your '''Account Settings''' (Edit > Account Settings or Tools > Account Settings, depending on your operating system). At the bottom of the left sidebar, you will find an entry named '''Outgoing Server (SMTP)'''. Click this to access your SMTP settings. In your SMTP settings, you should see a list of existing SMTP servers. We want to add a new entry, so click the '''Add...''' button. In the screen that pops up, fill in the settings of the KU Leuven SMTP server, using the example screenshot below. Replace the displayed user name with your own KULid (m/r/s/u number). You will have to fill in the corresponding password on first use. [[File:Thunderbird-SMTPS.png]] == Configure an identity for your e-mail account == Back in the '''Account Settings''' screen, in the left sidebar, click on your e-mail address (not on any of its children). In the screen that opens, there will be a button '''Manage Identities...''' at the bottom. Click it. In the new screen, there will be one existing identity already: the default identity corresponding with your normal e-mail address. We want to add a new identity, so click the '''Add...''' button. In the screen that pops up, fill in the name and e-mail address you wish to use. At the bottom, make sure you choose the KU Leuven SMTP server as '''Outgoing Server'''. This is shown in the image below. [[File:Thunderbird-Identity.png]] If you're adding an identity for a group alias, you may also want to automatically send a copy of any replies or emails you're sending to the alias itself to make sure all others are aware of it. To do that, enable the BCC checkbox under the '''Copies & Folders''' tab. It should automatically contain the alias. == Sending your first e-mail == When you compose a new e-mail, you can change the sender in the "From" field to the identity you just configured. If everything was installed correctly, Thunderbird will show you a pop-up to enter your KU Leuven password when you try to send the e-mail. In this pop-up, you can choose to save this password for later use. [[Category:Mail]] 24ac0e0c12f42f6e60c650cfb3fd04aa6bee0f63 1859 1858 2024-10-14T00:03:34Z Bert 8 /* Add a mailbox to Thuderbird */ wikitext text/x-wiki {{SMTPnotice|a forwarder as an alias}} You may want to send e-mail from Thunderbird using your @ulyssis.org address, or another domain name that you use for your account. Thunderbird allows you to do this. The KU Leuven provides an SMTP server which you can use as a student. Make sure the give your KU Leuven account access to this SMTP server using our tool on https://ulyssis.org/smtp before configuring Thunderbird. == Add a mailbox to Thuderbird == Before you can add an alias to send mails, you should set up a mailbox in Thunderbird. Most commonly you will want to set up the mailbox in which you receive the emails you want to reply to. If you are for example trying to configure pr@mystudentunion.be in Thunderbird, and this email address forwards to johndoe@student.kuleuven.be, then you will want to configure johndoe@student.kuleuven.be inside Thunderbird before continuing. In most cases (for example Gmail, Google, Hotmail and Outlook.com) Thunderbird will autodetect the right configuration once you enter your email address and password. Otherwise you may need to look at the documentation provided by your email provider. For your KU Leuven mailbox you can always check their [https://admin.kuleuven.be/icts/services/email/m365/configuratie-in-thunderbird-via-imap official documentation]. If you want to add your @ulyssis.org mailbox, you can use our [[Mailbox in Thunderbird]] docs. For other mail providers refer to their documentation or the documentation of Thunderbird. == Adding the KU Leuven SMTP server in Thunderbird == If you already have the KU Leuven SMTP server configured in Thunderbird, you can skip this step and proceed to [[#Configure an identity for your e-mail account|Configure an identity for your e-mail account]] below. You may have already added the KU Leuven SMTP server in Thunderbird when you created another alias or if you added your @ulyssis.org mailbox using our [[Mailbox in Thunderbird]] docs. Go to your '''Account Settings''' (Edit > Account Settings or Tools > Account Settings, depending on your operating system). At the bottom of the left sidebar, you will find an entry named '''Outgoing Server (SMTP)'''. Click this to access your SMTP settings. In your SMTP settings, you should see a list of existing SMTP servers. We want to add a new entry, so click the '''Add...''' button. In the screen that pops up, fill in the settings of the KU Leuven SMTP server, using the example screenshot below. Replace the displayed user name with your own KULid (m/r/s/u number). You will have to fill in the corresponding password on first use. [[File:Thunderbird-SMTPS.png]] == Configure an identity for your e-mail account == Back in the '''Account Settings''' screen, in the left sidebar, click on your e-mail address (not on any of its children). In the screen that opens, there will be a button '''Manage Identities...''' at the bottom. Click it. In the new screen, there will be one existing identity already: the default identity corresponding with your normal e-mail address. We want to add a new identity, so click the '''Add...''' button. In the screen that pops up, fill in the name and e-mail address you wish to use. At the bottom, make sure you choose the KU Leuven SMTP server as '''Outgoing Server'''. This is shown in the image below. [[File:Thunderbird-Identity.png]] If you're adding an identity for a group alias, you may also want to automatically send a copy of any replies or emails you're sending to the alias itself to make sure all others are aware of it. To do that, enable the BCC checkbox under the '''Copies & Folders''' tab. It should automatically contain the alias. == Sending your first e-mail == When you compose a new e-mail, you can change the sender in the "From" field to the identity you just configured. If everything was installed correctly, Thunderbird will show you a pop-up to enter your KU Leuven password when you try to send the e-mail. In this pop-up, you can choose to save this password for later use. [[Category:Mail]] 5027ee7d8ae9cf8577d1c238804ed8bfd16cab62 1860 1859 2024-10-14T00:04:07Z Bert 8 /* Add a mailbox to Thuderbird */ wikitext text/x-wiki {{SMTPnotice|a forwarder as an alias}} You may want to send e-mail from Thunderbird using your @ulyssis.org address, or another domain name that you use for your account. Thunderbird allows you to do this. The KU Leuven provides an SMTP server which you can use as a student. Make sure the give your KU Leuven account access to this SMTP server using our tool on https://ulyssis.org/smtp before configuring Thunderbird. == Add a mailbox to Thuderbird == Before you can add an alias to send mails, you should set up a mailbox in Thunderbird. Most commonly you will want to set up the mailbox in which you receive the emails you want to reply to. If you are for example trying to configure pr@mystudentunion.be in Thunderbird, and this email address forwards to johndoe@student.kuleuven.be, then you will want to configure johndoe@student.kuleuven.be inside Thunderbird before continuing. In most cases (for example Gmail, Google, Hotmail and Outlook.com) Thunderbird will autodetect the right configuration once you enter your email address and password. Otherwise you may need to look at the documentation provided by your email provider. For your KU Leuven mailbox you can always check their [https://admin.kuleuven.be/icts/services/email/m365/configuratie-in-thunderbird-via-imap official documentation]. If you want to add your @ulyssis.org mailbox, you can use our [[Mailbox in Thunderbird]] documentation page. For other mail providers refer to their documentation or the documentation of Thunderbird. == Adding the KU Leuven SMTP server in Thunderbird == If you already have the KU Leuven SMTP server configured in Thunderbird, you can skip this step and proceed to [[#Configure an identity for your e-mail account|Configure an identity for your e-mail account]] below. You may have already added the KU Leuven SMTP server in Thunderbird when you created another alias or if you added your @ulyssis.org mailbox using our [[Mailbox in Thunderbird]] docs. Go to your '''Account Settings''' (Edit > Account Settings or Tools > Account Settings, depending on your operating system). At the bottom of the left sidebar, you will find an entry named '''Outgoing Server (SMTP)'''. Click this to access your SMTP settings. In your SMTP settings, you should see a list of existing SMTP servers. We want to add a new entry, so click the '''Add...''' button. In the screen that pops up, fill in the settings of the KU Leuven SMTP server, using the example screenshot below. Replace the displayed user name with your own KULid (m/r/s/u number). You will have to fill in the corresponding password on first use. [[File:Thunderbird-SMTPS.png]] == Configure an identity for your e-mail account == Back in the '''Account Settings''' screen, in the left sidebar, click on your e-mail address (not on any of its children). In the screen that opens, there will be a button '''Manage Identities...''' at the bottom. Click it. In the new screen, there will be one existing identity already: the default identity corresponding with your normal e-mail address. We want to add a new identity, so click the '''Add...''' button. In the screen that pops up, fill in the name and e-mail address you wish to use. At the bottom, make sure you choose the KU Leuven SMTP server as '''Outgoing Server'''. This is shown in the image below. [[File:Thunderbird-Identity.png]] If you're adding an identity for a group alias, you may also want to automatically send a copy of any replies or emails you're sending to the alias itself to make sure all others are aware of it. To do that, enable the BCC checkbox under the '''Copies & Folders''' tab. It should automatically contain the alias. == Sending your first e-mail == When you compose a new e-mail, you can change the sender in the "From" field to the identity you just configured. If everything was installed correctly, Thunderbird will show you a pop-up to enter your KU Leuven password when you try to send the e-mail. In this pop-up, you can choose to save this password for later use. [[Category:Mail]] 8bc3ac748d042cb185e84b63007957180a5b90ba 1861 1860 2024-10-14T00:06:29Z Bert 8 /* Adding the KU Leuven SMTP server in Thunderbird */ wikitext text/x-wiki {{SMTPnotice|a forwarder as an alias}} You may want to send e-mail from Thunderbird using your @ulyssis.org address, or another domain name that you use for your account. Thunderbird allows you to do this. The KU Leuven provides an SMTP server which you can use as a student. Make sure the give your KU Leuven account access to this SMTP server using our tool on https://ulyssis.org/smtp before configuring Thunderbird. == Add a mailbox to Thuderbird == Before you can add an alias to send mails, you should set up a mailbox in Thunderbird. Most commonly you will want to set up the mailbox in which you receive the emails you want to reply to. If you are for example trying to configure pr@mystudentunion.be in Thunderbird, and this email address forwards to johndoe@student.kuleuven.be, then you will want to configure johndoe@student.kuleuven.be inside Thunderbird before continuing. In most cases (for example Gmail, Google, Hotmail and Outlook.com) Thunderbird will autodetect the right configuration once you enter your email address and password. Otherwise you may need to look at the documentation provided by your email provider. For your KU Leuven mailbox you can always check their [https://admin.kuleuven.be/icts/services/email/m365/configuratie-in-thunderbird-via-imap official documentation]. If you want to add your @ulyssis.org mailbox, you can use our [[Mailbox in Thunderbird]] documentation page. For other mail providers refer to their documentation or the documentation of Thunderbird. == Adding the KU Leuven SMTP server in Thunderbird == If you already have the KU Leuven SMTP server configured in Thunderbird, you can skip this step and proceed to [[#Configure an identity for your e-mail account|Configure an identity for your e-mail account]] below. You may have already added the KU Leuven SMTP server in Thunderbird when you created another alias or if you added your @ulyssis.org mailbox using our [[Mailbox in Thunderbird]] docs. Keep in mind that if you added your KU Leuven email address this '''no longer''' uses the KU Leuven SMTP, so you will still need to add it. Go to your '''Account Settings''' (Edit > Account Settings or Tools > Account Settings, depending on your operating system). At the bottom of the left sidebar, you will find an entry named '''Outgoing Server (SMTP)'''. Click this to access your SMTP settings. In your SMTP settings, you should see a list of existing SMTP servers. We want to add a new entry, so click the '''Add...''' button. In the screen that pops up, fill in the settings of the KU Leuven SMTP server, using the example screenshot below. Replace the displayed user name with your own KULid (m/r/s/u number). You will have to fill in the corresponding password on first use. [[File:Thunderbird-SMTPS.png]] == Configure an identity for your e-mail account == Back in the '''Account Settings''' screen, in the left sidebar, click on your e-mail address (not on any of its children). In the screen that opens, there will be a button '''Manage Identities...''' at the bottom. Click it. In the new screen, there will be one existing identity already: the default identity corresponding with your normal e-mail address. We want to add a new identity, so click the '''Add...''' button. In the screen that pops up, fill in the name and e-mail address you wish to use. At the bottom, make sure you choose the KU Leuven SMTP server as '''Outgoing Server'''. This is shown in the image below. [[File:Thunderbird-Identity.png]] If you're adding an identity for a group alias, you may also want to automatically send a copy of any replies or emails you're sending to the alias itself to make sure all others are aware of it. To do that, enable the BCC checkbox under the '''Copies & Folders''' tab. It should automatically contain the alias. == Sending your first e-mail == When you compose a new e-mail, you can change the sender in the "From" field to the identity you just configured. If everything was installed correctly, Thunderbird will show you a pop-up to enter your KU Leuven password when you try to send the e-mail. In this pop-up, you can choose to save this password for later use. [[Category:Mail]] 38db3c10516007a86d7973f464f698ccf6bb7690 0 72 1856 1821 2024-10-13T22:36:46Z Bert 8 wikitext text/x-wiki {{warning|Ongoing issues for Hotmail/Outlook|Recently, several users have been unable to send email through aliases using Hotmail/Outlook due to a bug on the side of Microsoft. For now it's unclear if this issue will be fixed or if this functionality is permanently broken.}} {{notice|Adding an alias to Hotmail/Outlook is not advised|Hotmail/Outlook does not use a relevant SMTP server, for example the one of the KU Leuven, to send emails as an alias. This may cause recipients to automatically reject your email or mark it as spam. You can circumvent this issue by using Thunderbird or another email provider. Please refer to [[Using a forwarder as an alias]] for some potential alternatives.}} You may want to send e-mail from Outlook.com using your @ulyssis.org address, or another domain name that you use for your account. Outlook.com allows you to do this by configuring a few settings. Because you should only be able to send mails from an e-mail address you actually own, make sure that you configured receiving mails before starting this process. Outlook.com will send a confirmation mail to the provided e-mail address to confirm that you own it. # In Outlook.com, click on your profile image. # Click '''My Microsoft account''' (Dutch: '''Mijn Microsoft-account'''). # Go to the tab '''Your info''' (Dutch: '''Je gegevens'''). # Under '''Account info''' (Dutch: '''Rekeninggegevens''') click on: '''Sign-in preferences''' (Dutch: '''Aanmeldingsvoorkeuren'''). # You will have to log in again to proceed. Click '''Add email''' (Dutch: '''E-mailadres toevoegen'''). # Select '''Add an existing email address as a Microsoft account alias''' (Dutch: '''Een bestaand e-mailadres als een Microsoft-accountalias toevoegen''') and fill in the email address you want to send from. # Click '''Add alias''' (Dutch: '''Alias toevoegen'''). # Confirm your request using the link or code, you just received via an email on the address you provided. You can now send emails in Outlook.com from this address: # In Outlook.com, click '''New message''' (Dutch: '''Nieuw bericht'''). # Click on '''From''' (Dutch: '''Van''') and select the email address. [[Category:Mail]] 9ba76d602073af2b6be302714f7cff65ee3c6b07 0 114 1862 1002 2024-10-16T13:29:24Z Milanmeu 47 Add Mail Category wikitext text/x-wiki Sending email is fairly similar on most hosting services. ULYSSIS hosting is not too different in that sense. We do use a queueing system to detect accounts that are being abused by malicious actors to send spam. == How? == In PHP and most other programming languages, content management systems (CMS), and frameworks, you can use the builtin email function. This may be referred to with names such as builtin, default, standard, local or sendmail. == Delay and limitations == Because of the large amount of users on our hosting services, security breaches and misconfigurations due to user mismanagement happen from time to time. As many malicious actors focus their efforts on abusing servers with a good reputation for the distribution of spam, it is not uncommon to find several thousands of emails being sent once a problem occurs. To combat this, ULYSSIS hosting delays sending of emails for up to 5 minutes and verifies a certain amount (50) of email is never surpassed. If at any point the level is surpassed, ULYSSIS is notified and can take action, while probable spam is stopped from being transmitted. Therefore it is important to keep a potential delay in time when expecting email from your website, but also not to send vast amount of email all at once. It is in general good practice to spread the transmission of for example an email list with several hundred participants. [[Category:Webserver]] [[Category:Mail]] c6b30133ae0f974e92300007594bd21b5261849f 0 3 1863 1847 2024-10-16T13:30:02Z Milanmeu 47 /* Mail */ wikitext text/x-wiki <div style="background:#f9f9f9;border:1px solid #ddd;font-size:95%;padding:1.5em;"> Welcome to our documentation website. Many of the common procedures and issues our users experience are described here. If you still encounter problems we haven't covered or you just can't seem to get things to work, even though you followed one of our manuals, feel free to contact us on ulyssis@ulyssis.org for personal support.</div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Account == * [[Registering a new account]] * [[Renewing your account]] * [[Transferring your account]] * [[Resetting your password]] * [[Reducing disk usage|Help, my account uses too much disk space]] * [[Why do I have to pay 0.00 euro and how?]] </div><div style="width:45%;float:left"> == Files == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Making Backups]] * [[Secure file permissions]] * [[Reducing disk usage]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Webserver == * [[Webserver changes summer 2024]] * [[Using your webspace]] * [[Using (Fast)CGI for non-PHP websites]] * [[Getting Apache logs]] * [[Managing PHP errors]] * [[Setting PHP options]] * [[Sending email from websites]] * [[Adding domain names|Adding domain names (.be, .com, .org, ...)]] * [[Getting SSL/TLS|Getting SSL/TLS (HTTPS security)]] * [[Shibboleth|Shibboleth (Centrale KU Leuven Login)]] * [[Claiming a port]] * [[ULYSSIS security measures]] </div><div style="width:45%;float:left"> == Mail == * [[Introduction to ULYSSIS email]] * [[Mailbox]] * [[Mailbox in Thunderbird]] * [[Forwarders]] * [[Using a forwarder as an alias]] * [[Add an alias in Gmail]] * [[Add an alias in Hotmail/Outlook]] * [[Add an alias in Thunderbird]] * [[Add an alias in ULYSSIS webmail]] * [[Spam]] * [[Sending email from websites]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == CMSs == * [[Software Version Checker]] * [[Setting up WordPress]] * [[Setting up Drupal]] * [[Setting up Joomla]] * [[Setting up MediaWiki]] * [[Updating WordPress]] * [[Updating MediaWiki]] </div><div style="width:45%;float:left"> == Security & anti-spam == * [[Secure file permissions]] * [[Software Version Checker]] * [[Preventing spam on Wordpress]] * [[Preventing spam on Joomla]] * [[Preventing spam on Drupal]] * [[Preventing spam on MediaWiki]] * [[Securing MediaWiki using Centrale KU Leuven Login]] * [[ULYSSIS security measures]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Databases == * [[Using PostgreSQL]] * [[Using MySQL]] * [[Using PHPMyAdmin]] * [[Using PHPPgAdmin]] * [[Using Adminer]] * [[Making Backups]] </div><div style="width:45%;float:left"> == Shell == * [[Accessing your files]] * [[Transferring files over SFTP]] * [[Accessing shell servers over SSH]] * [[ULYSSIS public IRC]] * [[Useful Linux Commands]] * [[Managing Cron jobs]] * [[Claiming a port]] * [[Installing packages]] </div> <div style="clear:both;"></div> </div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Versioning == * [[GitLab]] </div><div style="width:45%;float:left"> == ULYSSIS Public Services == * [[ULYSSIS public IRC]] </div> <div style="clear:both;"></div> <div> <div style="width:45%;float:left;padding-right:10px;"> == Tutorials == * [[Using the kulemt package]] * [[Exporting your KU Leuven class schedule and calendar]] </div> <div style="clear:both;"></div> </div> __NOTOC__ eb0c6b749eecf9922006635e99b1a067184173a3 0 265 1864 1846 2024-10-31T17:53:34Z Onda 55 /* When are the changes planned? */ wikitext text/x-wiki This page lists the changes to the webservers of ULYSSIS in the summer of 2024, and how you can prepare for it. If any of these instructions are not clear to you, or if you have some more questions about the changes, '''don't hesitate to e-mail us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]'''. == When are the changes planned? == These changes are planned for Sunday, November 10th, and Monday, November 11th, 2024. == What will change? == We will upgrade the Ubuntu release on our servers from 22.04 LTS to 24.04 LTS. This will include newer version of many services. An overview of the most important version changes can be found below. For other services/packages, you can always use the [https://packages.ubuntu.com/ Ubuntu Package Search]. The distribution name for Ubuntu 24.04 LTS is "noble". * PHP will be updated from 8.1 to 8.3 * PostgreSQL will be updated from 14 to 16.2 * MariaDB (MySQL) will be updated from 10.6.7 to 10.11.8 * Python will be updated from 3.10 to 3.12 Furthermore, many services (such as Apache2) are migrating their regex engine from PCRE to PCRE2. You can find a list of incompatibilities [https://stackoverflow.com/questions/70273084/regex-differences-between-pcre-and-pcre2 here]. If you host your own PHP website, you might want to check out these guides: * [https://www.php.net/manual/en/migration82.php Migrating from PHP 8.1.x to PHP 8.2.x] * [https://www.php.net/manual/en/migration83.php Migrating from PHP 8.2.x to PHP 8.3.x] Note that any existing Python virtual environments in use will need to be recreated in order to function properly. b2e12056397b3f75da4e428c90f0de5823adbb18 0 78 1865 1831 2024-12-03T22:14:53Z Kou9 56 Replaced content with "{{notice|KU Leuven Internal Documentation| As KU Leuven has recently released their own internal documentation, we will direct you to their resources for further instructions. Please refer to the following link: https://icts.kuleuven.be/docs/at/cm/ep/s/Lessen_synchroniseren_via_iCal}} [[Category:Tutorials]]" wikitext text/x-wiki {{notice|KU Leuven Internal Documentation| As KU Leuven has recently released their own internal documentation, we will direct you to their resources for further instructions. Please refer to the following link: https://icts.kuleuven.be/docs/at/cm/ep/s/Lessen_synchroniseren_via_iCal}} [[Category:Tutorials]] e29e8c86050d5e0581f01bd299fd0f0108b35cb4 1866 1865 2024-12-03T22:19:02Z Kou9 56 wikitext text/x-wiki {{notice|KU Leuven Documentation| As KU Leuven has recently released their own documentation, we will direct you to their resources for further instructions. Please refer to the following link: https://icts.kuleuven.be/docs/at/cm/ep/s/Lessen_synchroniseren_via_iCal}} [[Category:Tutorials]] ba6ac78075de4db84e3f2795775b99b275e3f586 0 9 1867 1577 2024-12-30T01:01:33Z Bert 8 /* Using the command line */ wikitext text/x-wiki You can find all your Apache logs (like <code>access.log</code> and <code>error.log</code>) on all of our shell servers in the directory <code>/var/log/apache_user/''username''</code>. For more information on how to access your files, please visit [[Accessing your files]]. ==Using Cyberduck (graphical interface)== You can access the log files using an SFTP client like Cyberduck. After logging in to one of our shell servers as per [[Accessing your files]], click on "Go" on the top bar and then click "Go to Folder...": [[File:Getting Apache Logs - Cyberduck 1.png]] Then enter <code>/var/log/apache_user/''username''</code> as path name (replace ''username'' with your own username): [[File:Getting Apache Logs - Cyberduck 2.png]] After pressing "Go", you will see a directory for each of your websites, containing their Apache logs. [[File:Getting Apache Logs - Cyberduck 3.png]] You can view a log file by selecting it and pressing the "Edit" button. [[File:Getting Apache Logs - Cyberduck Edit button.png]] After a few days, logs will be compressed into a <code>bz2</code> file. You can download such a file and open it with [https://www.7-zip.org/ 7-Zip]. ==Using the command line== You can also access your logs by [[Accessing shell servers over SSH|logging in to one of our shell servers over SSH]] and navigating to the correct directory: username@ssh1:~$ cd /var/log/apache_user/username username@ssh1:/var/log/apache_user/username$ ls username.ulyssis.be username@ssh1:/var/log/apache_user/username$ cd username.ulyssis.be username@ssh1:/var/log/apache_user/username/username.ulyssis.be$ ls access-2014-05-07.log error-2014-05-07.log username@ssh1:/var/log/apache_user/username/username.ulyssis.be$ tail error-2014-05-07.log [Wed May 07 01:27:14 2014] [error] [client 10.0.0.1] File does not exist: /home/user/username/www/favicon.ico If you can't find your username inside of <code>/var/log/apache_user</code>, don't worry. If you enter it with <code>cd username</code>, it will automatically appear. Older logs will be compressed with bzip2 but can be easily browsed from the command line using bzless. Other tools like bzcat and bzgrep might also come in handy. [[Category:Webserver]] d10dc2d85b8ca3293371b5e12277feb8b7433148 1868 1867 2024-12-30T01:02:09Z Bert 8 /* Using the command line */ wikitext text/x-wiki You can find all your Apache logs (like <code>access.log</code> and <code>error.log</code>) on all of our shell servers in the directory <code>/var/log/apache_user/''username''</code>. For more information on how to access your files, please visit [[Accessing your files]]. ==Using Cyberduck (graphical interface)== You can access the log files using an SFTP client like Cyberduck. After logging in to one of our shell servers as per [[Accessing your files]], click on "Go" on the top bar and then click "Go to Folder...": [[File:Getting Apache Logs - Cyberduck 1.png]] Then enter <code>/var/log/apache_user/''username''</code> as path name (replace ''username'' with your own username): [[File:Getting Apache Logs - Cyberduck 2.png]] After pressing "Go", you will see a directory for each of your websites, containing their Apache logs. [[File:Getting Apache Logs - Cyberduck 3.png]] You can view a log file by selecting it and pressing the "Edit" button. [[File:Getting Apache Logs - Cyberduck Edit button.png]] After a few days, logs will be compressed into a <code>bz2</code> file. You can download such a file and open it with [https://www.7-zip.org/ 7-Zip]. ==Using the command line== You can also access your logs by [[Accessing shell servers over SSH|logging in to one of our shell servers over SSH]] and navigating to the correct directory: username@ssh1:~$ cd /var/log/apache_user/username username@ssh1:/var/log/apache_user/username$ ls username.ulyssis.be username@ssh1:/var/log/apache_user/username$ cd username.ulyssis.be username@ssh1:/var/log/apache_user/username/username.ulyssis.be$ ls access-2014-05-07.log error-2014-05-07.log username@ssh1:/var/log/apache_user/username/username.ulyssis.be$ tail error-2014-05-07.log [Wed May 07 01:27:14 2014] [error] [client 10.0.0.1] File does not exist: /home/user/username/www/favicon.ico If you can't find your username inside of <code>/var/log/apache_user</code>, don't worry. If you enter it with <code>cd username</code>, it will automatically appear. Older logs will be compressed with bzip2 but can be easily browsed from the command line using <code>bzless</code>. Other tools like <code>bzcat</code> and <code>bzgrep</code> might also come in handy. [[Category:Webserver]] 340c7470518b15b9a5ee9d2141acb4f62f492a19 0 37 1869 1833 2025-01-07T00:16:54Z Milanmeu 47 /* Python and Django */ wikitext text/x-wiki You're not stuck with PHP if you want to make a dynamic website. You can use all sorts of frameworks and programming languages with ULYSSIS, as long as it has CGI or FastCGI support. If you want to use a certain programming language or framework, and you can't get it to work, don't hesitate to contact us at [mailto:ulyssis@ulyssis.org ulyssis@ulyssis.org]. We will of course not write any code for you, but we can give you some pointers or directions. ==CGI== CGI is a simple way to create a dynamic website. We use Apache's [http://httpd.apache.org/docs/2.4/mod/mod_cgid.html mod_cgid] to provide support for CGI. Note, however, that CGI is inefficient and in general we recommend you to use a framework together with FastCGI. There are many frameworks, ranging from very simple and lightweight, to more complex and feature rich. If, for example, you want Apache to interpret all files with the extension <code>.cgi</code> as CGI scripts, use the following <tt>.htaccess</tt> file (to be placed in your <code>www</code> folder): <pre>Options +ExecCGI AddHandler cgi-script .cgi</pre> Here's an example of a very simple Python CGI script (called <code>hello.cgi</code>): <pre>#!/usr/bin/env python3 print('Content-Type: text/plain\n') print('Hello world!')</pre> CGI scripts need to be executable, otherwise they won't work: <pre>chmod +x hello.cgi</pre> ==FastCGI== We use Apache's [http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html mod_fcgid] to provide support for FastCGI. In order to use FastCGI, you will generally need a starter script specific to your programming languae, framework or application. Just do a web search for "''keyword'' mod_fcgid", where ''keyword'' is the programming language, framework or application you're planning to use, and you will often find good instructions. We've included some examples below You'll want to treat this starter script as a <code>mod_fcgid</code> script, and usually, you'll want to redirect everything to this script, so you can use an <code>.htaccess</code> file that looks like this: <syntaxhighlight lang="apache">Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ starter.fcgi/$1 [QSA,L]</syntaxhighlight> Replace ''starter.fcgi'' with the name of your starter script. Don't forget to make your starter script executable: <pre>chmod +x starter.fcgi</pre> The starter script must be located in the same folder as the <code>.htaccess</code> file. {{warning|Warning!|Do not place sensitive files inside the web accessible folder. Make sure they are located in a folder outside the document root, or they will be downloadable through the webserver.}} It is adviced to only place the fcgi starter script, <code>.htaccess</code> and static files (images, stylesheets) inside the document root. === Startup time and persistency === It is important to keep in mind that our Apache webworkers will only run your start script when a request is made. As soon as that first request has been received, it will try and keep a few instances of your application around for future use. This of course affects how you restart your application after changes (see below), but also means that applications with a longer start up time (for example a language such as Python combined with a larger framework) will experience an initial slow request. This slow startup is obviously not a factor for faster languages such as Haskell, C++ or Go. Sadly, Apache is unable to have FastCGI processes persist beyond a reload or restart. This means in practice that every night around 6h25 when the logs are rotated, which requires Apache to be reloaded, all running fcgi processes will be gracefully terminated. The same thing happens when we make changes to the Apache configuration when a new website or user is added. For those who have a very high startup time and don't generate enough traffic to not experience issues with this behaviour, it's possible to use a [[Managing_Cron_jobs | cronjob]] to visit the website every night at 6h30 or 7h, or even hourly. ===Restarting your application=== If you've changed your application, you will need to restart it for these changes to take effect. However, because you're editing the application on a different server than where it is running, you do not have access to the running process. You'll have to create some sort of mechanism to restart the process. In the Django and Go examples below, the starter script has been written so that when it is changed, the application is automatically restarted within 1 second. The same mechanism can be applied to other Python sites. You can change the modification date without actually changing the contents of the starter script by using <code>touch</code>: <pre>touch starter.fcgi</pre> Replace <code>starter.fcgi</code> with the name of your starter script. === Examples === ==== Python and Django ==== If you want to make a website using Python and [https://www.djangoproject.com/ Django], we recommend that you use a virtual environment. You can use the following steps to get up and running with Django on your ULYSSIS hosting account. <ol> <li>[[Accessing shell servers over SSH|Log in to a shell server]]</li> <li>Create a new virtualenv, you can create one in <code>~/.venv</code>, for example: <pre>python3 -m venv ~/.venv</pre> </li> <li>Activate this virtualenv: <pre>. ~/.venv/bin/activate</pre> </li> <li> Install Django and flup for FastCGI inside of this virtualenv: <pre>pip install django flup6</pre> </li> <li> Create a new Django project: <pre>django-admin startproject mysite</pre> Replace ''mysite'' with your project's desired name. </li> <li> Edit the allowed hosts in your Django project's settings, in <code>mysite/mysite/settings.py</code>. Look for the line <code>ALLOWED_HOSTS = []</code> and replace it with: <pre> ALLOWED_HOSTS = [ 'username.ulyssis.be', 'username.studentenweb.org' ] </pre> Use your ULYSSIS username in place of ''username''. </li> <li> Put an <code>.htaccess</code> file in your site's directory, e.g. the <code>www</code> folder: <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Create the starter script (replace <code>user</code> with org if you are an organization, and <code>username</code> with your ULYSSIS username): <syntaxhighlight lang="python">#!/home/user/username/.venv/bin/python import sys, os, os.path from threading import Thread this_file = os.path.realpath(__file__) site_dir = '/home/user/username/mysite' sys.path.insert(0, site_dir) os.chdir(site_dir) os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings' def stat_thread(): import time, os, signal start_mtime = os.stat(this_file).st_mtime while True: cur_mtime = os.stat(this_file).st_mtime if cur_mtime != start_mtime: os.kill(os.getpid(), signal.SIGTERM) time.sleep(1) Thread(target=stat_thread).start() from django.core.servers.basehttp import get_internal_wsgi_application from flup.server.fcgi import WSGIServer WSGIServer(get_internal_wsgi_application(), debug=False).run() </syntaxhighlight> Call this script <code>mysite.fcgi</code>. </li> <li> Make the starter script executable: <pre>chmod +x mysite.fcgi</pre> </li> <li> Go to ''username''.ulyssis.be (or whatever URL you chose to use), and it should show you the default "Welcome to Django" page. </li> </ol> This guide was based on, and you can find more information in the official Django documentation: * [https://docs.djangoproject.com/en/stable/intro/tutorial01/ The Django tutorial] * [https://web.archive.org/web/20220811150710/https://flask.palletsprojects.com/en/2.0.x/deploying/fastcgi/ Flask documentation for FastCGI] ==== Go ==== To make a website or web application in Go and host it on your ULYSSIS hosting account, you can use the standard library ''fcgi'' package. <ol> <li> [[Accessing shell servers over SSH|Log in to a shell server]]</li> <li> Put an <code>.htaccess</code> file in your site's directory (e.g. the <code>www</code> folder) with a reference to your executable. Here we've chosen <code>mysite.fcgi</code>, but you can adapt this to your liking. <pre>Options +ExecCGI AddHandler fcgid-script .fcgi RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ mysite.fcgi/$1 [QSA,L]</pre> </li> <li> Write your code, and compile the binary to <code>mysite.fcgi</code>. Below you can find a basic example of how to register two handlers (of which one is the fallback), then start the FastCGI client, and finally have a function (which is called as a goroutine) to check if the binary has been replaced so old processes don't stick around. <syntaxhighlight lang="go">package main import ( "fmt" "net/http" "net/http/fcgi" "os" "path/filepath" "time" ) func uri_interesting(w http.ResponseWriter, r *http.Request) { w.WriteHeader(http.StatusOK) fmt.Fprintln(w, "<h1>Oh, seems like this link isn't that interesting after all</h1>") fmt.Fprintln(w, "<p>Back to the <a href=\"/\">Homepage</a></p>") } func uri_default(w http.ResponseWriter, r *http.Request) { if r.URL.Path != "/" { w.WriteHeader(http.StatusNotFound) fmt.Fprintln(w, "<h1>This page doesn't exist</h1>") fmt.Fprintln(w, "<p>Back to the <a href=\"/\">Homepage</a></p>") } else { w.WriteHeader(http.StatusOK) fmt.Fprintln(w, "<h1>Welcome to this testwebsite!</h1>") fmt.Fprintln(w, "<p>This website is written in Go but doesn't really do much.") fmt.Fprintln(w, "Feel free to visit this <a href=\"/interesting/link\">Interesting link</a> or this <a href=\"/non-existent/link\">non-existent link</a>.</p>") } } func main() { go check_selfreplacement() http.HandleFunc("/interesting/link", uri_interesting) http.HandleFunc("/", uri_default) if err := fcgi.Serve(nil, nil); err != nil { panic(err) } } func check_selfreplacement() { fcgi_location, _ := os.Executable() fcgi_location, _ = filepath.EvalSymlinks(fcgi_location) start_stat, _ := os.Stat(fcgi_location) for { current_stat, _ := os.Stat(fcgi_location) if start_stat.ModTime() != current_stat.ModTime() { os.Exit(0) } time.Sleep(1 * time.Second) } } </syntaxhighlight> If you want to give this example a try, save it as <code>mysite.fcgi.go</code> and then use <code>go build mysite.fcgi.go</code> to compile it. </li> <li>Visit your website to verify everything works</li> </ol> [[Category:Webserver]] 6ca5cdeca528c088b3deb0671c2821a14ea9ba24